Oversight Board/2018-2020-candidates/Rahul Bothra - Revision history

Pro-panda at 05:11, 30 November 2018

2018-11-30T05:11:31Z

← Older revision		Revision as of 01:11, 30 November 2018
Line 3:		Line 3:

	'''My contributions,'''		'''My contributions,'''
	* [https://github.com/search?q=org%3Asugarlabs+author%3Apro-panda Active code contributor]		* [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
	* Activity Maintainer for Flappy and CowBulls		* [http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055080.html Code reviewer] and activity maintainer
	* [http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055080.html ~~code~~ reviewer].		* GSoC' 18 student and GCI' 18 mentor
	* GSoC' 18 student ~~working on [https://summerofcode.withgoogle.com/archive/2018/projects/5320748025511936/ porting Sugar to Python 3].~~
	* 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 also concerned that we are functioning in an inefficient manner.

Pro-panda at 05:08, 30 November 2018

2018-11-30T05:08:41Z

← Older revision		Revision as of 01:08, 30 November 2018
Line 1:		Line 1:
	Hi everyone,		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]
			* Activity Maintainer for Flappy and CowBulls
			* [http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055080.html code reviewer].
			* GSoC' 18 student working on [https://summerofcode.withgoogle.com/archive/2018/projects/5320748025511936/ porting Sugar to Python 3].
			* 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 also concerned that we are functioning in an inefficient manner.

Pro-panda at 05:02, 30 November 2018

2018-11-30T05:02:08Z

← Older revision		Revision as of 01:02, 30 November 2018
Line 18:		Line 18:
	* 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		* 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.~~

Pro-panda at 05:01, 30 November 2018

2018-11-30T05:01:40Z

Pro-panda at 02:26, 30 November 2018

2018-11-30T02:26:04Z

← Older revision		Revision as of 22:26, 29 November 2018
Line 5:		Line 5:

	I am excited by our goals and our potential. But I am concerned that the way we are working is wrong.		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,'''		'''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.

Pro-panda at 02:25, 30 November 2018

2018-11-30T02:25:42Z

← Older revision		Revision as of 22:25, 29 November 2018
Line 4:		Line 4:
	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.		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.

	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,'''		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.		* 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		* There is a lot of talk, but there is not an equivalent amount of work done. We fail to properly materialise discussions

Pro-panda at 02:25, 30 November 2018

2018-11-30T02:25:21Z

← Older revision		Revision as of 22:25, 29 November 2018
Line 4:		Line 4:
	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.		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.

	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,		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.		* 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		* 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 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 GSoC and GCI organisation.

	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:'''

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

Pro-panda at 19:07, 27 November 2018

2018-11-27T19:07:54Z

← Older revision		Revision as of 15:07, 27 November 2018
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.

Pro-panda at 21:07, 24 November 2018

2018-11-24T21:07:10Z

← Older revision		Revision as of 17:07, 24 November 2018
Line 7:		Line 7:
	* 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.
	* There is a lot of talk, but there is not an equivalent amount of work done. We fail to properly materialise discussions		* 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, ~~but fail~~ to ~~reach the right depth~~		* 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.		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.
Line 14:		Line 15:
	* 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; prioritising tasks which are more important to us, and improving mentoring checks to ensure that mentors are active
	* Work on a roadmap of our goals across various domains and timelines		* Work on a roadmap of our goals across various domains and timelines, and try to make sure they are implemented

	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.

Pro-panda: SLOB Election Candidature - Rahul Bothra

2018-11-24T20:59:29Z

SLOB Election Candidature - Rahul Bothra

New page

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

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, but fail to reach the right depth

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; prioritising tasks which are more important to us, and improving mentoring checks to ensure that mentors are active
* Work on a roadmap of our goals across various domains and timelines

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

← Older revision		Revision as of 01:01, 30 November 2018
Line 4:		Line 4:
	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.		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.

	I am excited by our goals and our potential~~. But~~ I am concerned that ~~the way~~ we are ~~working is wrong~~.		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.
	* 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 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 ~~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:'''		'''What I will undertake once elected:'''
Line 17:		Line 17:
	* 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

	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.