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: @@
-== Web Hosting ==
+{{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.}}
-To have a website, you have to find a space on a machine called a server to store the website there. You can buy such service from one of many hosting companies.
+{{Remonav}}
-Mozilla can help Mozilla Reps by hosting your website on Mozilla servers.
+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].
-Hosting is server space that your community will need when it starts to become more prominent in its locale.  When you are ready to launch a site, your team will need to secure a web URL from a URL provider and then you will need to that URL at a server that will host your community content.  Unfortunately, Mozilla does not have the resources or the legal clearance to host all Mozilla community websites.  But, Mozilla have been able to help locales in the past with hosting.  Therefore, you will need to find a local partner and get hosting service set up for your community
+==General requirements==
-Here are some great examples of community-driven sites hosted by third-party services.
+This are the general requirements evaluated in any request:
-*  [http://moztw-z.wikidot.com/ Mozilla Taiwan]
+* The following questions should be answered: Why this request is it needed? How does it benefit Mozilla mission?
-*  [http://www.mozilla-hispano.org/ Mozilla Hispano]
+* The request coming from a known Mozilla community member.
-*  [http://www.mozillapl.org/ Mozilla Poland]
+* 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.
-*  [http://www.mozilla-russia.org/ Mozilla Russia]
+* There is an established project/community (+6 months) supporting the request, already running in production stage.
-*  [http://www.mozillaitalia.it/firefox/ Mozilla Italia]
+* There is at least 2 people on the project responsible for the request and as main contact point.
-In some cases, Mozilla has been able to support our communities by subsidizing (or even fully covering) the cost of the hosting.  In every case, Mozilla looks for the highest leveraged opportunity to support its community.  With limited funds and a need to scale, Mozilla will always look for that opportunity where impact will be amplified to help the greatest amount of people.  We very much use this idea when looking at each request for hosting support.
+==Domain Name==
-You may request support with hosting by [mailto:william@mozilla.com emailing William Quiviger].  In preparation, you should be able to answer questions like:
+* Full fit general requirements.
-*  How many people are (or will be) accessing your site?
+==Hosting==
-*  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?
-These questions are meant only to show the level of impact you hope to have and answer the question of leverage that Mozilla will ask.
+* 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.
-== Domain Name ==
+==Email==
-Setting up a website requires you to select a domain name for your website. Domain name is an address to your website like johnsmith@'''domain.net''' or www.'''domain.net'''. It's strictly related to selecting a name for your project, and in result may require time. Because domains costs, we offer you a temporary solution at the beginning to set up a domain inside our domain like ''''yourdomain'''.communities.mozilla.org. You can use it for some time until you find out the name for your community/project and setting up a domain on your own.
+* The domain name for the emails is already transferred to Mozilla.
-If the domain is related to Mozilla project, Mozilla may help you by financing domain buyout and yearly payment. You should also be aware of several rules regarding using mozilla word in your project/domain name.
+==SSL==
-* Use free domain from your provider (like polish *.art.pl or *.fsf.hu)
+* The domain name for the website is already transferred to Mozilla.
-* Buy a domain (we can buy it for you!)
-* Request for a subdomain in *.communities.mozilla.org / *.mozilla-communites.net
-== Web Appls ==
+==FAQ==
-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).
+'''Why does the domain name need to be transferred to Mozilla?'''
-These days we tend to use web apps everywhere. Examples of webapps are: forum, web mail system (Gmail), blog, site with news etc.
+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.
-MCS project provides you with a set of tools that you can use to build your websites. We intend to make it easy to install them on your own, and we will try to build an automated installer that will let you avoid the pain of learning web application development if you cannot afford it. (Although we do recommend using this opportunity to learn new, practical skill in a comfortable and helpful atmosphere of Mozilla project)
+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.
-There are many kinds of web applications, but for the basic community website we identified 4 kinds of tools: CMS, Forum, Wiki and Planet of blogs.
+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.
-You may choose to use any of them or all of them for your website. You can use other tools, but then you have to rely on your knowledge or external resources.
-Currently you can find documentation of the project at [https://wiki.mozilla.org/MCS https://wiki.mozilla.org/MCS].
+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:
+<pre>blog.communitysysadmins.org. IN NS ns-277.awsdns-34.com.</pre>
+'''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.
+[[Category:Remosop]]