Reps/SOPs/Digital resources: Difference between revisions
No edit summary |
No edit summary |
||
| Line 29: | Line 29: | ||
* How do you intend to increase users to your site? | * How do you intend to increase users to your site? | ||
== Step 3: | == Step 3: File a bug == | ||
{{admon/note|Changes imminent|This step is about to change as Community IT team takes over}} | {{admon/note|Changes imminent|This step is about to change as Community IT team takes over}} | ||
File a bug for [https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20Reps Mozilla Reps on Bugzilla] and select '''Community IT request'''. Once you get the approval from the ReMo Community IT task force, Mozilla's IT team will take care of it and follow-up with you. | |||
= Examples = | = Examples = | ||
Revision as of 15:13, 20 July 2012
Main | Join | Procedures (SOPs) | Leadership (Resources) | Meetings | Website | FAQ
Who should create a community site?
A Mozilla Representative on behalf of his/her local community with prior consensus from that community + A mentor/ or Council can vouch.
When should you do it?
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?
"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?
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
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: File a bug
This step is about to change as Community IT team takes over
File a bug for Mozilla Reps on Bugzilla and select Community IT request. Once you get the approval from the ReMo Community IT task force, Mozilla's IT team will take care of it and follow-up with you.
Examples
Here are some great examples of community-driven sites hosted by third-party services.
More Ideas
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).
These days we tend to use web apps everywhere. Examples of webapps are: forum, web mail system (Gmail), blog, site with news etc.