Next one
- More good things to include in list of responsibilities and documentation:
- The ins and outs of managing help desk requests (i think john manages help desk)
- Note that the help desk is not a task that should be own by the tech lead, so I will recommend we do not include it in full in the tech lead responsabilities (only tasks that do require site admin access or tech knowledge should be added to the tech lead queue)
- Creating lighthouse tickets from helpdesk
- There is an 'Attach a Lighthouse Ticket' action on the right sidebar when support staff is looking at a discussions, tickets with bug/feature requests that can't be solved inmediatedly should be assigned a lighthouse ticket and they can be reopened on help.p2pu.org later when a fix is done and we want to let the user know.
- Forwarding to private discussion
- etc ...
- The release went well, shared notes on a google doc with you (also moved some important details to a http://pad.p2pu.org/releases
- I have been doing some cleanup on the github wiki (noticed there was at least one spam link this time)
- Next:
- Keep working on documentation
- Prepare list of people who has contributed translating lernanta in the last months for Dirk (store where? on the wiki?) google doc maybe (it contains email addresses)
- More cleaning of the github wiki (read all the pages there and make fixes where neccesary) - thanks, i know it's not fun ;-)
- Let specific partners know Dirk will be taking over?
- Openbadges / (Brian, Sunny)
- "Just wanted to let you know that Dirk Uys is taking over many of my responsibilities going forward. We have been working together for the past few weeks making sure that the transition will be smooth. I'll also still be around to help with any questions."
- Demo what is done on multi-task edit/create/delet/order on the tech call tomorrow and let dirk do the next step which is to integrate this functionality on the new challenge creation form.
- Call about badges project on Thursday
- Let Dirk manage this week's dev priorities section on the community call
- On Friday, check with Bekka the status of the previous invoice and send the last one (probably best to convine them if the transaction needs to be redone).
- Zuzel to let us know if it hasn't arrived by Friday
- Exit interview
May 2
- Release planning with Dirk
Apr 23
- https://trello.com/board/documentation/4f91ccb50677637b271aff62
- The future of P2PU development processes
- Consider relaxing release schedule
- TODO: Zuzel to design a sysadmin role (pick responsibilities from the detailed-responsibilities etherpad) that we could break out separately
- Offer as contract on retainer / question -> how many hours per week is reasonable?
- Email to team
- Discuss hand-over with Dirk
Apr 17
- Setting priorities for Dirk
- Fixing most obvious UX issues
- Do you have something specific in mind? Are there some existing cards/tickets with UI issues you will like to assign to him?
- John suggested some cards in a past tech call (I added the cards with only the titles) but they are pending details from him
- I am adding tasks to https://trello.com/board/dirk-s-todo/4f7aa81b6f0fc2d24d99dd47 in the mean time
- This past week he has work on:
- The introduction to contributing to lernanta course -> challenge transformation
- deferred ajax loading of the data in courses' metrics dashboard page
- fixing a bug with titles for which the slug was empty
- updating notification sent to user when (s)he creates a course with new text provided by alison/bekka
- adding a more_details field to schools to support customizations requested by Karen (+ one unittest): http://help.p2pu.org/discussions/questions/63-school-page-layout
- I have been trying to pick tasks that allow him to touch different parts of the lernanta source code so he gets familiar with them
- Added "Process for manual adition of badges until there is a new learning person" to tech pad but we could start talking about it today
- http://lists.p2pu.org/pipermail/p2pu-dev/2012-April/002624.html
- In the future, learning lead will take over. Right now we are in process of hiring a new learning lead.
- For now:
- Zuzel will create a template form (etherpad) with the information we need to create new badges
- Send the community list the new badges before creating them to get feedback
- P2PU Lab implications for platform
- Different options to support experimentation (experimentation of "learning" practices):
- For each: what possibilities does this create for P2PU (what risks / challenges)
- API
- Allows development of separate front-end
- e.g. lighthouse api
- Embed
- Embed can work both ways (we embed other peoples features, or others embed ours)
- Code runs on central server
- Allows us to display parts of our site inside other websites (distribute features to other sites), e.g. a P2PU hosted course could be embedded on the wiki for school of maths
- Or display parts of other sites inside p2pu.org pages (add functionality we don't have)
- Integration is superficial - limitations to what the embedded code can change on the host site / the embedded features can't talk to the server / cannot change CSS ...
- Easier to embed p2pu through using Oembed (user only needs to know the URL from p2pu.org to automatically get the code they need to put on their site / not required to copy the embed code)
- want to try out a different forum style e.g. embed http://disqus.com/
- Plug-in architecture (like wordpress) + software than can be installed in other servers
- People are able to install different instances of lernanta and enable dissable plugins that offer new functionality or modify the core functionality (depending on what the plugin infraestructure allows them to do)
- Allows extension of core functionality
- Plug-in runs on the server where the instance runs
- Security issues, plug-ins may have access to data
- Reliability questions, what if something breaks? how do we recove?
- terms of service
- control who can install plug-ins on our server
- Modular architecture / Reusable Django apps
- Build features as semi-independent apps
- Makes it easier for others to re-use our code and include in their projects
- Prototypes
- Separate instance of lernanta
- Allows high level of customization
- Scenario
- Each school gets more independent identity / feel / community
- P2PU is the "liberal arts" school for all non-school courses
- User accounts across all sites
- labs.p2pu.org is a separate instance for more radical experimentation
- allows any kind of embedding
Apr 3
- Dirk enjoys the onboarding process (well done!)
- Need to collect feedack when he is done
Mar 27
Mar 20th:
Mar 6th:
- DML
- Learn page demo tomorrow
- School of Games
Feb 28: did not see you online -- nothing on the agenda either
Feb 21: ping me if there is a call today. thx.
Feb 14
Berlin update
- Zuzel planning to be in Berlin for all of July
- Luis may come, but not work on P2PU
- P2PU would try to find accomodation that works comfortably for 2 people
Contract in the works. Will be complete for next payment round.
- Make sure health insurance is ok
Monthly Call -- Last Updated -> 26 September 2011
1 - How are things going overall? How were the last 4 weeks?
- We are getting used to work with a bigger set of people
- Important to get communication right
2 - Priorities for next month
- Webmaking 101
- Metrics again (more people)
- School of Ed (UCI)
- General UX enhancements (<- from Arlton)
- Improve communication / development processes?
After next month:
- Not exactly next month: defining p2pu experience (courses, study groups, challenges, personal learning plans, portfolios,...)
3 - Questions / issues / discussion
- Role of Product Manager in development process
- Bring the user-perspective into the conversation?
- Listen to users? Or suggest new features from scratch?
- Clarify the "learning product" for P2PU
- Need a blueprint for development processes (lightweight)
- Avoid design by committee - but make sure community input is taken seriously and the use cases are clear
- How to coordinate between all key stakeholders?
- Who makes the ultimate decisions?
- Module ownership approach useful, but coordination between modules important
- Lack dev resources to accomplish everything, e.g. old feature requests (e.g. discussion by email) still on hold
4 - Long-term success metrics for Zuzel
- # Commits (we work), # Issues (big tickets in september will make hard to count this) - only useful as base metric, but sometimes other metrics are more important
- Healthy and active volunteer developer community
- # Volunteer developers (new members over time)
- Activity level
- Number, importance and quality of new features (list)
- Site is stable, performant, secure, and reliable
- No downtime except for release related restart of webserver
- Regular releases with new features (and few bugs, which are fixed quickly)
- Bugs are fixed quickly
- Dan's security alert - fixed immediately
- Other small bugs - fixed immediately
- Interactions with other projects (open badges)
5 - Feedback to Philipp
- Don't overcommit give that we have limited resources (already getting better)! - Stackeholder (datelines)
- Good job finding new interesting projects (School of Ed, others)
- Communication getting better, but still room for improvement