Hi all,
On Mon, Nov 28, 2011 at 11:20 AM, Vineel Reddy Pindi <
pindivin...@gmail.com> wrote:
> Hi Kinshuk, Thanks for sharing your ideas for Mozilla in India.
>
> Thanks so much, Hari, Anup, Arun, Sai Kiran for your feedback! We'd
> definitely need your help in going forward.
>
> Srikar and Pavan, Thanks for your interest in Mozilla. Please look for my
> email that i will be sending you shortly.
>
Thank you Axel for the suggestions!
I realized, the reply i sent to this thread got bounced! So here i am
sharing it again:
Absolutely agree with Kinshuk on having synchronized all India campaigns
and collaborating with other Communities.
Regarding the executive body for the community, its a bit early for us to
have such a body/council and it may bring unwanted complexity, i personally
feel that. At first, we may want to focus on:
a.) the areas of contributions: For this we need members who can take
responsibility of respective functionality and be a mentor for any new
member who want to participate in that area.
b.) growing and nurturing the community: For growing the community at
regional level, Mozilla Reps program [1] is the best way to go. Mozilla
reps because, as of now we have infrastructure/resources to support reps.
Reps are encouraged to build-on and support existing/future local community
efforts and programs. We should aim to have at-least one regional leader
per state/region. Please note that, Mozilla reps program DO NOT replace or
undermine efforts by existing community of Mozilla volunteers.
Community growth can be seen when there is development at an individual
level. Mentoring/nurturing is important for growth.
Based on the key finding from Mozilla Hispano community [2], which is one
of the largest, active and veteran regional communities, we can have a
organizational structure for Mozilla India in two phases:
Mozilla India regional community:
The regional community can be structured based on set of project areas to
which contributors are assigned. The internal activities of the members of
the project can be described as below, and any community member can be part
of it by participating in it.
- User: Anyone visiting the project.
- Contributor: User who contributes and helps the project to proceed.
- Committee Member: Active contributor who has the right to vote in the
decisions of the project.
- Mentor: Contributor(may have experience/expertise in a area) with
their experience can guide newly joined community members. Mentors help
mentorees become future mentors.
Phase I:
Open various areas of contribution at Mozilla India
1. Technical Management: Access to the housing master control,
databases, disk space, use of bandwidth and CPU, installation,
configuration and management modules, and support other areas responsible
for the management modules.
2. Moderation: Defining hierarchies of forums and mailing lists,
moderating role assignment most active collaborators, moderating forums,
answers to queries.
3. Documentation: Control and organization of the wiki documentation,
review of contributions from other members, developing and maintaining
FAQs, incorporating produced answers to common questions in forums and
mailing lists. Preparation of tutorials.
4. PR: Writing articles, news gathering and translation of Mozilla
community sources in English (Mozilla Foundation, Mozilla Links, ...),
translation teams update product information at home, organizing
regular meetings on IRC.
5. Labs: Development of projects and assists users in the
development forums.
6. Marketing: Spreading the word, marketing campaigns, events and all
kinds of coordination to promote Mozilla in India.
7. Localization/L10n: Help making Firefox, Thunderbird and other
projects available
in Indian language <
https://wiki.mozilla.org/L10n>s. Also help tell
your people about how Mozilla is building a better Internet by translating
content <
https://wiki.mozilla.org/L10n:Web_parts> on Mozilla web sites.
8. Design: We believe in the power of well-made and widely distributed
art, and want to make it possible for artists to cover the web and
people with designs inspired by Mozilla.
9. Support: Help users get the most out of using Firefox and other
Mozilla projects.
Step 1. A ‘Provisional Mentoring Body’ can be invited to take charge of
each area in Phase I, based on their recent(past 6 months) contributions to
Mozilla in India.
Step 2. Community members take responsibility at respective area of
interest. Each area will have one mentor in-charge + a set of contributors.
Mentor's encourage contributors to document his/her activities during this
period to learn and grow accordingly.
Step 3. A community member should actively participate for three months in
any area of interest, in order to be proposed as a ‘Committee
Member’(official member). These members are entitled to take decisions/
vote at respective areas at Mozilla India.
In areas without mentors/responsibility, it will be among several members
who want to help when making decisions about the area, all of them must
vote to agree (simple majority). That is, members from the committee form a
responsible staff, but having to agree on everything they do between them.
The goal of Phase I, is to let every contributor/community member have a stake
in the regional community - Mozilla India.
Phase II:
Once we have a dedicated enthusiastic team contributing on various areas.
These active community members + the provisional mentors can apply for the
next term(6 months or 1 year?).
Committee Member
- How do one qualify an contributor as a member entitled to vote?
- A contributor who during a period of not less than three months remain
contributing to the project may be proposed as a member with voting
rights, both by himself and by any of the current voting members.
- After that, the current 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.
- The control need not be exhaustive, but if someone raised doubts
about the legitimacy of the voting power of another member.
- 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
charge). This fact must be communicated by concerned himself to be
considered as an absence and not lack of cooperation.
- If a member wants to leave the committee, we may vote for a new
proposed member to replace the former. The former member lose their status.
- 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 an contributor as a member entitled
to vote?"
Mentors
A mentor is a contributor(may have experience/expertise in a area) who
voluntarily guide new community members providing information,
collaboration tools and knowledge to promote and encourage their
participation in the project, so this is as active and fulfilling possible.
Requirements to become a mentor, a mentor must meet at least some set of
requirements:
- Bring in the community long enough to know all its internal
organization.
- Having worked in the Community at least one project.
- Have basic knowledge of the area pretending to be a mentor.
- Show initiative and personal treatment facility.
- Mentors help mentorees become future mentors.
To mentor listed as "official", the person must communicate with any other
current mentor area and spend time as a co-mentor before becoming a
mentor.This means that the first rookie will take together and guided by
the current mentor, who will teach the basic mechanisms for the role of
mentor.
Responsibilities
- Each area will have one mentor in-charge and a variable number of
contributors. Preferably, it will prevent a single community member
responsible for several areas.
- The role is responsible for defining tasks, prioritize to get the best
possible progress and review its implementation. Mentor can also
collaborate to drive the execution itself, but should not be their main
task.
- The mentor has the final decision in case of conflict in the
respective area. If the conflict still arises, the case/issue should be
taken to Committee panel. Decisions taken under this point must be
consistent with the previous objective of securing the best possible
progress in the area.
- Responsible positions shall be elected every six months(?). A
mentor/contributor who hold a position of responsibility will be eligible
for re-election. In the election of each area will vote all voting members
of the project, but be limited to the census of an area to contributors in
that area.
- Whoever takes over an area, have temporary leeway to decide what to do
and what not to do with the perspective that every so often assess what has
been done and what is not. Specifically, the veto it has to add things and
in no case be removed functionality in an area without an absolute majority
of the members of the project. By the time of voting, if the person is very
nice but rejected ideas that require a lot of effort without a reasonable
number of volunteers, or just crazy ideas, should have no problem retaining
his office. In turn, the proponent of these ideas is encouraged to look
like, as well as an idea, a commitment to take it forward. Records forums,
mailing lists and wiki should serve to make a fair trial.
Thanks again, Kinshuk for bringing this up. I am very happy that we are
discussing these things. :)
All kinds of suggestions, comments are welcome!
Regards,
Vineel
[1]
https://wiki.mozilla.org/ReMo
[2]
http://www.mozilla-hispano.org/