On Thu, 03 Nov 2005 09:51:06 -0800 Blake Barnett <[EMAIL PROTECTED]> wrote:
> David Seikel wrote: > > > > >I agree, a separate modules (but not e17/modules) directory, > >e17/proto if we have to, or cvs at edevelop.org in that order of > >preference for me. > > Ok. I'm fine with having everything in the main CVS tree (themes > also?) but part of the problem I'm trying to solve with this is that > a lot of times, if things DON'T get put in the main tree, or people > don't have CVS access in the beginning which is usually the case, > that work is UNKNOWN. I want to raise the visibility. So that > people can see what's being worked on, what the state is, how they > can help, and make it EASY to do that. > > I think edevelop.org is a great place to put new projects, even those > that shouldn't ever go into E CVS (as long as they are E related). Doh! I forgot to consider having to give cvs write access to every module writer. Good use for svn on edevelop.org. Of course, as you know Blake, I've been playing with the project module on edevelop.org, and I was asking for some sort of code repository, please go with svn if possible. And for the person that keeps emailing me in private when it should probably just go to the list - I consider that the e17/* cvs directory should only be used for things that will be an official part of E17. The main e17 developers decide what is and isn't official. I don't like that proto is in there, as I believe that proto is for things that are not yet finished enough to find a proper home. I'm guessing that misc is for unofficial things. On the other hand, I'm just a n00b here in e17, I haven't been around long enough to learn the One True Way.
pgpYi14EKMxp0.pgp
Description: PGP signature
