NEXO: Difference between revisions
No edit summary |
(simplified, merged.) |
||
| Line 16: | Line 16: | ||
After a new NEXS release has been deemed deployment-ready, update the [[NEXO]] page to state that this is the most recent stable release. |
After a new NEXS release has been deemed deployment-ready, update the [[NEXO]] page to state that this is the most recent stable release. |
||
=== Development process === |
|||
... |
|||
=== Build system === |
=== Build system === |
||
| Line 33: | Line 30: | ||
If this is a new activity: |
If this is a new activity: |
||
# Follow the [[#Development process |
# Follow the [[#Development|development process]] to add the new activity to the OLPC_CORE_ACTIVITIES variable in /home/pilgrim/pilgrim/streams.d/olpc-development.stream (see the [[#Build system|]] for details) -- remember to commit and push your changes. |
||
#* Ask the NEXO build master to do this step for you, if you prefer |
#* Ask the NEXO build master to do this step for you, if you prefer |
||
| Line 40: | Line 37: | ||
=== Release notes === |
=== Release notes === |
||
... |
... |
||
== Notes for developers and testers == |
== Notes for developers and testers == |
||
Revision as of 08:44, 19 December 2009
NEXO is a collection of activities and other material designed for use on XOs in Nepal. (is it an entire XO image, from Fedora and Sugar to the full activity suite? If so, designed to boot from NAND, from an SD card, both?)
Background & how to use NEXO
...
Development
Most NEXO development tasks can be grouped under 2 categories:
- Activity updates (or addition of new activities): this process is documented below in the updating activities section.
- Tweaks on top of underlying OLPC OS through pilgrim at /home/pilgrim: the internals are documented below on the build system section.
Before making any change, you should have fully tested it on an individual XO. At this point, you can make the change on the pilgrim box (192.168.5.233) as the pilgrim user. If your change involved changing anything under the pilgrim repository, please make sure to commit and push your changes.
Your change is now ready for inclusion in the next NEXO build, but there is one last step: Update [[#Release notes|]] with your change. If you need to, create a new entry at the top of the page labelled simply "Unreleased development version" or similar (otherwise, append to the development entry that already exists). When released, the build master will assign an appropriate version number and release date and send the list of changes to the team.
After a new NEXS release has been deemed deployment-ready, update the NEXO page to state that this is the most recent stable release.
Build system
...
Updating activities
To add a new version of an activity (or a brand new activity) for inclusion in a future NEXO build:
- On your own computer, access the Deployment share of the fileserver.
- Put the new or updated activity in the NEXO/activities directory
- Clean up the activities directory: remove old versions
- This is important because this directory (in entirity) is synchronized to the school servers, sometimes over slow network links
If this is a new activity:
- Follow the development process to add the new activity to the OLPC_CORE_ACTIVITIES variable in /home/pilgrim/pilgrim/streams.d/olpc-development.stream (see the [[#Build system|]] for details) -- remember to commit and push your changes.
- Ask the NEXO build master to do this step for you, if you prefer
Your activity is now ready for inclusion in the next NEXO build.
Release notes
...
Notes for developers and testers
- See also the [[#Development process|]] above.
Related projects
There are also NEXS and NEXC projects, related to the server and the C?...
NEXS and NEXC development
...