--- John Beppu <[EMAIL PROTECTED]> wrote:
> However, you don't have to chronicle your every
> little move.  For example, if you need to reformat
> a few lines of code here and there
> or add a few comments, just do it.
> 
> Use your judgement to determine what's noteworthy
> and what's not.

I just want to say a few quick words about how I
see this working:

1.) SVN will be a development branch, it will not
directly go into CPAN, rather I will run a diff
on the SVN banch from time to time, read the
changelog,
and apply as necessary.

2.) If you don't add an entry into the changelog for
a change, and I find something in the patch that
doesn't match with any given entry, I will ask the
list
why someone did something.  You better have a good
reason :)

3.) Any API changes or additions should be discussed
first on the list, and in private.  Most of the
existing API is the result of actual USE, which is
why things aren't always orthogonal.  A usage case
will usually win an API change argument.

4.) I will appoint a co-maintainer or two in CPAN
now that the permissions have been straightened out.
If you are going to contribute code or act as a 
co-maintainer, I don't want you pushing any code to
CPAN without me saying "go ahead".


What does this mean to you?  Well it means I will use
subversion as a "patch submission" system, all patches
made to the subversion system, with CHANGELOG entires
will be accepted as submissions under the LGPL.

I'll bundle those changes I think make sense, and
for which people can come up with compelling
arguments,
in what will be the "official stable version" which
will appear in CPAN. 

Hopefully that will give us a sufficiently flexible
development branch for people wanting to take SDL perl
in new directions, but keep enough stability that
people can use it.

Personally, I'd rather see more time spent building
applications using it rather than altering the API.

Sound good?

Dave


__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools

Reply via email to