Hans-Joerg Frieden wrote:

Hi!

And the same to you. And everyone else.

For those who need an introduction, I am a Linux-user, sysadmin, programmer, civil engineer (degree in Medical Cybernetics, very useful. NOT! :-) ) who do programming (C for Atmel, PIC16 and Linux), HTML (typically with CGI scripts written in C) and electronics for money, and HTML/PHP/postgreSQL, electronics, bicycle trips and play three or four wind instruments on my "spare" time.

I actually work with what used to be my hobby, so now I've started planning a small and portable ultrasound device (could be used to measure distances, movement etc. The ultimate geek gadget!) as a hobby. Ultrasound is what civil engineering in medical cybernetics is ALL about, btw :-)

I've seen the discussion raging on on aw.net, amigadev and elsewhere. Can we concentrate it on one point please (preferrably this mailing list) so that we don't need to monitor too many web fora? I definitely lack the time for that.

Agreed. I just couldn't there for a while, cause mozilla had eaten all my emails and I was sitting outside the firewall :-)

My main points from the forum discussions are:

1: Decide on a manager. 2: Manager goes on to discuss porting with sander.vesik@ireland.sun.com (correct way to start, according to porting.openoffice.org) 3: We decide how to host various things like mail, http, versioning control system, and who is responsible for what. 4: Those of us responsible for something (from step 3) starts putting together the resources needed. 5: The rest of us start looking at what needs to be done to the codebase.

Starting off in any other direction just doesn't work for me.

PS: I've cheated on step three to five, since I'm already hosting a mailing list and am busy putting everything into my SVN repository (but if the project team wants to use CVS instead, go ahead. I sure ain't stopping you. You can even copy MINE once it's a bit more finished :-) ). While doing this I'm identifying which directories belong to OO.org and which are just full of download/somelibrary.tar.gz's. These obviously needs to go in their respective libs/ or helpers/ subdirs in the repository.

PPS: If the team decides to not use my servers for this, that is just fine with me, but except for the fact that the mailing list has @samfundet.no I don't think you'll find many servers with better uptime/cpu-speed/network connection for free. It's a 24/7 Linux server on a dual 1.6GHz AMD MP with a direct 100Mbit up it's arse :-P

PPPS: The libraries are things like neon, libxml2 (together this forms most of what we needed to port SVN anyway :-P ), libz, libexpat, flatxmlbinaries (I presume only ONE xml toolkit is necessary :-P) etc etc.

P4S: Now I REALLY need to eat something, so will take a long break from this discussion while I fetch some blood sugar and other things (need new engine for my Mini-Z as well ;-) ). There's no end to the foolishness one does at 9 am after having been up since 2... (WAY out of sync with the rest of the time zone here...)