On Warp Pipe, Open Source, Closed Source

An anonymous reader writes "There's an interview with the developers of GameCube tunneling util Warp Pipe over at the O'Reilly Network. One of the main issues asked was why they elected to close the source code for their project, when they started Warp Pipe originally as an open project. Quick summary: They appeared to use open source as a means to recruit people, but then closed it soon afterwards because they felt that managing an open project would be too much of a hassle compared to maintaining a closed one. I wonder: What are the unwritten 'rules' that the general open source community abides by for opening and closing code?" Although Warp Pipe has created controversy before, it does seem it's now an effective "online service that brings GameCube players together for gaming sessions", something to be applauded.

Comments

yeah and....?

[mwheeler01]

If a contributor wants his code to be open source, there's nothing stopping him from releasing the code unless he signed a confidentiality agreement with the project. If a contributor wants his code undisclosed that's his right as well.