Johannes Winkelmann wrote:
Hi there,
[ this is rather long. my apologies ]
Hi Johannes. I think your length is quite fine. Ew..
Also, I'd like to propose having weekly or bi-weekly IRC meetings on a defined weekday (i.e. wednesday), to allow slightly more focused discussion and allowing those with less interest to constantly idle on IRC to take part in IRC discussions. Simone suggested to list the dates on a wiki pages, which whould also allow to attach notes like agenda or results; However those meetings are supposed to me non-formal, and attendance is purely optional.
This all sounds good. Perhaps weekends are best? Jaeger and I are often available on IRC during the workdays; but I won't always be able to ditch my responsibilities there to take part. I know the timezone difference is significant, and I don't think you guys should have to wait until midnight for us. Thus, maybe weekends are the answer?
We'll also need to update the handbook, and find out where to host the releases (the main file server up to now was fukt, to which no one besides Per has access).
I guess berlios is the most logical solution for this?
- write a port validator to detect potentially malicious or dangerous commands in Pkgfiles; run on contrib nightly or so; suggest its use on the relevant wiki pages
Wouldn't a fakeroot/pretendroot version of pkgmk be a simple and effective solution to this problem? I fear that a validator would be difficult to write [cleanly], and not all that hard to break.
- find a maintainer for prtsync (Jay originally wrote it but lacked time/interest, I added a number of quick fixes to address problems appearing during the test runs); there are a number of annoyances, missing features, and things to clean up; nothing too urgent though
Heh, yea..
- define contact persons for certain subsystems; examples for this are: server maintenance, subversion, bug tracking, website accounts, prtsync, mailing list admin, release engineering, user account management and access control. A lot of this stuff currently ends up in my (and probably others') private inbox, which is slightly tiresome.
Let's list these subsystems on the Wiki, and let people sign themselves up for things that interest them.
- define a more democratic way do take decisions. Things like the core/opt separation or WiFi kernel module inclusion are typical examples for this, both were basically decided ad hoc on IRC by those online at that point in time.
Perhaps email threads containing "PROPOSAL" or some other tag in the subject would allow further participation, and provide more accessible documentation for our decisions. -- Jay Dolan jdolan.dyndns.org A: Top posting. Q: What's the most annoying thing about usenet? A: Because it's annoying to read. Q: Why is top-posting bad?