Skip to content
zuzelvp edited this page Jul 11, 2011 · 6 revisions

July 2011

How are things going overall?

Any big wins / achievements / opportunities?

Major challenges / doubts / questions?

Metrics: How are you tracking progress / How do you know things are working?

April 2011

Overview

  • Launched http://new.p2pu.org: Original idea was to use for beta testing, and plan for migration in July. Response has been overwhelmingly positive, and already more study groups and courses on the new site than the old one. Currently investigating earlier migration date.
  • Every two weeks, we release a new version of the site that has lots of improvements and bug fixes. A detailed list of changes can always be found here: https://github.com/p2pu/lernanta/wiki/Lernanta's-Roadmap

High level roadmap (major focus areas):

  • Schools: Provide richer and better integrated set of features for schools. Wireframes and functional design completed. See description here: https://cacoo.com/diagrams/Ly2n5wiuzwpU2uMq
  • Study Groups/ Courses: Improve features within study groups. Allow more rich content to be added, and add facilitation features.
  • Email Integration: Facilitate the email-based use of the site, comment by email.
  • Learning Recognition: Badges and peer-assessment associated with study groups tasks to recognize learning occurring inside the study groups.
  • Front-end: Overall look of the site looks nice and clean in major browsers, but needs more testing and adjustment before public launch.
  • Migration: Facilitate the migration into the new site.
  • Integration with External tools: Support better integration with external tools (more than RSS and embedding).
  • Internationalization: Translate the interface into other languages (starting with Spanish)

Process of involving the community via feedback, and volunteer developers

  • Marked increase in volunteer contributions.
    • Have given commit access to one other developer
    • Other contributors are sending us “patches/pull requests” (improvements they have made, that we add to the application)
  • Source code is hosted on a public repository that allows contributors to help us improve the site.
  • Use of a public task tracker (http://p2pu.lighthouseapp.com) to store and handle feedback/tasks (organized by areas/tags and time/release milestones).
  • Use of the mailing lists and the new site to interact with the community and the beta-test users.
  • Created a study group in the new site that helps potential contributors join the development process (using P2PU to hack P2PU).
  • Community calls for real-time discussions.

Areas that need help / Challenges

  • Design / Front-end
Clone this wiki locally