Hi Mike, Sounds like an interesting project. We generally stick with GNU but in some cases incorporate MIT stuff (and the accompanying license) when it makes sense for our clients.
The biggest deciding factor for us is our target market, but at the moment we have no clients who seem to be overly concerned about this issue. As a non-profit If the product we are producing is something that we really want adopted commercially with no hesitation by even the most picky clients (for example accessibility enhanced products) then we may go with MIT in cases where one or more of our target markets seems overly concerned about real or perceived issues surrounding GNU. Other than that GNU is pretty much our standard unless of course we are building on pre-existing MIT stuff. So in a nutshell I would say it depends on your target market and your market strategy so to speak. We want to encourage as many people as possible to participate in anyway they choose to including contributing to the code base and feel that GNU is a way to attract individuals with similar goals and strategies. MIT works for us as well and satisfies some more traditional strategies as well as allowing "sharing" and sometimes when we don't feel we could do a better job on MIT products we incorporate them cause they are are of good quality and are highly accessible (open source, no cost and/or licensing fee) to everyone. On Google Code We use Google Code and we really like it. Again it is highly accessible (low cost and works with most TTS) In addition Google was nice enough to bump up our project limit as well due to our official non-profit status just because we asked and as you mentioned it works well with Mercurial, our fav versioning system. In addition we use Eclipse which can be configured to Google Code / Mercurial ... all for no cost so we find that it is a hard combo to beat although it would be nice if someone did! Cheers, Chris On Aug 16, 4:14 pm, Michael Ellis <michael.f.el...@gmail.com> wrote: > Hello all, > > I've been working for the past few months on a group collaboration and > problem solving application and am almost ready to put up a beta > version on GAE for folks to experiment with. Many thanks to Massimo > and all of you regulars here for helping me up the learning curve! > > The app is called PeerTool and is a complete re-write in Python and > web2py of a commercial app I developed in PHP about 6 years ago. My > intent is to provide a free public access site that any group may use > and also to release the code open source. > > I'll post an announcement here when the time comes, hopefully in the > next week or two. In the meantime, I'd be grateful for advice or > suggestions in two areas: > > 1. Choosing the most appropriate license. My primary goal is to > make the product as widely useful and available as possible. I > believe it could be of benefit to almost any team, task force, board, > or committee that wants to use brainstorming and collaborative > evaluation of ideas (with real-time interaction!). > > 2. Most appropriate hosting for the project source code. I've never > started a public project before and would like to know what > experiences others have had with Google Code, SourceForge, etc, -- > especially concerning web2py apps. I'm leaning toward Google Code at > present. My code is already under Mercurial so it seems like that > would be a good fit. > > Thanks in advance, > Mike
