Change Details

From https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project#Reporting > Reporting is very important for the followers of your project, your mentors, and yourself. Investing a few minutes reporting on a weekly basis will save you a lot of time and energy. > > For the weekly reports, please create a Phabricator task and associate it with your project. Insert a table with the date and report columns in which you'll write your weekly report. Write your reports as telegrams, always linking to the areas of progress: tasks, patches, demos, documentation pages etc. It is better to deliver short or even incomplete reports on a weekly basis than trying to elaborate the best deep weekly report but then get stuck and not deliver it at all. Two good examples of weekly reports can be found at A sample: T100997

@allcandidates Weekly reports are a great means to document the progress of your projects, reflect on your learnings, share your work with the broader Wikimedia community & get feedback. Looking back at the collection of your GSOC posts years from now, you will feel accomplished & proud of yourself :) Weekly Reports (~15) for GSOC/Outreachy are due as indicated on the respective pages: https://www.mediawiki.org/wiki/GSOC17_WeeklyReports https://www.mediawiki.org/wiki/Outreachy/Round_14/WeeklyReports Once you are done writing a report, link it from the Updates section of the MediaWiki [[ https://www.mediawiki.org/wiki/Google_Summer_of_Code_2017 | GSOC ]] & [[ https://www.mediawiki.org/wiki/Outreachy/Round_14 | Outreachy ]] page.

From https://www.mediawiki.org/wiki/Outreach_programs/Life_of_a_successful_project#Reporting > Reporting is very important for the followers of your project,@allcandidates Weekly reports are a great means to document the progress of your projects, reflect on your learnings, share your work with the broader Wikimedia community & get feedback. Looking back at the collection of your mentorsGSOC posts years from now, and yourself. Investing a few minutes reporting on a weekly basis will save you a lot of time and energy.you will feel accomplished & proud of yourself :) Weekly Reports (~15) for GSOC/Outreachy are due as indicated on the respective pages: https://www.mediawiki.org/wiki/GSOC17_WeeklyReports > > For the weekly reports, please create a Phabricator task and associate it with your project. Insert a table with the date and report columns in which you'll write your weekly report. Write your reports as telegrams, always linking to the areas of progress: tasks, patches, demos, documentation pages etc. It is better to deliver short or even incomplete reports on a weekly basis than trying to elaborate the best deep weekly report but then get stuck and not deliver it at all. Two good examples of weekly reports can be found athttps://www.mediawiki.org/wiki/Outreachy/Round_14/WeeklyReports A sample: T100997Once you are done writing a report, link it from the Updates section of the MediaWiki [[ https://www.mediawiki.org/wiki/Google_Summer_of_Code_2017 | GSOC ]] & [[ https://www.mediawiki.org/wiki/Outreachy/Round_14 | Outreachy ]] page.