India/community/task force: Difference between revisions

India/community/task force (view source)

Revision as of 21:05, 15 March 2013

2,623 bytes added , 15 March 2013

no edit summary

Vineelreddyp

Confirmed users

1,172

edits

@@ Line 1: / Line 1: @@
 {{DoNotEdit}}
 Each Area has a Task Force Team. Task Forces are groups of individuals with a similar interest who focus on a specific Area of contribution(SUMO, Localization, QA, Engagement, Web-Dev, IT ).
 * Each Task Force has a core contributor in charge to organize it and guide people interested in contributing to the area.
 * Each Task Force has Mentor(s) to help newcomers to get started in the regional community. Mentor's encourage contributors to document his/her activities during this period to learn and grow accordingly.
@@ Line 7: / Line 8: @@
 ** Each Task Force can have tasks, a small work that has to be done assigned to a contributor. Not mandatory to have big/complex infrastructure like bugzilla for these assignments.
 ** Each task has a description, person in charge, due date and status. They are listed on their corresponding area/project page and also in the profile of the person in change of it. This last thing it’s very important because it’s a way to friendly remind people they have something to do.
+* Projects:
+Every initiative is a new project, from “Localizing AMO” to “Improve site design” or “Tips and tricks for beginners”. Anyone can create a new project. Each task force can have any number of projects.
+====== Who can be part of the Mozilla India Task Force? ======
+Any contributor of Mozilla in India can choose to be part of the Mozilla India Task Force Team. The list of core-contributors and mentors will be listed at Mozilla India wiki and mozillaindia.org website. It will be on meritocracy basis for the work one do inside the regional community i.e. Mozilla India.
+====== How do one qualify as an core contributor? ======
+* A contributor who during a period of not less than six months remain contributing to a project(online or offline) may be proposed as a Mozilla India core contributor, by himself or by any of the members of the Task Force Team.
+* After a member is proposed, all the other core members must vote on the merits earned by the contributor to give approval, the negative votes must be accompanied by an objective explanation
+Accumulation of merit:
+* For the forums will have the quality (not necessarily quantity) of the interventions, performances spam cleaning, material responses, responses with reference to Frequently Asked Questions, etc..
+* For PR, In the news section will look at the news published and response time for the original story and creating their own articles.
+* In the area of documentation issues look and quality of written documentation.
+* There are active and absent members. All members are entitled to be absent for a period of time (up to 8-10 weeks in a period of 6 months) of the project for whatever reason, during this time, membership status (no change). This fact must be communicated by concerned himself to be considered as an absence and not lack of cooperation.
+====== How do one qualify as an contributor as a member entitled to vote? ======
+All the core-contributors get to be part of the decision making. These members will be entitled to take decisions/ vote at respective areas at Mozilla India.
+* The control need not be exhaustive, but if someone raised doubts about the legitimacy of the voting power of another member, the status can be reviewed.
+* Any member may at any time review the status of another member. In this case, evaluate the contributions of the member in the last six months and must be voted by an absolute majority of all members if you are repealing member status of the project. May regain its status on the basis of the above under "How do you qualify as an contributor as a member entitled to vote?"
 Below is the list of the task force teams with contributors, provisional owners and the mentors: