[Parsix-Users] Parsix Random News #1 - October 24, 2007

[Alan Baghumian]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

Recently, I have sent several emails each one related to a few  
differentsubjects, so I decided to call such emails as "Parsix Random  
News" orPRN in brief. You are reading the first official PRN (#1) :-)  
Currently I have noidea to publish the PRN in a regular timed fashion.

[ Parsix Build Server is up an running ]
  Finally I got some spare time to write an automated build server  
forthe project. The build server reads a queue table, updates local  
SVNworking copy, fetches related source code from the upstream (in case  
ofnon native packages), builds packages for i386 and amd64  
architecturesin a fresh pbuilder [1] chroot and then uploads produced  
packages tothe local APT repository. Beside of accurate machine built  
packages, itis a very time saving tool. It's fairly stable now, but I  
have a bunchof ideas to improve it. It also logs [2] build process and  
the packagewatch system [3] is also updated to represent build status.  
Massivedevelopments should go over the queue system: an authenticated  
webbased system to add packages to the queue and to confirm them to  
bebuilt by build server.

[ Parsix Calls For Volunteer Co-Developers ]
Our tool-chain is finally in a good level and I'm satisfied that we  
cancall for some co-developers. First let me summarize what we have as  
a brief introduction:

a) SVN Repository: After this, all packages *must* go through the  
svnrepository. No manual packages [4]. Developers will have access to  
theSVN repository to do their works (docs, artwork, packages, patches  
etc)

b) Build Server and APT repository [2], [5].

c) Bug tracker: It has been up and running for a while. It's open to  
allto submit bugs and problems and developers can handlereported bugs  
[6].

d) Wiki: I don't describe more about the wiki. All small documentsand  
howtos should go through wiki [7].
e) Forums and user mailing list: To handle support activities and  
userdiscussions [8], [9].

f) Development mailing list: To handle development activities  
anddiscussions [10].

g) Watch system: Reports the latest status for Parsix packages. 
* Required skills categories:
- ----------------------------------------------------------------------------------a)  
A reasonable level of English language.

b) To be familiar with Debian/Ubuntu/Parsix systems,different software  
packages and their functions and tasks.

c) Basic SVN and version control knowledge [11].

d) Debian packaging, Read [12], [13].
* Needed activities and required  
skills:----------------------------------------------------------------------------------
a) Bug tracking: Be able to reproduce reported bugs and find source  
ofproblems and suggest solution. Skills (a,b).

b) Documentation: To write needed howtos, guides etc. Skills (a,b).

c) Maintainer: To package new software and update existing packages for  
Parsix. Skills (a,b,c,d).

If you are interested to be a Parsix Co-Developer, email me.

Cheers,
Alan

[1] http://netfort.gr.jp/~dancer/software/pbuilder-doc/pbuilder-doc.html
[2] http://buildd.parsix.org
[3] http://watch.parsix.org
[4] http://svn.debian.org/wsvn/pkg-parsix
[5] http://parsix.org/packages/
[6] http://bugs.parsix.org
[7] http://wiki.parsix.org
[8] http://parsix.org/html/PNphpBB2-viewforum-f-1.html
[9] http://parsix.org/cgi-bin/mailman/listinfo/parsix-users
[10] http://parsix.org/cgi-bin/mailman/listinfo/parsix-devel
[11] http://svnbook.red-bean.com/
[12] http://www.debian.org/doc/maint-guide/
[13] http://debianpaket.de/svn-buildpackage/index.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD4DBQFHHwl3seAo3XkuIc0RAsAeAKCpi07sH58D1EWGx8VMtol3A++OjQCY3+eB
qv1jyyND35JFbo/BQJo+mw==
=Kc9H
-----END PGP SIGNATURE-----