Slashdot Log In
Third NetBSD Hackathon Summary
Posted by
kdawson
on Thu Nov 30, 2006 12:58 PM
from the fun-in-the-channel dept.
from the fun-in-the-channel dept.
jschauma writes, "The third NetBSD Hackathon was
held on Saturday and Sunday, November 25th and 26th, 2006. NetBSD users
and developers met on IRC to prepare NetBSD for the upcoming re-branching
of NetBSD 4.0. Approximately thirty NetBSD developers and more than 140
NetBSD users joined in on the two days, paying particular attention to
improving install documentation and ensuring build stability. A Wiki page as a TODO list
was used for the first time, an approach that is likely to be used in future
hackathons. All in all, over 200 bugs have been worked on in those two days
and while not all of the critical showstoppers could be fixed, valuable
progress was made in identifying root causes."
Related Stories
[+]
First NetBSD Bugathon a Success 32 comments
Daniel de Kok writes "Last weekend the first NetBSD Bugathon weekend was organized by Elad Efrat to handle as many open PRs (problem reports) as possible in a weekend, checking and fixing the bugs that were reported. Although the first Bugathon was not announced widely, it was a success: about 30 developers and 20 users closed around 270 PRs, bringing the number of open PRs down from 4200 to less than 4000.
The next Bugathon will take place on 7-8 October, and NetBSD users and developers are invited to help fixing bugs and handling PRs."
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
Nice to see Wiki software used (Score:5, Interesting)
Re: (Score:1, Troll)
Mini-rant mode --
Open Source pet-peeve: using a wiki for documentation. Expecting the users (the oh-so-often-spoken-of "community") to write your documentation for you is lazy. I know developers usually prefer not to deal with documentation. I understand the appeal of throwing something out there and having the users document it so you don't have to. But please, PLEASE, let the wiki-as-documentation phenomeno
Re: (Score:3, Informative)
I'm with you. There's nothing worse than projects who seem to have no design plan and just code ahead. Documentation is lacking and you have users guessing about the features. Most prominent example in my eyes is Asterisk.
Fortunately, wikis were used for this event only. I can understand that they wanted to have a process that allows for fast changes
Re: (Score:2)
Re: (Score:2)
It has its place. But it makes a piss-poor substitution for real documentation.
Re: (Score:2)
Laugh at me if you must... (Score:1)
i wish i had the time (Score:3, Interesting)