Confirm
128
edits
Changes
Created page with "<div style="clear:both; border: 2px solid rgb(40, 40, 40); text-align:center; padding: 2px; background: #ffffff; border-collapse: separate; -moz-border-radius: 10px; margin-top:2..."
<div style="clear:both; border: 2px solid rgb(40, 40, 40); text-align:center; padding: 2px; background: #ffffff; border-collapse: separate; -moz-border-radius: 10px; margin-top:20px;" >
[[NeMo|Home]] | [[NeMo/Workflow|Structure & Governance]] | [[NeMo/People|People]] | [[NeMo/Articles|Articles]] | [[NeMo/Meetings|Meetings]]
</div>[[Category:Nemo]]
__NOTOC__
People working on this project shall be classified into 3 Team Categories
#'''Content Writers''' - Major resource contributors – write articles in English mostly.
#'''L10N teams''' – Translate the articles written into the local languages. We shouldn’t translate the articles word by word, but must write them to suit the local taste, retaining only the essence of the content, so we can reach the readers better.
#'''Media Outreach''' – People who work on getting Media contacts, bloggers, magazines, volunteers etc. and also gather feedback from them once articles start to get published and give their feedback and suggestions to the Content Writer Teams and L10N teams appropriately.
These teams above shall be monitored and mentored by a '''Core team''' that shall include people from our very own Mozilla PR.
== Organizational Structure ==
<br>
[[Image:Nemoworkflow.png|center]] <br>
* The '''Core Team''' shall monitor the whole process. The committee that forms the Core team shall consist of a Head-Leader to each of the Media outreach, Content writer and L10N teams and people from Mozilla. They take decisions critical to the whole project – appointing new leaders, changes to organizational process etc.
*'''Each of the three teams shall be headed by a group of Team Leaders''' (with a head leader, from the Core) who will mentor and monitor the progress of their respective team.
*#Actions of the volunteers shall be authorized and their contributions shall be recognized by the Team leaders.
*#Any malpractice of the code of conduct and misuse of the freedom of his/her volunteer team member(s) shall be reported immediately to the Core Team.
*# Give termly reports on their team’s progress to the Core team
*'''The Media Outreach Team''' will see through that the articles get published in various newspapers and magazines.
*#The Media outreach leaders will need to approve for their volunteers – ('''who necessarily need to be a communications rep''') to reach the Press and other media before publishing.
*#Leaders along with their volunteers who publish content shall gather feedbacks from the Press/Print media and give them to Content Writers’ Team Leaders, L10N Team leaders and the Regional Localization Leader for the particular publication.
* '''The Content writers’''' team is the most elite group of the project. They form the backbone. They come up with topics to write articles upon, do them in simple English.
*#The Team Leaders/Editors of the Content Writers Group will need to approve the articles written by the volunteers to get them moved to Mozilla Wiki.
*#They work closely with their volunteers – '''who may or may not be Communication Reps.'''
*The '''L10N Teams''' shall look after translating the articles into local languages. Team leaders appoint and monitor regional localization leaders who look after translating content into local languages.
*#Regional Localization Leaders (RLL) will need the approval of the L10N Team leaders for their articles to get moved to Mozilla Wiki.
*#RLLs again, acknowledge and recognize their local volunteers and suggest to appointing new RLLs.
== Implementation and Incentives ==
<br>
'''All the articles written and approved shall be published in the Mozilla Wiki'''
We definitely need to acknowledge and recognize the selfless contribution of the passionate volunteers who have worked hard towards attaining our goal. In that regard,
#There shall be a points table to each of the contributor. The more contribution that he/she makes, the more points they get. This shall be viewed in carefully by the Core Team and if found appropriate, based on feedback from the existing Team leaders and the work put in by the volunteers, he/she shall be made one of the Team leaders of that group
#Awesome Comms Reps Swag for all contributors above certain points!
#A letter of recognition from Mozilla.
[[NeMo|Home]] | [[NeMo/Workflow|Structure & Governance]] | [[NeMo/People|People]] | [[NeMo/Articles|Articles]] | [[NeMo/Meetings|Meetings]]
</div>[[Category:Nemo]]
__NOTOC__
People working on this project shall be classified into 3 Team Categories
#'''Content Writers''' - Major resource contributors – write articles in English mostly.
#'''L10N teams''' – Translate the articles written into the local languages. We shouldn’t translate the articles word by word, but must write them to suit the local taste, retaining only the essence of the content, so we can reach the readers better.
#'''Media Outreach''' – People who work on getting Media contacts, bloggers, magazines, volunteers etc. and also gather feedback from them once articles start to get published and give their feedback and suggestions to the Content Writer Teams and L10N teams appropriately.
These teams above shall be monitored and mentored by a '''Core team''' that shall include people from our very own Mozilla PR.
== Organizational Structure ==
<br>
[[Image:Nemoworkflow.png|center]] <br>
* The '''Core Team''' shall monitor the whole process. The committee that forms the Core team shall consist of a Head-Leader to each of the Media outreach, Content writer and L10N teams and people from Mozilla. They take decisions critical to the whole project – appointing new leaders, changes to organizational process etc.
*'''Each of the three teams shall be headed by a group of Team Leaders''' (with a head leader, from the Core) who will mentor and monitor the progress of their respective team.
*#Actions of the volunteers shall be authorized and their contributions shall be recognized by the Team leaders.
*#Any malpractice of the code of conduct and misuse of the freedom of his/her volunteer team member(s) shall be reported immediately to the Core Team.
*# Give termly reports on their team’s progress to the Core team
*'''The Media Outreach Team''' will see through that the articles get published in various newspapers and magazines.
*#The Media outreach leaders will need to approve for their volunteers – ('''who necessarily need to be a communications rep''') to reach the Press and other media before publishing.
*#Leaders along with their volunteers who publish content shall gather feedbacks from the Press/Print media and give them to Content Writers’ Team Leaders, L10N Team leaders and the Regional Localization Leader for the particular publication.
* '''The Content writers’''' team is the most elite group of the project. They form the backbone. They come up with topics to write articles upon, do them in simple English.
*#The Team Leaders/Editors of the Content Writers Group will need to approve the articles written by the volunteers to get them moved to Mozilla Wiki.
*#They work closely with their volunteers – '''who may or may not be Communication Reps.'''
*The '''L10N Teams''' shall look after translating the articles into local languages. Team leaders appoint and monitor regional localization leaders who look after translating content into local languages.
*#Regional Localization Leaders (RLL) will need the approval of the L10N Team leaders for their articles to get moved to Mozilla Wiki.
*#RLLs again, acknowledge and recognize their local volunteers and suggest to appointing new RLLs.
== Implementation and Incentives ==
<br>
'''All the articles written and approved shall be published in the Mozilla Wiki'''
We definitely need to acknowledge and recognize the selfless contribution of the passionate volunteers who have worked hard towards attaining our goal. In that regard,
#There shall be a points table to each of the contributor. The more contribution that he/she makes, the more points they get. This shall be viewed in carefully by the Core Team and if found appropriate, based on feedback from the existing Team leaders and the work put in by the volunteers, he/she shall be made one of the Team leaders of that group
#Awesome Comms Reps Swag for all contributors above certain points!
#A letter of recognition from Mozilla.
