Jump to: navigation, search

Summer of Code/2018/Making a Beginner Guide

249 bytes added, 12:51, 16 March 2018
Counterpart the Risks
'''Bold text'''===Project and the community===#*'''If your project is successfully completed, what will its impact be on the Sugar Labs community?'''
::* If the project is successful it will be of huge help for new developers to SugarLabs as well as establish all the documentation at one place in a well-organized way. This will also give first-time users a pleasant experience as they wouldn’t have to figure out all the procedures by themselves.
::* FAQ’s like “How to download the Sugar labs projects” and “how to start contributing” would be taken care of at a single place in a decently organized way.
::* Sugarbot will be a new project to Sugar labs which could be further expanded and embedded within our chatting and mailing channel.
::* In future, it could also be utilized for assigning issues thus increasing automation and productivity. There seems to be a lot of scope for Sugarbot’s expansion.
#*'''What will you do if you get stuck on your project and your mentor isn't around?'''
::* I will try to resolve the issue myself by looking it up on Google, StackOverflow etc.
::* Read the documentation of the tool in which problem occurs.
::* Contact other SugarLabs members through IRC, developer mailing lists
::* If the problem is still not resolved, I will engross myself on some other module to keep the things rolling and wait for my mentors to help me out.
#*'''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?'''::* Convey daily work to my mentors::* Daily updates on IRC::* I will keep posting updates on my work on the developer mailing as per requirements::* I’ll update my weekly work on either Github or BitBucket::* Keep my work well documented for the community.
===Other Commitments===

Navigation menu