As mentioned in a previous discussion, I'm currently recruiting folks who'd 
be willing to take on specific roles in the AbiWord release process.  

One of the biggest complexities during the process of making AbiWord 
binaries is creating packages for all of the various platforms that we 
support.  Once we've frozen the sources for a specific release, those need 
to get built into an ever-growing number of package formats.  Ideally, *all* 
binaries for a given release would be built cleanly from the same sources, 
but that's a lot of simultaneous compilation to be doing.  

Thus, for each release we need to have a set of known people with fast net 
connections who'd be willing to create specific packages.  For an overview 
of the requirements, see:

  http://www.abisource.com/mailinglists/abiword-dev/01/August/0401.html

For a current set of "must have" packages, see:

  http://www.abisource.com/mailinglists/abiword-dev/01/August/0687.html
  http://www.abisource.com/mailinglists/abiword-dev/01/August/0726.html

However, we'd love to have a much broader range of packages, so we're 
looking for volunteers who'd be willing to regularly and reliably produce a 
specific package or set of packages.  

job description
---------------
As we get close to each release, this could involve a series of near-daily 
candidate builds.  Then, once we hit the final release, you may be asked to 
rebuild packages repeatedly to resolve any problems which arise that are 
serious enough to break the freeze.  

You'll be working closely with one or more testers who'll be verifying that 
you've created clean packages (the MD5s match, the product launches and 
runs), and that the release works as advertised.  

Note that you're not necessarily expected to do the coding work to *fix* 
bugs (that's what the maintainers are for), but feel free to help out there 
as well.

status
------
So far, the following people have volunteered to be packagers:

  Linux/i386   Tim LaDuca
  Win32        Nikolaj Brandt Jensen, Tim LaDuca
  Slackware 8  JAL

For details, see:

  http://www.abisource.com/mailinglists/abiword-dev/01/August/0406.html
  http://www.abisource.com/mailinglists/abiword-dev/01/August/0410.html
  http://www.abisource.com/mailinglists/abiword-dev/01/August/0707.html

If I've missed anyone, please let me know. 

bottom line
-----------
If you're willing to be an AbiWord packager, please send us a message at 
[EMAIL PROTECTED] (you'll need to subscribe first), introducing 
yourself, and describing the packages you'd like to be responsible for. 

Thanks!

Paul
motto -- many hands make light work

Reply via email to