Difference between revisions of "Oversight Board/2018-2020-candidates/Rahul Bothra"

From Sugar Labs
Jump to navigation Jump to search
m
Line 14: Line 14:
 
What I will undertake once elected:
 
What I will undertake once elected:
 
* Attend every SLOB meeting regularly
 
* Attend every SLOB meeting regularly
* Revamping how we conduct GCI and GSoC to attract more contributions; prioritising tasks which are more important to us, and improving mentoring checks to ensure that mentors are active
+
* Revamping how we conduct GCI and GSoC to attract more contributions as well as improve the quality of mentoring; making sure we prioritise tasks which are more important to us, adding more checks before adding developers, grooming of every task / project before it is added / selected.
* Work on a roadmap of our goals across various domains and timelines, and try to make sure they are implemented
+
* Make a clear roadmap of our goals for the next 2 years in each domain of code, outreach, design and content. Start towards implementation of those goals according to priority.
  
 
I would like support from the community for my candidature for the post as a SLOB member.
 
I would like support from the community for my candidature for the post as a SLOB member.

Revision as of 14:07, 27 November 2018

Hi everyone, I am Rahul Bothra (pro-panda). I am a Python Developer and code reviewer for Sugar Labs.

I was a GSoC' 18 student with Sugar Labs, and I worked on porting Sugar to Python 3. I continue contributing in terms of code, code reviews and as a mentor in GCI' 18.

I am excited our goals and our potential. But I am concerned that the way we are working is wrong. Currently in the SLOB meetings,

  • A lot of the members are inactive. They don't attend the SLOB meetings or reply to motions, crippling our progress.
  • There is a lot of talk, but there is not an equivalent amount of work done. We fail to properly materialise discussions
  • We don't have a concrete plan of our goals. We try to cover a lot of breath in our efforts, and end up working on things which are not related to our goals (eg: Sugar Social)
  • We drag work for a lot of time, (eg: ASLO v3) a direct result of inactive mentoring and checks during GSoC

I also feel there is a lack of concern about the number of developers working on Sugar and the activities. We are failing in attracting new consistent developers despite being a popular GSoC and GCI organisation.

What I will undertake once elected:

  • Attend every SLOB meeting regularly
  • Revamping how we conduct GCI and GSoC to attract more contributions as well as improve the quality of mentoring; making sure we prioritise tasks which are more important to us, adding more checks before adding developers, grooming of every task / project before it is added / selected.
  • Make a clear roadmap of our goals for the next 2 years in each domain of code, outreach, design and content. Start towards implementation of those goals according to priority.

I would like support from the community for my candidature for the post as a SLOB member.