Differences

This shows you the differences between two versions of the page.

--- people:jane [2013-11-08 16:53] – jane
+++ people:jane [2013-11-09 17:42] – jane
@@ Line 15: / Line 15: @@
   * How relevant is the issue?
   * What is status quo of the communication between release team and maintainer?
-  * Overview of other communication strategy of other web frameworks
+  * Overview of other communication strategies of other web frameworks
   * What signal could we be used to measure that the new communication strategy succeeded
 Implementation
@@ Line 24: / Line 24: @@
 === How relevant is the issue? ===
-Relevants is depending on person affected by the problem, in this case the flask installation maintainer. For this project, I am simplifying things and declaring everyone as a maintainer that obtained a copy of flask from this [[https://github.com/mitsuhiko/flask | github account]].
+Relevants is depending on the 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 requests to flask project. For this reason is using the fork counter of on github maybe misleading.
+I assume here that the maintainer that would benefit most from an improved release process is not regularly involved in the software development process of flask. Therefor this maintainer should have an options to quantify the trust that an announced release is actually from the current release manager of flask.
+Thanks to mattupstate I have a figure how many [[https://crate.io/packages/Flask/ | download requests]] have been made from the link on the [[http://flask.pocoo.org/ | 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.
+The cup whispers that the stat displayed is to small for Jane's clumsy courser to get hold of but admires neither the less option to compare the uptake of the different version.
+=== What is status quo of the communication between release team and maintainer? ===
+The release manager publishes the new version via https://pypi.python.org/pypi. In addition is flask released [[https://github.com/mitsuhiko/flask/releases| on github]]. In this project I would like to look in particular on the communication process or work flow of releasing a new version on pypi.python.org as this is the link provided on the project website.
+In addition does the release manager [[https://twitter.com/mitsuhiko/status/345464720574263296 |tweets about the new release]].
+The point that the [[https://caremad.io/blog/packaging-signing-not-holy-grail/ |author ]] makes here is that public key of the release manager would need to be included with the first time installation.
+People that install flask for the first time are not part of the scope of the challenge so I won't go into that. //Coffee cup: you just don't want to talk about a scenario where the first package is tampered with. (Maybe I don't want to wear the tinfoil hat longer then needed.)//
+The author and mitsuhiko agree that the web of trust isn't practical.
+On the other hand is the topic: the internet of things.
+Let's turn everyday object into indicator. Proposed idea: turn everyday decives into indicator of a new release.
+=== Implementation ===
+The video:
+[[https://vimeo.com/78989037 | of an everyday item turning into an release indicator]]
+=== Review ===
+Following the solution suggested in [[https://github.com/mitsuhiko/flask/issues/908 | #908]] ->email to the mailing list admin would have taken me 5min now I am considering if joined event: release and keysigning party would be the way forward to (re) engage the flask community.
+The cup mumbles "please consult your local hackerspace for all risc involved in running such an event."