KnowledgeBase
2265
Comment: add http browsable link to material
|
2379
|
Deletions are marked like this. | Additions are marked like this. |
Line 4: | Line 4: |
* Meeting log from BOF session at UDS [attachment: 2007-11-1-https://wiki.ubuntu.com/Training/2007-11-01BofLog] |
Meeting Logs
Meeting log from BOF session at UDS [attachment: 2007-11-1-https://wiki.ubuntu.com/Training/2007-11-01BofLog]
- Meeting log from [attachment:2007-10-18-ubuntu-training.log 18th October]
- Meeting log from [attachment:2007-09-20-ubuntu-training.log 20th September]
- Meeting log from [attachment:2007-09-06-ubuntu-training.log 06th September]
- Meeting log from [attachment:2007-08-23-ubuntu-training.log 23rd August]
- Meeting log from [attachment:2007-08-09-ubuntu-training.log 9th August]
Launchpad and Bazaar
This is a step-by-step guide for creating a branch of the Ubuntu Desktop Course and working on it. The Ubuntu Desktop course is hosted on Launchpad in a bazaar repository (https://launchpad.net/ubuntu-desktop-course)
- Create a directory on your system, we use ubuntu-desktop-course here
- $ mkdir ubuntu-desktop-course; cd ubuntu-desktop-course
- Create a repository to hold branches
- $ bzr init-repo .
- This step is not absolutely necessary, but of advantage if you want to have several branches
- $ bzr init-repo .
- Branch from the desktop course beta
$ bzr branch http://bazaar.launchpad.net/~canonical-training/ubuntu-desktop-course/ubuntu-desktop-course-beta ([https://code.launchpad.net/~canonical-training/ubuntu-desktop-course/ubuntu-desktop-course-beta browse])
- A new directory named ubuntu-desktop-course-beta is created and populated
- The local branch of the desktop course makes it possible to see the changes you made more easily when offline
- Create your own branch
$ bzr branch ubuntu-desktop-course-beta ubuntu-desktop-course-beta-<NAME OR NICK>
- This is your working copy
- Edit and change the XML files
- Use any editor you like
- gnome-edit offers syntax highlighting
- bluefish offers easy use of xmllint to check the XML validity
For more options see http://wiki.docbook.org/topic/DocBookAuthoringTools
- Use any editor you like
- Commit your changes
- $ bzr commit -m "Example commit, corrected error on bzr usage"
- Commit after every logical change, e.g. update of a paragraph or list
- Use sensible commit messages
- $ bzr commit -m "Example commit, corrected error on bzr usage"
- Publish your branch
- From your branch directory call
bzr push bzr+ssh://<LAUNCHPAD USERNAME>@bazaar.launchpad.net/~<LAUNCHPAD USERNAME>/ubuntu-desktop-course/<YOUR BRANCH NAME>
- From your branch directory call
Training/KnowledgeBase (last edited 2009-08-31 10:21:51 by 88-134-43-96-dynip)