5
edits
Psubhashish (talk | contribs) (→Ideas: added two more that came before Dec. 24) |
(→Ideas) |
||
| Line 185: | Line 185: | ||
# One of the major things I am going to do over here is, in today's Mozilla India, if we have any grievance, we have to express it only to a limited number of Mozillians in India. This isn't good, keeping in mind that most of the issues that come up are due to an experienced Mozillian. And most chances are that the senior Mozillian in question is a good friend of the limited number of Mozillians to whom the grievances have to be raised. So, the issue quickly gets submerged and there is no follow up and no kind of action is taken against the senior Mozillian for his/her wrong deeds. | # One of the major things I am going to do over here is, in today's Mozilla India, if we have any grievance, we have to express it only to a limited number of Mozillians in India. This isn't good, keeping in mind that most of the issues that come up are due to an experienced Mozillian. And most chances are that the senior Mozillian in question is a good friend of the limited number of Mozillians to whom the grievances have to be raised. So, the issue quickly gets submerged and there is no follow up and no kind of action is taken against the senior Mozillian for his/her wrong deeds. | ||
# My plan is to come up with a system where in, the grievance can be sent out to the other Mozillians who, the junior Mozillian is pretty sure will not be affected by the senior Mozillian and the junior Mozillian should be able to share his/her concerns with ONLY the other Mozillians (the grievance report should not go to the senior Mozillian or his/her friends(pretty much like blocking)). What this will ensure is a transparent and non-biased. Once a decision has been reached as to whether the Senior Mozillian in question is actually at fault or not, the message can be conveyed to them and they should have a way to see the discussion at the end so that they can have their opportunity to justify their actions and is not one sided. | # My plan is to come up with a system where in, the grievance can be sent out to the other Mozillians who, the junior Mozillian is pretty sure will not be affected by the senior Mozillian and the junior Mozillian should be able to share his/her concerns with ONLY the other Mozillians (the grievance report should not go to the senior Mozillian or his/her friends(pretty much like blocking)). What this will ensure is a transparent and non-biased. Once a decision has been reached as to whether the Senior Mozillian in question is actually at fault or not, the message can be conveyed to them and they should have a way to see the discussion at the end so that they can have their opportunity to justify their actions and is not one sided. | ||
; ---ADDED POINTS--- | |||
#The points noted by the members are actually interesting as they have been able to highlight the problems and solutions for the same in their own geographical groups or have been able to give a broad array of ideas that we, as Mozilla India, can implement to make this community a very efficient community. But I had a few extra thoughts in my mind. Here they go: | |||
##Viswaprasath in his comments, put out that he wants to start a new Focus group for Addons and this discussion did even come up in the Future Technologies and Products Telegram group. All the members of the group thought it was a good idea and we all supported the effort. But what we all failed collectively is the fact that as per the Details of the team structure, we already have a focus group for Addons and none of us knew about it and we blindly thought about the idea without doing any kind of due diligence.(Note, even I was part of this failure and I realized it when I was preparing for the event out here in Hyderabad). This clearly means that the Mozillians who didn't participate in MInM(and even most of the Mozillians who participated in MInM) have no idea about the existence of the groups. This, I feel, is pretty much similar to Mozillians not knowing the real responsibilities of the Meta Team, as suggested by Ankit and Dyvik apart from the existing Provisional Meta Team. | |||
###What I feel is that we have many geographical groups and we have members from all the geographical groups who were a part of MInM, and it wouldn't be difficult to get the list of people who were part of the same. If we can get that, we should start a process of regrouping the MInM team and having all the geographical groups organizing community-enabling events in their geographical areas and having all the functional and focus groups' events so that the Mozillians who weren't a part of MInM get to know all the possible options for contributions and these geographical groups would surely need support of other communities as no one community is fully self-sufficient right now, as much as I understand. If we can somehow decentralize the whole hierarchy(it is already decentralized on papers but not in effect yet), that would be the ideal thing to happen. | |||
###For example, Dyvik, I and Aastha(What I would like is that not only 3 people but all the people who are willing to contribute should be able to give suggestions openly) have been having very good number of discussions on this and we did come to pretty much the same conclusion and we are organizing an event in Hyderabad where many of the functional and focus groups' work will be shared and fresh talent can be brought into Mozilla and we can again accelerate Mozilla and bring Mozilla India to the efficiency it once had. This event is not the end but a beginning to the whole reboot process. Similar kinds of events have to happen all around India and we should be able to expand the scope too, and not just stick with a few topics being repeated every time. | |||
###If something like that happens(I would like you to read all the points raised by the other respondents of the activity), you can see that most of the comments of 'having WebVR sessions' or Rust sessions or similar type of comments gets accommodated. | |||
##Apart from that fact, we also have to take the points raised by Subhasis Chatterjee pretty seriously too, as he has raised very much valid points over there for the long term growth and stability of Mozilla India. But I would maybe want to have a discussion on his point no. 2 which states we must take in new members to the core group based on his interests, without judging his/her technical skillset. I would say we should take in Mozillians who are interested and do have at least a bit of track record in the back pack, as if a person who is very much knowledgeable in Designing, Marketing, etc. wants to enter the Rust focus group but has no experience in coding whatsoever, we should probably guide him/her for a few weeks first and when he/she is ready, we can onboard him/her. Similarly, if a person does not know designing at all but is very much interested in it, designing isn't something that can be thought to a person easily. So, that person would not be the ideal member for the team. Maybe he/she would be ideal for some other team and we should be able to guide him/her. | |||
; 9. Subhasis Chatterjee | ; 9. Subhasis Chatterjee | ||
edits