HTTPS clone URL
Subversion checkout URL
- API development process
- Board Updates
- Configuring lernanta on hudson
- Course Metrics Roadmap
- css framework
- Deployment on dev.p2pu.org (outdated)
- Dev Meetings 2011
- Development documentation
- Development Notes
- Fossacademy code overview
- Github Cheat Sheet
- Known issues
- Lernanta code overview
- Lernanta Roadmap 2011
- Lernanta Workflow (outdated)
- Lernanta's Setup Install
- MySQL & Lernanta
- Release 0.2 Change List
- Release 0.3 change list
- Release 0.4 Change List
- Release 0.5 change list
- Release 0.6 change list
- Release 0.7 change list
- Release 0.8 change list
- Release 0.9 change list
- Release 1.0 change list
- Release 1.1 change list
- Release 1.2 change list
- Release 1.3 change list
- Release 1.4 change list
- Release 1.5 change list
- Release 1.6 change list
- Release 1.7 change list
- Release 1.9 change list
- Release and testing process
- Release Reviews (outdated)
- Roadmap 2012 January to June
- SauceLabs Tests
- Setting up the development environment on Mac
- Setting up the development environment on Ubuntu
- Setup in Production
- Setup Lernanta
- Setup Lernanta Automated
- Setup Lernanta Manually
- Stian's ideas about lernanta functionality (outdated)
- Translating Lernanta
Clone this wiki locally
Lernanta is the software that supports P2PU's site, which started as a fork of Mozilla drumbeat's Batucada project. It is based on Django, and licensed under MPL 1.1/GPL 2.0/LGPL 2.1. Thanks to all the people who have/are/will contribute code into Lernanta.
- Use our automated script for an assisted setup of the development environment. (Highly recommended)
- Or follow the hard and rocky step-by-step instructions
We have several resources for those of you that want to dive into the code as soon as possible!
- Then we have a quick overview of what's going on inside the code and how that relates to a running instance of Lernanta.
- We also have some pointers on how to get your contributions merged back into Lernanta
- Last but not least, we have a challenge on the P2PU site to help you get started!
- Main communications are on the p2pu-dev mailing list
- We can also arrange hangouts at the Internet Relay Chat (IRC) channel #p2pu-dev in irc.freenode.net (How to use IRC). Please join us!
- A development roadmap shows major milestones and an overview of planned features for each bi-weekly release.
- If you want to submit a bug you can create an issue right here on github. Please ensure that the bug is valid or that a feature is implementation ready.
- We also have a less tech place for users to ask us questions and report problems at help.p2pu.org.
- We try to keep a shorter list of issues marked as 'easy-contribution' so new contributors have a good place to get their feet wet with our code base! If you don't find a task just for you, let us know at the mailing list and we will prepare one.
- We have a page for people interested in translating Lernanta into other languages.
- You can find other development documentation on this github wiki.
- Receive daily summary of commit notifications to lernanta:master by email, twitter, or RSS.
- See dev stats at http://www.ohloh.net/p/lernanta
If you want to adopt a task, that's great! Even if you're relatively new to programming, this is a friendly community and we encourage you to dive in! (DON'T FORGET TO TAKE A LOOK AT THE CHEAT SHEET) The general process we're following is:
- Find an issue on github that you're interested in, maybe one labeled as 'easy contribution'.
- Let us know with a comment on the task that you can help with it, so we don't duplicate efforts and help you get up to speed.
- Fork the code on github.
- Set up your development environment
- Make your changes. Commit. Update your fork on github.
- Send us a pull request. Note that all the code contributed/committed into our repository is licensed under the terms expressed in LICENSE.txt
If you're not familiar with that process we're happy to explain it more (and will try to do so in our cheat sheet as well). To do all this, you need to have a github account. If you really don't want to use github, please feel free to send a manual pull request of submit a patch.