Reps/SOPs/Digital resources: Difference between revisions

Latest revision as of 19:32, 29 September 2023

Warning: With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.

This document describes the policies the Mozilla Reps Council agreed to apply when reviewing and approving Community IT requests.

General requirements

This are the general requirements evaluated in any request:

The following questions should be answered: Why this request is it needed? How does it benefit Mozilla mission?
The request coming from a known Mozilla community member.
The requester represents the project he’s requesting resources for. Communities will be asked to provide a document explaining who owns these kind of requests.
There is an established project/community (+6 months) supporting the request, already running in production stage.
There is at least 2 people on the project responsible for the request and as main contact point.

Domain Name

Full fit general requirements.

Hosting

Hosting requests should include a twelve (12) month road map. Include link to wiki.mozilla.org or other documentation. This helps to evaluate the life cycle & life span of the request. Some microsites, for example, only have a six month life, while others such as discourse.mozilla-community.org will have an indefinite life span.
In most cases, we try not to duplicate services that already exist. For example, Community IT team would prefer to migrate a Wordpress site into the Wordpress-as-a-Service instead of building a new Wordpress instance.
The domain for the website has already been transferred to Mozilla’s Domain Registrar or will be transferred.

Email

The domain name for the emails is already transferred to Mozilla.

SSL

The domain name for the website is already transferred to Mozilla.

FAQ

Why does the domain name need to be transferred to Mozilla?

We want all Mozilla Community domains to be safe, not just now, but always. This means that they are properly renewed and monitored by Mozilla IT.

Mozilla will work with the existing Domain Name Owner to transfer to Mozilla’s Domain Registrar. This will help ensure that these domain names and properly renewed and monitored. It also avoids possible future domain renewal / maintenance issues.

It’s a good practice to avoid individuals to own community domains, avoiding bottlenecks, possible future personal conflicts and the well known bus factor. Historically this approach has been proven more effective than individuals owning mozilla-related domains.

Mozilla will only own the administrative part, but the community is responsible and owns any changes and decisions to it and its subdomains. At the moment of the request the requester should provide a document describing how the community is organized to be sure he’s the right person to own this request.

Will Mozilla modify the domain or its content without community approval?

No. While your domain will be at Mozilla’s Domain Registrar and Mozilla Domain Name Servers, Mozilla will not modify the domain without approval or direction from the domain’s Technical Contact.

The Mozilla Reps Council will work to ensure that this policy is followed.

Can I still use my own DNS instead of mozilla’s one?

Yes, you can request to use your custom NS to handle the domain zone instead of Mozilla’s one.

For various services, you may be required to delegate a sub-domain NS RR to Mozilla. This allows Community Ops greater flexibility in managing the service. For instance, you may be asked to delete your blog site to Amazon’s Route 53:

blog.communitysysadmins.org. IN NS ns-277.awsdns-34.com.

Can I request any type of hosting?

Yes! The Community IT Operations team will be happy to work with you to find the best solutions for your needs.

@@ Line 1: / Line 1: @@
+{{Warning |1= With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.|title= With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.}}
 {{Remonav}}
-[[category:remosop]]
-= Who should create a community site? =
+This document describes the policies the Mozilla Reps Council agreed to apply when reviewing and approving [https://bugzilla.mozilla.org/form.reps.it Community IT requests].
-A Mozilla Representative on behalf of his/her local community with prior consensus from that community + A mentor/ or Council can vouch.
+==General requirements==
+This are the general requirements evaluated in any request:
+* The following questions should be answered: Why this request is it needed? How does it benefit Mozilla mission?
+* The request coming from a known Mozilla community member.
+* The requester represents the project he’s requesting resources for. Communities will be asked to provide a document explaining who owns these kind of requests.
+* There is an established project/community (+6 months) supporting the request, already running in production stage.
+* There is at least 2 people on the project responsible for the request and as main contact point.
+==Domain Name==
+* Full fit general requirements.
+==Hosting==
+* Hosting requests should include a twelve (12) month road map. Include link to wiki.mozilla.org or other documentation. This helps to evaluate the life cycle & life span of the request. Some microsites, for example, only have a six month life, while others such as discourse.mozilla-community.org will have an indefinite life span.
+* In most cases, we try not to duplicate services that already exist. For example, Community IT team would prefer to migrate a Wordpress site into the Wordpress-as-a-Service instead of building a new Wordpress instance.
+* The domain for the website has already been transferred to Mozilla’s Domain Registrar or will be transferred.
+==Email==
+* The domain name for the emails is already transferred to Mozilla.
+==SSL==
+* The domain name for the website is already transferred to Mozilla.
+==FAQ==
+'''Why does the domain name need to be transferred to Mozilla?'''
+We want all Mozilla Community domains to be safe, not just now, but always. This means that they are properly renewed and monitored by Mozilla IT.
+Mozilla will work with the existing Domain Name Owner to transfer to Mozilla’s Domain Registrar. This will help ensure that these domain names and properly renewed and monitored. It also avoids possible future domain renewal / maintenance issues.
-= When should you do it? =
+It’s a good practice to avoid individuals to own community domains, avoiding bottlenecks, possible future personal conflicts and the well known bus factor. Historically this approach has been proven more effective than individuals owning mozilla-related domains.
-When the size of the community grows bigger and requires more channels to stay connected with the latest updates, this is the time a community website should be setup. Regional community should publish the goals that they wish to achieve through the community website.
-= Why should you do it? =
+Mozilla will only own the administrative part, but the community is responsible and owns any changes and decisions to it and its subdomains. At the moment of the request the requester should provide a document describing how the community is organized to be sure he’s the right person to own this request.
-"One of the most important components of every community is a website. Our research indicates that building and maintaining a website  is one of the most challenging and time consuming aspects of working with a community. It's especially visible for smaller communities. For  them, web design, website deployment, and keeping the web software up to date  is a blocker to productivity that sharply reduces time they can    spend  on actual goal of their community." -- https://wiki.mozilla.org/MCS
-= How can you do it? =
+'''Will Mozilla modify the domain or its content without community approval?'''
-== Step 1: Choose a domain name ==
-Every good site needs a good domain, but picking that domain can be quite difficult. You have a few options with a Mozilla Community Site:
-    * mozilla.country: mozilla.jp, mozilla.ro, etc.
-    * mozilla.org.country: mozilla.org.il, mozilla.org.tr, etc.
-    * mozilla-country.org: mozilla-mexico.org, mozilla-uk.org, etc.
-    * Something completely different: aviary.pl, camp-firefox.de
-Still stuck for ideas? http://mozilla.org/community/directory.html might help for inspiration.
-== Step 2: Decide on your hosting needs ==
+No. While your domain will be at Mozilla’s Domain Registrar and Mozilla Domain Name Servers, Mozilla will not modify the domain without approval or direction from the domain’s Technical Contact.
-Without hosting, even the most brilliant domain name fails to deliver anything. So, next, you have to work out what your hosting needs are. This is no simple task, so answer these questions in preparation for step 3:
-    * How many people are (or will be) accessing your site?
-    * What is the internet usage population in your country?
-    * What bandwidth requirements will you need to be provided by your hosting partner?
-    * What is the cost for monthly, semi-annual, or annual service?
-    * How do you intend to increase users to your site?
-== Step 3: Contact William or Pierros ==
+The Mozilla Reps Council will work to ensure that this policy is followed.
-{{admon/note|Changes imminent|This step is about to change as Community IT team takes over}}
-Finally, email william@mozilla.com or pierros@mozilla.com describing your plans for a community website, including your decision on a domain name and your hosting needs.
-= Examples =
+'''Can I still use my own DNS instead of mozilla’s one?'''
-Here are some great examples of community-driven sites hosted by third-party services.
+Yes, you can request to use your custom NS to handle the domain zone instead of Mozilla’s one.
-*  [http://moztw-z.wikidot.com/ Mozilla Taiwan]
+For various services, you may be required to delegate a sub-domain NS RR to Mozilla. This allows Community Ops greater flexibility in managing the service.  For instance, you may be asked to delete your blog site to Amazon’s Route 53:
-*  [http://www.mozilla-hispano.org/ Mozilla Hispano]
-*  [http://www.mozillapl.org/ Mozilla Poland]
-*  [http://www.mozilla-russia.org/ Mozilla Russia]
-*  [http://www.mozillaitalia.it/firefox/ Mozilla Italia]
-= More Ideas =
+<pre>blog.communitysysadmins.org. IN NS ns-277.awsdns-34.com.</pre>
-== Web Apps ==
-Every website you see on the Internet is either a plain HTML document or an application that created HTML pages dynamically and presents them to the read (webapps).
+'''Can I request any type of hosting?'''
-These days we tend to use web apps everywhere. Examples of webapps are: forum, web mail system (Gmail), blog, site with news etc.
+Yes! The Community IT Operations  team will be happy to work with you to find the best solutions for your needs.
-= Getting your request approved =
+[[Category:Remosop]]