Would love to rephrase some parts.
Sent from Mobile sorry for typo
People who are documenting are not just loving the documentation part. They
wanted to make sure what they have learnt and doing is shared to all. once
I have tried to ask documenting the things in MozillaIN blog also, but
there was some difficult faced by contributor and even once I tried to
write a post was very difficult to get started and getting permission then
promoting the post in social media. I would suggest give rotational author
permission to write in Mozilla India blog for functional teams, like for
rust this month Vignesh, next month Abhiram, then Mehul and so on they may
love to share their thoughts to bigger audience, similarly for webvr,
WebExtensions, and so on. This way MozillaIN blog will see lot of
engagement.
I personally know many contributors who started QA contribution in India.
Mentors like chandrakant ji, Swarnava helped people like Prasanth who are
contributing now. If you need any help always Madhuri is available to help
in QA (both automation and manual testing) and has invited us to do test
pilot adoption and testing many times.. I know some people like
Surentharan, Fahima got help from Prasanth and they sometimes help to
document things. If anyone need to write blog on that MozillaTN website you
can come to me I am (or any other org admins) Happy to accept your pull
request.
We should not say contributors contributing to social media is not
welcomed. Our MozillaIN social media engagement is really high and we can
very well see during privacy campaign each year. Efforts are done well in
past and is continuing till day. During one of the Mozilla India community
meetup we had video call with our mom and brought very good traction to
in-built video call feature. Many things are learnt from those
contributors.
Only one thing what many may be lacking to understand is how strengthening
regional community is helping to bring strong single MozillaIN community.
To explain this I would like to share a small thing what happened in
Tamilnadu.
Previously lot of colleges had their own website, own Facebook page,
Twitter handle. One thing was clear, when something (an announcement about
new features or near by meetups) has to be shared it was difficult to do.
So first thing we did was bring all the pages under single MozillaTN page
and most importantly all the club leads had editor access to the page. So
this helped us to make sure all the events done at one college is shared to
another college also. Then websites were not linked properly and ownership
is not transferred, so we invited students who were having their college
website to build and push to MozillaTN repo, this way Currently website
team can give access to any one in that college to write blog and
transition is very easy. One way or another each website was connected to
each other using disqus comment and connection is very strong and everyone
knew what is happening there.
Finally we wanted to have close connection with up coming contributors. Yes
Makilan shared birthday wishes to our community members in social media (
we can't do it in MozillaIN social media handle as it may look spamming) it
made sure the contributor is very close to Mozilla community.
The way of thinking may need to be changed.
We have scaled very well, to balance the load we need many smaller
components which all together make one big successful thing.
Think of this, all the event request goes to Mozilla community at SFO, then
it comes to India since we are near, then it comes to reps who is in that
region. If only this is correct way then that event might have not even
happened. But to make things bit faster we had a contact point MozillaIN
where we were asking lot of event request, and all contributors made sure
they travel whenever they were free and built very strong diverse community
all over india, then again after sometimes the number of events in regions
gets increased , so regional community started websites and made sure
processing is faster.
Finally MozillaIN community is stronger and are creating more leaders by
having various on boarding process who can again create more leaders. Only
one thing we miss is to understand this and also documenting it in blog.
The reason for lack of documentation is very simple, it's difficult for
many to get access.