Re: Plans for next release?

To Dave, yes it will be/is an open source license.  We wouldn't change
that, and we'll either just do a BSD-style template license or use the
Python Software Foundation License, if only for the added feature that
it's listed on opensource.org as a blessed open source license.  ATM I'm
looking at the details of the second (I'm familiar with how to go about
the first).

On Thu, 2004-08-05 at 05:00, Fabian Fagerholm wrote:
> Just throwing ideas into the air here, but how about setting up a public
> CVS (or similar revision control system) repository for development of
> Albatross-based toolkits?
> 
> Object Craft could maintain the "Albatross" branch, which would have a
> conservative release policy. The "SnakeSkin" branch, while not being
> labeled as a development or unstable branch, would allow new features to
> enter more quickly and would have a rapid release cycle. Any number of
> development branches could exist for experiments and testing.
> 
> Would it be possible for Object Craft, Mediapulse and the Open Source
> community (Debian in particular) to collaborate in this way?

So this would be like Mozilla, with both Mozilla suite and Firefox
projects.  I like the idea because it lets each project tailor itself to
the developers closer (Mediapulse not concerned with past code as much
as ObjectCraft).  I know in the past this has come up and maintaining a
public cvs server isn't something objectcraft wanted to get into, and
neither would mediapulse, this isn't the only project on our cvs server
=).

I'll step in here and say though mediapulse can take care of getting the
server and details though something like sourceforge, which is pretty
much what we would have done anyway.  That will give us a public base
for a bug system, mailing lists, homepage, cvs server, downloads, etc. 
I know from first hand experience sf's servers are sometimes a pain to
deal with (and down at the worst times for a developer, lol), but they
do support a great number of projects that cope so we could too.  This
way, the only thing objectcraft would need to do it check in albatross
to sf's cvs server and keep it in sync with their local server.  The
project can be called something generic like python-web, with two
modules in the cvs server, albatross and snakeskin.

Other than the cvs server, and maybe the release tarballs in the
downloads section, it's up the the objectcraft guys how much of sf they
want to use.  Having a mailing list, wiki, etc already I'm sure I
wouldn't want to move that if it were us, at least not at the start.

If the above sounds good, let me know and I'll get the ball rolling.

Mike