Differences

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

--- people:jane [2013-11-08 17:00] – typo jane
+++ people:jane [2015-10-05 15:55] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-=== Jane @ flossie2013 ===
+====== Jane ======
-//a log of a remote participant and her coffee cup.//
+I'm was born in Germany and lived and worked in Ireland before I followed the team of authors of a great
+book and moved to Edinburgh.
-** challenge#0 **
+Here some of my past projects:
-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.
+  * [[http://www.edinburghcanalfestival.org.uk/ | raft race]]
+  * [[http://vimeo.com/40813198 | facial motion tracking]]
-  * Discussed on IRC to branch of the [[http://flask.pocoo.org/docs/tutorial/setup/ |flask tutorial]] to introduce a section that explains how to seperate the config settings via from_envvar().
+  * [[ http://studio.sketchpad.cc/sp/pad/view/ro.9tLnq9fG8256B/latest | on screen tinkering also known as coffee && code]]
-  * Her coffee cup wispers that the discussion of "best practise" of flask is [[http://www.reddit.com/r/Python/comments/1phog0/im_writing_a_web_app_flask_tornado_and_would/ | still in development]].
+  * and critical design [[http://design-mensch.de/portfolio/humans.php | quantifying privacy ]] & the [[ http://edinburghhacklab.com/2013/10/tinfoil-hat-party/|tin foil hat party]]
-  * (maybe premature) Conclusion: Wait till the [[http://www.kickstarter.com/projects/1223051718/practical-flask-book-project/posts | flask book]] is out and progess on [[https://github.com/mitsuhiko/flask/issues/901| #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 [[https://github.com/mitsuhiko/flask/issues/908 | #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 [[https://github.com/mitsuhiko/flask/issues/908 |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. 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]].
-----
-You find me also on [[http://wiki.edinburghhacklab.com/irc| IRC]] or on twitter @_janem
+I'm on our IRC channel /mailinglist/[[http://twitter.com/_janem |twitter]]. Whatever finds you first.
+x Jane