[p2pu-dev] Tech call notes - 9 May 2012

[Dirk Uys]

*Upcoming Release*

   - 21/22 May


   - robots.txt


   - some minor config changes


   - removing course organizers


   - email notification subject improvements


   - link to page enabling multi-task edit/create/delete/order added to
   challenges home page.


*Past Release*

   - 4 May


   - Bug fixes and other small improvements


++++++++++++++++++++++++++++


*May 9*


   - How do trello, tender (help.p2pu.org), and lighthouse integrate?


   - Two goals:


   - Simplify


   - Understand


   - Three tools:


   - help.p2pu.org


   - report bugs, ask for help, single point of contact for our users


   - -> keep it the one main point of contact


   - Lighthouse


   - tracking development tasks


   - has a lot of old content (may not be up to date)


   - *question ->* can we replace this with github issue tracker?


   - Trello


   - community feedback


   - dev work


   - planning for development


   - maybe only use trello for project pipeline and make github replace the
   other dev boards


   - Questions:


   - are we using others? github?


   - john mentioned that start using github for new bug reports


   - what about mailing lists?


   - Difference between issue tracker and trello


   - Issue tracker -> tracking bug reports ie click this and it doesn't work


   - Trello -> stuff we're committed to working on and are currently doing


   - Do users log bugs?


   - John: No, they submit bugs via help.p2pu.org -> this is the single
   point of contact


   - Moved this down:Philipp: +1, but right now they also log bugs (there
   is a link to lighthouse in the footer - see Zuzel's note below) Let's
   remove that and point to help.p2pu.org +1


   - Developers verify the issue (is it really a bug?) and then fix it or
   log it as a bug to be fixed.


   - Should contributors be able to create tickets?


   - All contributors / developers should be able to create tickets


   - I noticed that users log bugs on lighthouse as well (I thought we had
   moved all of that to help)


   - The 'Found a Bug?' link on the footer points to lighthouse (which can
   be changed) - should be changed to help --
   http://help.p2pu.org/discussions/problems#new_topic_form


   - However ultimatedly bugs that can not be solved inmediatedly should be
   moved to lighthouse since they are easier to manage there.


   - There is an 'Attach a Lighthouse Ticket' action on the right sidebar
   when support staff is looking at a discussions


   - Are trello and lighthouse in sync?


   - I don think we have integrated trello and lighthouse


   - trello is beaing used mostly for staff communication (with the
   exception of the work on the p2pu api)


   - lightouse is still easier to use by voluntary contributors and it is
   integrated with help.p2pu.org


   - Whats the difference between help and community mailing list?


   - help is help.p2pu.org with is our user support site (with single sign
   on with p2pu.org)


   - the community mailing list is a place to which some organizers,
   learners and people involved in moving p2pu fordward are subscribed


   - Project pipeline vs development trello boards


   - Dev board ->
   https://trello.com/board/development/4f3d1ecc3a1fad867ad57e76


   - Project pipeline = high level overview of projects and deadlines
   (sometimes checklists are used to provide more details about steps and
   progress)


   - Extra boards including dev board, challenge improvements board and
   p2pu api board go more in detail and can be assoicated with moultiple cards
   on the project pipeline


   - Project pipeline vs lighthouse?


   - project pipeline = where staff resources are focussed


   - lighthouse is a big repository of TODOs (feedback from p2pu community
   and users) which can at some point go into trello or could be takled by
   volunteers or could stay open for a long time


   - What about Github issues?


   - it integrates with the code


   - *Simplified setup:*


   - *(1) **How P2PU Support Works*


   - Single point of contact -> help.p2pu.org


   - If a support request comes in that is a bug we do this:


   - FIX IT -> Done


   - or Log it as a bug using the issue tracker that dev wants to use


   - report back on help.p2pu.org (or provide the link to the issue so that
   users can track progress)


   - always try to respond to people, even if we can't solve the problem


   - If a user sends an email directly to an individual or to a list:


   - forward it to help at p2pu.org


   - Make sure not to delete headers / edit message so that original
   authors get replies from the helpdesk


   - (2) Managing the development process


   - Store bugs and issues that need to be solved on github issue tracker


   - Volunteers can grab issues from here


   - Bugs


   - Trello project pipeline -> Overview of development "chunks" and where
   they are in the process


   - update during weekly tech call


   - Trello is where we store agreed specifications for what we build


   - Store screenshots, mock-ups


   - Link to background discussion on the dev list


   - Roadmap on wiki (dreammap? - what we would like to do)


   - updated once a month


   - higher level than trello


   - +1 -- i think that we need to consolidate a little. communication is
   spread across help, trello, lighthouse, mail, irc, etherpad, github, p2pu,
   etc


   - help - user help / non dev help


   - dev list - all dev discussions (like the API discussion currently
   happening on trello)


   - github - tickets/bug reports, code reviews +1


   - test https://github.com/benlangfeld/Lighthouse-2-Github if you are
   going to migrate tickets to github


   - I don't know if it will be possible to integrate help.p2pu.org with
   github --
   http://help.tenderapp.com/discussions/suggestions/660-github-issues-integration


   - trello - high level strategy/priorities - does this then need to be
   synced with roadmap on github wiki


   - *Next steps:*


   - Direct every user questions / bug reports to help.p2pu.org


   - (Zuzel?) Replace link to lighthouse from footer to point at
   http://help.p2pu.org/discussions/problems#new_topic_form


   - Dirk/Zuzel -> Clean up lighthouse tasks (only 50 open ones, I'll flag
   some) to make sure we don't loose important ones


   - schedule a call for this (i things at EST 10 - 12 thrusday, 10 on
   friday) let me know what time works for you


   - Dirk -> Investigate moving from lighthouse to github issue tracker


   - Are there any features we are losing?


   - We may be losing the ability to "send" tickets from help.p2pu.org to
   the tracker (we can do that for lighthouse). Do we care about this?


   - John -> Organize existing project pipeline into roadmap (discuss next
   week)



   - New badge to be added
   http://help.p2pu.org/discussions/problems/198-re-new-message-from-jonas-backelin-problems


   - done: https://p2pu.org/en/badges/certified-networked-teacher/


   - Check why 'This badge can be earned at all challenges.' is been
   displayed there


   - static bit of the template, we should probably change that


   -
   https://github.com/p2pu/lernanta/blob/master/lernanta/templates/badges/badge.html#L33


   - The badge needs to be associated with
   https://p2pu.org/en/groups/certified-networked-teacher/content/4demonstrating-the-use-of-web-tools-in-a-networked-learning-scenario/


   - I think there were three rubrics on http://pad.p2pu.org/p/CNT


   - django admin interface not working - will fix in shell


   - what error do you get?


   - no error, it doesn't update -- I will check if I can replicate which
   is the rubric missing?


   - and https://p2pu.org/en/badges/p2pu-open-source-developer/


   - and https://p2pu.org/en/badges/p2pu-translator/


   - Next


   - Let Jonas know and close the discussion at help.p2pu.org


   - Dirk/zuzel: fix things that's wrong



   - Release management update


   - Use google doc and/or etherpad?


   - Google doc with technical todo (might contain sensitive info)


   - Update release section on http://pad.p2pu.org/p/tech and include with
   dev notes sent to mailing list


   - Good to have one step-by-step guide with all the notes that remains
   updated


   - Maybe prepare a template and reuse it for each release


   - Take notes *after* the release (don't let this slow down the actual
   release)


   - Doesn't need to be public (main audience is internal)


   - Next step:


   - Dirk -> Create a release checklist (link to or replace existing
   documents)


   - Contains a few standard items (same for each release)


   - And updated with specifics per release



   - Go through list of responsibilities and make sure each has a new owner


   - http://pad.p2pu.org/p/detailed-responsibilities


   - [Dirk] Clarify "ask" for andre truter


   - Next steps;


   - Dirk to review again


   - Speak to Andre Truter about outsourcing as much as possible (maybe to
   andre, maybe to someone else)


   - Review in 1 month



   - Dev priorities/progress reporting in the community call


   - It's a pretty brief update during the community call, try to* keep it
   short*.


   - zuzel will run this week section



   - Demos:


   - multi-task edit/create/order/delete: see edit tasks link at the top
   left of http://alpha.p2pu.org/en/groups/my-challenge/ (login with admini
   strator/password)


   - add/remove organizers
   http://alpha.p2pu.org/en/groups/how-to-ride-a-bike/edit/participants/ (login
   with user10/password)


   - Next step


   - Dirk to look at it
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p2pu.org/pipermail/p2pu-dev/attachments/20120510/140b95a6/attachment-0001.html>