Slashdot Mirror

← Back to Stories (view on slashdot.org)

Ask Slashdot: Spreading the Word About At-Risk Open Source Projects?

Posted by timothy on from the do-not-go-gentle-into-that-good-night dept.

An anonymous reader writes "There is a piece of software, released under the Modified BSD license, that risks becoming abandonware and, IMHO, is worth being saved. Where can I post an announcement to find people than can take care of it?" This seems like a problem that a lot of projects run into; is there a clearinghouse for open-source projects at risk?

3 of 115 comments (clear)

  1. Re:Try to get the license changed to GPL by Chemisor · · Score: 1, Interesting

    The problem with GPL is that nobody can take the code private and make money selling it. Many people like me think this is unfair and tend not to provide unpaid work. I sometimes send bug reports to a GPL project, but would never even consider contributing any code. GPL people feel the same way about my MIT licensed projects. So before you change the license, be sure you are on the side you want to be on. I have no numbers, but you should not just assume one side is larger than the other.

  2. Re:what's the name? by 6Yankee · · Score: 3, Interesting

    If the submitter had given the name, the comments would be full of people bitching about slashvertisments.

  3. Which repo requires GPL? by tepples · · Score: 3, Interesting

    The OP's situation involves software under what appears to be a 3-clause BSD license, which is a GPL-compatible free software license. Which repositories require specifically the GPL as opposed to GPL-compatible free software licenses in general?