The last couple of weeks in MOTU

[Jamie Jones]

On Thu, 2006-01-19 at 14:55 +0100, Raphaël Pinson wrote:
> On 1/19/06, Jamie Jones <hentai_yagi at yahoo.com.au> wrote:
> > Yes, which brings me to the point of my mail, now that the flaming is
> > over - and we are carrying on our way, Masters would you mind picking
> > apart those packages on REVU, and helping us apprentices achieve MOTU
> > enlightenment.
> 
> Do you mean a reviewing course on #motu-school for example? Or at
> least a conference on important points we mind about?
> 
> Raphaël

G'day Raphaël, MOTU's, and fellow MOTU apprentices,

Some of the things I had in mind (other then getting more feedback on
all packages in revu), in no particular order are:

*) Introduction the various helpers used to build .debs, eg, dpatch and
friends, so we can become familiar with them, both to create new .debs,
and to patch existing ones. IIRC Debian has been complaining their build
systems have been changed unnecessarily, I suspect they may be because
some of us don't know how to use these other build systems.

*) Introduction to packaging 1 source that produces 1 binary, 1 source
that produces multiple different binaries, 1 source that produces
multiple binaries by rebuilding the source with eg different configure
flags, 1 source that produces a binary and libs, and 1 source that
produces libs only.

*) Guide on common packaging mistakes, and how to avoid them.

*) Figure some sort of way for us to be able to get builds and reports
of our packages on the different arches available ie amd64, i386 and
powerpc, without begging on IRC.

*) Perhaps an experimental repo for us to upload proposed changes or new
ideas to, eg I've been trying to get some i386 only packages running on
amd64, but have had a lack of feedback (none actually) from any testers,
presumably because it is to hard to test.

*) Clarification on what is and is not acceptable for
universe/multiverse and how to judge which we should submit packages to.
Do we follow the DFSG strictly ? Can we include what they consider
non-free but are useful to us (often eg game data that can't be
modified, but could mean non-commercial use licensed software) ?

*) Guides to effective bug triage, and how to do it right.

*) Beginners guide to malone.

*) How to be an effective reviewer.

*) Guides to the common revision control system being used.

That's about all I can think of right now, but those are some of the
areas I see that could help us apprentices achieve MOTU enlightenment.

Regards
Yagisan
-- 
Jamie Jones
Proprietor
E-Yagi Consulting
ABN: 32 138 593 410
Mob: +61 4 16 025 081
Email: eyagi.consulting at gmail.com
Web: http://www.eyagiconsulting.com

GPG/PGP signed mail preferred. No HTML mail. No MS Word attachments
PGP Key ID 0x4B6E7209
Fingerprint E1FD 9D7E 6BB4 1BD4 AEB9 3091 0027 CEFA 4B6E 7209
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/ubuntu-motu/attachments/20060120/b69e5dcc/attachment.pgp