[Setools] Gjallar (previously known as Q2) next steps!

[Hans N Beck]

Hi Göran,

Sounds all good. Especially that point with the mailing list, because  
I hoped  that this list could be a platform for such projects :-)

Thanks for your effort to make this project open source !

Regards

Hans

> What I intend to try do this week is:
>
> 1. Set up a swiki with info at http://swiki.krampe.se/gjallar (unless
> someone has a better name FAST). The swiki is up already in fact,
> readonly - see development model below.
>
> 2. Prepare one or two documents we already have (need to scan them so
> that they do not contain any sensitive info). I added a short
> introduction that I cut out from a different doc, it is a bit rough
> around the edges but even though it is more of a "selling the dev
> env"-doc it does contain some other small bits.
>
> 3. Harass my project leader further to nail the license so that we can
> publish code.
>
> 4. Prepare a ready to download "dev env" so that people can join  
> and get
> started without having to put all pieces together manually.
>
> 5. Prepare a dev "howto" describing some doits etc.
>
> When we get more momentum we can turn the Swiki into a nice website  
> and
> get a logo - it is funny how important such things are. :)
>
> I am doing now 1-3 now, 4-5 is not interesting until I have nailed the
> license and can publish the code.
>
> Regarding the model for development I will probably want to run this
> project like this to begin with:
>
> - I am the project leader and will give developer access to  
> developers.
> I will act a bit like Linus does by reviewing and integrating
> contributions into the "official" codebase.
>
> - Developers wishing to participate simply contact me and will be  
> given
> write access to the MC repo and to the Swiki. Each developer should  
> also
> describe himself with at least one sentence on the Gjallar Swiki so  
> that
> we always have a list of the team.
>
> - There is nothing stopping any of the developers joining to start  
> their
> own official "branches" in the Gjallar repo, but I would like to  
> discuss
> that need first.
>
> - The Monticello repo will be open for developers to publish their
> versions into without review. So fixes or enhancements can simply be
> pushed there. Then I will either pick them up and integrate into the
> official codebase or we will move them into some contributions  
> directory
> if integration for some reason is not good.
>
> - Initially we don't create yet-another-mailinglist, we can probably
> start by using this one.
>
> - Only code licensed under the MIT license will be let in, given that
> Gjallar uses that license. :)
>
> - As soon as possible I will set up a Gjallar system for issue  
> tracking
> of Gjallar itself. Eating our own dog food.
>
> Please comment on the above.
>
> regards, Göran
>
> PS. Sorry for the lack of code - I really am trying to get it decided,
> but people are still away on vacation here etc.
> _______________________________________________
> Setools mailing list
> Setools at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/setools