Difference between revisions of "Oversight Board/2018-2020-candidates/Rahul Bothra"
m |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
Hi everyone, | Hi everyone, | ||
| − | I am Rahul Bothra (pro-panda) | + | I am Rahul Bothra (pro-panda). |
| − | + | '''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. | ||
| − | |||
'''Currently in the SLOB meetings,''' | '''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. | * A lot of the members are inactive. They don't attend the SLOB meetings or reply to motions, crippling our progress. | ||
| − | |||
* 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 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 | * 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 | + | * 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:''' | '''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. | * 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 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 | |
| − | |||
Latest revision as of 00:11, 30 November 2018
Hi everyone, I am Rahul Bothra (pro-panda).
My contributions,
- Active code contributor; also working on Port to Python 3 project
- 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.
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.
- 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 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:
- 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.
- Make sure everything (except any decision concerning only the board) are taken publicly and in an open environment