This is an old revision of the document!
Jane @ flossie2013
a log of a remote participant and her coffee cup.
challenge#0 Find and contribute to an relevant issue to improve an open source software project e.g. flask and log your progress. Your timeframe for your contribution is from now till 2013-11-09 4pm.
- Discussed on IRC to branch of the flask tutorial to introduce a section that explains how to seperate the config settings via from_envvar().
- Her coffee cup wispers that the discussion of “best practise” of flask is still in development.
- (maybe premature) Conclusion: Wait till the flask book is out and progess on #901 is made and then try to make a tutorial about it.
- Checked recent submitted issues listed on flasks github account that would match my skillset. Opted for #908 as I recently worked a lot with different mailinglists and interested in a well documented software release process.
- Coffee cup makes a jump as my mentor CorneliaB gives the go ahead.
- Conclusion: I have a contribution idea. Yeah!!! (But no coffee in the office and missed the cake at the event.)
challenge#1 Create a proposal for a communication strategy to announce software updates to maintainer of existing flask installation. Background
- How relevant is the issue?
- What is status quo of the communication between release team and maintainer?
- Overview of other communication strategies of other web frameworks
- What signal could we be used to measure that the new communication strategy succeeded
Implementation
- Learn and apply ideas from software projects where maintainer routinely response fast to critical updates
- Set the current strategy in a metrics with the proposed strategy
Review
- Summarize the outcome & praise the giants
How relevant is the issue?
Relevants is depending on person affected by the problem, in this case the flask installation maintainer. Maybe even more specifically flask maintainer that are currently not regular making pull request to flask project. For this reason is using the fork counter of on github maybe misleading. Thanks to mattupstate I have a figure how many download requests have been made from the link on the website. A sign of good uptake of the new release would be indicated by a bigger number then the number of previous released. Maintainer perform a download and my tweet about flask and animate more people to try out the new version. On the other side is the number of download not equal with the number of installation. Some people might newer go further to installation or request a make a dublicate download request. A brief look at the state over time might indicate also if more download are performed after the current announcement made on the current mailing list.