Re: [IAEP] [ANNOUNCE] Sucrose 0.83.4 Development Release
Bernie Innocenti wrote: Walter Bender wrote: Wow!! We have great release notes lately. To credit authors, I'd also append the patch summary by author, Linus-style. It can quickly be obtained this way: git log v0.83.3..HEAD | git-shortlog Excellent, will do that for the next release. So the command for sugar for this release would be (no-merges to get rid of the messages when you merge the master tree Merge branch 'master' of gitori...@git.sugarlabs.org:sugar/mainline): git log v0.83.4..v0.83.5 --no-merges | git-shortlog That will encourage people to write nice commit messages :) I would suggest to put up some guidelines (no rules), so a reader can more easily parse them. For example: - ticket number always at the beginning of the commit message - Start message with a capital letter - For typo fixes use: _Typo - For pylint fixes use: _Pylint More thoughts? Simon ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
Re: [IAEP] [Sugar-devel] [ANNOUNCE] Sucrose 0.83.4 Development Release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Jan 22, 2009 at 09:54:36AM +0100, Simon Schampijer wrote: So the command for sugar for this release would be [...]: git log v0.83.4..v0.83.5 --no-merges | git-shortlog That will encourage people to write nice commit messages :) I would suggest to put up some guidelines (no rules), so a reader can more easily parse them. For example: - ticket number always at the beginning of the commit message - Start message with a capital letter - For typo fixes use: _Typo - For pylint fixes use: _Pylint Use the recommended style as mentioned in Git documentation somewhere: First line a summary of at most 40 chars, then empty line, then optional detailed commit message (which is stripped by git-shortlog). Also, I'd suggest mentioning ticket numbers at end instead, in the style used by Debian. Example: Fix foobar - barbaz. Closes: SL#1234, OLPC#1235. The logic is to always prepend Closes: and then either SL# or # for each comma-separated ticket closed, or prepend OLPC# for tickets closed at the laptop.org bugtracker. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkl4irQACgkQn7DbMsAkQLgCDQCbBObD5vCNDLrGX3HNLNK1RvFg vokAniZd0hz/KXxZ2JhUf1Fr8s6me++e =4VCG -END PGP SIGNATURE- ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
[IAEP] bookrea...@lists.laptop.org , collaborations with the gnubook project
Dear all, We are working with the gnubook developers to help optimize it for reading books on the XO. Those of you who have tested it out already know what it looks like; for the rest of you, you can still see it in action at the open library. Help and suggestions are much appreciated. If your own projects use less hackable book readers, please consider migrating to gnubook -- every Internet Archive book will be available in that format. http://openlibrary.org/olpc/bookreader https://bugs.launchpad.net/gnubook We are also working with CK12 to start wikifying some useful public domain texts, so that teachers can start making localized versions of them. This is another step towards the goal of useful wikibooks for every student -- and tools to let every student create their own books. Their flexr toolchain is undergoing rapid development, and it makes me grin every time I use it. Poke user:jgay if you want more access to it than you get by default (say, to create your own book from scratch)... have faith that underneath the sexy exterior is the heart of a mediawiki instance, ready to synch with your favorite wiki anywhere else in the world. http://flexbooks.ck12.org/flexr/ For discussions about every part of this toolchain, from annotation and uploading to reading to bookshelf collection creation, we are setting up a new list : bookrea...@lists.laptop.org Some of the initial discussion will be carried out here, to solicit input from everyone; you are encouraged to join that list for more detailed discussion. Regards, SJ ps - At some point in the platonic future these topics may merge with those on wikirea...@lists, but for now the former is primarily about finding, organizing, and sharing mostly-static booklists or syllabi, and the latter is focused on compiling, copyediting, and sharing collections of thousands of wiki articles, with dense internal links and regular revisions and updates. ___ IAEP -- It's An Education Project (not a laptop project!) IAEP@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep
