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

(4 intermediate revisions by the same user not shown)

Line 1:

Hi everyone,

I am Rahul Bothra (pro-panda)~~. I am a Python Developer and [http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055080.html code reviewer] for Sugar Labs~~.

I am Rahul Bothra (pro-panda).

~~I was a GSoC~~' ~~18 student with Sugar Labs~~, ~~and I worked~~ on [https://summerofcode.withgoogle.com/archive/2018/projects/5320748025511936/ ~~porting Sugar~~ to Python 3]. ~~I continue contributing in terms of code, code reviews~~ and ~~as a mentor in~~ GCI' 18.

'''My contributions,'''

* [https://github.com/search?q=org%3Asugarlabs+author%3Apro-panda Active code contributor]; also working on [https://summerofcode.withgoogle.com/archive/2018/projects/5320748025511936/ Port to Python 3] project

* [http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055080.html Code reviewer] and activity maintainer

* GSoC' 18 student and GCI' 18 mentor

I am excited by our goals and our potential, but I am also concerned that we are functioning in an inefficient manner.

~~I am excited by 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

* Lack of concern about the number of developers working on Sugar and its activities. We are failing in attracting new consistent developers for it, despite being a popular ~~GSoC~~ and ~~GCI~~ organisation.

* Lack of concern about the number of developers working on Sugar and its activities. We are failing in attracting new consistent developers for it, despite being a popular organisation in the Google programs.

* The selection of mentors and organisation admins for Google programs is a closed process.

'''What I will undertake once elected:'''

Line 16:

Line 20:

* 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.

* Make sure everything (except any decision concerning only the board) are taken publicly and in an open environment

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

@@ Line 1: / Line 1: @@
 Hi everyone,
-I am Rahul Bothra (pro-panda). I am a Python Developer and [http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055080.html code reviewer] for Sugar Labs.
+I am Rahul Bothra (pro-panda).
-I was a GSoC' 18 student with Sugar Labs, and I worked on [https://summerofcode.withgoogle.com/archive/2018/projects/5320748025511936/ porting Sugar to Python 3]. I continue contributing in terms of code, code reviews and as a mentor in GCI' 18.
+'''My contributions,'''
+* [https://github.com/search?q=org%3Asugarlabs+author%3Apro-panda Active code contributor]; also working on [https://summerofcode.withgoogle.com/archive/2018/projects/5320748025511936/ Port to Python 3] project
+* [http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055080.html Code reviewer] and activity maintainer
+* GSoC' 18 student and GCI' 18 mentor
+I am excited by our goals and our potential, but I am also concerned that we are functioning in an inefficient manner.
-I am excited by 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
-* Lack of concern about the number of developers working on Sugar and its activities. We are failing in attracting new consistent developers for it, despite being a popular GSoC and GCI organisation.
+* Lack of concern about the number of developers working on Sugar and its activities. We are failing in attracting new consistent developers for it, despite being a popular organisation in the Google programs.
+* The selection of mentors and organisation admins for Google programs is a closed process.
 '''What I will undertake once elected:'''
@@ Line 16: / Line 20: @@
 * 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.
+* Make sure everything (except any decision concerning only the board) are taken publicly and in an open environment
-I would like support from the community for my candidature for the post as a SLOB member.