Folks -
As mentioned out earlier, I have emptied the inbox and moved the remaining packages into the treated repository. Specifically this affected: * Collections: The unresolved discussion about #flatten vs. #flattened (see [1], [2]) * CollectionsTests: Tests for both versions * AlienInstaller: The installer package for Alien The latter raises an interesting question: Is there a need for some "extras" repository where community-relevant packages can be stored that aren't really part of the trunk? AlienInstaller would be one of those and there may be others. Such packages definitely don't belong into the inbox (the purpose of the inbox is to identify contributions quickly, deal with them, and move them into treated) but they are also not part of the trunk (the installer really being a meta package). I could see that an "extras" repository might prove useful here. Thoughts? The good news is that the inbox is empty now and looking for more contributions. Keep 'em coming! [1]http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-September/139616.html [2]http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-September/139962.html Cheers, - Andreas |
On Tue, Oct 6, 2009 at 5:25 PM, Andreas Raab <[hidden email]> wrote:
Wow! Good work! Gulik. -- http://gulik.pbwiki.com/ |
I think an extras repo would be cool. I'm in the midst of some
experiments with factoring a skinning infrastructure out of Polymorph, and when I come up with the right approach, it won't look much like polymorph anymore (I could create a new project on Squeaksource.com) and won't be stable enough to go into a base image any time soon. One of the design decisions I've made is to throw out compat with forks, so it does make sense to track the work along side that of the trunk. Another good reason to have an extras repo is: people who are doing work on applications which don't belong in a base image will have the opportunity to participate in the process with the same tools that the trunk uses. So we'll feel the same pain with the outages, etc. This encourages people working on their own projects to contribute fixes to squeaksource, etc. On Tuesday, October 6, 2009, Michael van der Gulik <[hidden email]> wrote: > > > On Tue, Oct 6, 2009 at 5:25 PM, Andreas Raab <[hidden email] <javascript:_e({}, 'cvml', '[hidden email]');>> wrote: > > > > The good news is that the inbox is empty now and looking for more contributions. Keep 'em coming! > > > Wow! Good work! > > Gulik. > -- > http://gulik.pbwiki.com/ > -- Ron |
On 08.10.2009, at 10:18, Ronald Spengler wrote: > I think an extras repo would be cool. I'm in the midst of some > experiments with factoring a skinning infrastructure out of Polymorph, > and when I come up with the right approach, it won't look much like > polymorph anymore (I could create a new project on Squeaksource.com) > and won't be stable enough to go into a base image any time soon. One > of the design decisions I've made is to throw out compat with forks, > so it does make sense to track the work along side that of the trunk. > > Another good reason to have an extras repo is: people who are doing > work on applications which don't belong in a base image will have the > opportunity to participate in the process with the same tools that the > trunk uses. So we'll feel the same pain with the outages, etc. This > encourages people working on their own projects to contribute fixes to > squeaksource, etc. While I agree having an extras repo would be good, I wouldn't see it as repository for applications. Those have a fine place at squeaksource.com IMHO. "Extras" on source.squeak.org would rather contain stuff specific to Squeak trunk, no? - Bert - |
Free forum by Nabble | Edit this page |