Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Programming Operating Systems BSD IT Technology

Third NetBSD Hackathon Summary 15

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."
This discussion has been archived. No new comments can be posted.

Third NetBSD Hackathon Summary

Comments Filter:
  • by Alkivar ( 25833 ) * on Thursday November 30, 2006 @02:00PM (#17051970) Homepage
    It's really nice to see Wiki software used for it's original purpose, and used properly. Hopefully the NetBSD team continues to keep a wiki in mind during the next hackathon.
    • Re: (Score:1, Troll)

      by fotbr ( 855184 )
      If only this was a sign that the "a wiki is the solution to EVERYTHING" mentality is dying off.

      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)

        by TCM ( 130219 )

        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'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

        • by fotbr ( 855184 )
          No argument with how it was used in this case -- its a great example of when a wiki truely is a useful collaboration tool, and NetBSD does generally have good documentation.
      • by fotbr ( 855184 )
        Yay, I'm a troll because I don't think a wiki is the magical solution to everything!

        It has its place. But it makes a piss-poor substitution for real documentation.
    • It's really nice to see Wiki software used for it's original purpose, and used properly.
      Unfortunately I can't edit your post to correct the typo.
       
  • ...not noticing this was bsd.slashdot, instead of games.slashdot, I was tricked into clicking on the link by my hopes of hearing that someone recovered the Amulet of Yendor and taken it to the astral plane :(
  • by eneville ( 745111 ) on Thursday November 30, 2006 @06:34PM (#17057468) Homepage
    i wish i had the time to actually contribute, or even read the netbsd kernel. it's got a lot of potential. sometimes i wonder how the linux kernel became more popular than the bsds. net/open do seem more stable in some ways.

Beware of Programmers who carry screwdrivers. -- Leonard Brandwein

Working...