> Since my first goal is to write something for my animal rights group that > I can maintain easily, I'm really only interested in doing it "my way" for > now.
I think this is a good approach in general, for several reasons: 1. Each project came to this group with particular processes and goals in mind. Participation should not undermine these processes and goals. 2. There are many ways to skin a cat. Each project has a vision of how it's doing things and how the parts will fit together to form a whole. If that vision is allowed to continue to the end, then it has the best chance of producing a coherent piece of software. If it's constantly interrupted, the software can become "design by committee." 3. These are volunteer efforts. If you're not paying someone, you can't expect to direct their approach too much. Volunteers who are spending too much time doing things they don't want to do tend to quit. > Personally, I think a REST API has greater potential than stored > procedures, especially for a hosted service, for obvious reasons. This is an example of what I mean. Stored procedures may be more appropriate for some systems that use a different architecture than the ones we're looking at now. Apparently, the REST API can serve similar purposes. (I'd never heard of REST, it looks like I have some reading to do). I look forward to seeing as these systems (all of which have very different architectures and goals) develop. > That's the Academic Free License. The AFL gives them the right to > relicense the code in the future _and_ to create proprietary > derivatives, > from my reading. > > Of course, the sane way to do this is to simply ask contributors to > assign > copyrights to you when the contribute. Sigh, this disappoints me. I don't like non-straightforward things. I presume they're not asking contributors to sign the code over to them because many people would balk at assigning copyright to a for-profit company. So instead, they found this roundabout way of getting the same rights without contributors realizing it. I have a hard time respecting CiviCRM with stuff like this going on. -- Bob _______________________________________________ software mailing list [EMAIL PROTECTED] http://lists.flossfoundations.org/mailman/listinfo/foundations-software
