Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
people:jane [2013-11-08 23:46] – jane | people:jane [2013-11-09 17:42] – jane |
---|
=== What is status quo of the communication between release team and maintainer? === | === 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. | 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. | 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. |
=== Review === | === 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. | 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." | The cup mumbles "please consult your local hackerspace for all risc involved in running such an event." |
| |
| === Implementation === |
| The video: |
| [[https://vimeo.com/78989037 | of an everyday item turning into an release indicator]] |
| |
| |
| |
---- | ---- |
You find me also on [[http://wiki.edinburghhacklab.com/irc| IRC]] or on twitter @_janem | You find me also on [[http://wiki.edinburghhacklab.com/irc| IRC]] or on twitter @_janem |
| |
| |