From: Alessio S. <ale...@gm...> - 2008-09-25 10:06:20
|
On Thu, Sep 25, 2008 at 11:50 AM, XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX wrote: > On Thu, Sep 25, 2008 at 11:06 AM, Alessio Stalla > <ale...@gm...> wrote: >> I have a basic working implementation now. If Erik is ok with it, when >> I return home this evening I can send him the code so he can put it >> into the repository. I just need to put a summary of the license at >> the beginning of each file, I'll copy it from ABCL source files. I >> don't know how svn commit privileges work, but it would be a great >> thing to have, especially in this early phase when a lot of things are >> subject to change... > > Well, in open source it works this way: depending on your role and > contributions, the project maintainer(s) may decide to grant you > commit access; sometimes to specific parts of the repository. > > Before you send me the code, I think it would be good to discuss where > in the source tree it should be stored. Inside the lisp/ directory > might be less handy, because of the fact that it will be harder to > exclude the files when making a 1.5 build. > > This becomes less of an issue if we create a lisp/javascripting > directory though. How did you intend to name your package? > > If you didn't come up with a name yet, how about: > org.armedbear.lisp.javascripting ? > For now, it is named abcl-script. This would not fit very well in the org.armedbear... package hierarchy, so I think ...scripting as suggested by Ville is better. > > I quickly considered how to get the code into the repository and get > you two working on it. This is my proposed plan: You send me (or the > list whichever you prefer) the code tonight, so I can have a look at > it. If I have any comments, I'll send them in response. > > In the mean time, I'll try to get you two set up as committing members > of the project on common-lisp.net. This may take a few days. I'd like > the two of you to commit directly to the repository, but we'll set up > a branch for your work (to be integrated into the trunk when the code > is less "in flux"). I'd appreciate it if you didn't commit to the > trunk yet without prior notice (partial commitership for the branch). > Then, after a while, when we're all settled and in agreement of the > quality of code we're trying to deliver, we can agree that you can > commit anywhere you like (full committership). > > > How does that sound to you? > Sounds good :) Bye, Ale > > Bye, > > Erik. > |