[Special Report] 3.6 is out, now what? :-)
ducasse
ducasse at iam.unibe.ch
Wed Oct 8 14:18:07 UTC 2003
Hi goran
I like your list. It is a good goal.
I would add the event notification of Roel because we can build a lot
of nice tools
with that.
I would add: we NEED harvesters for special areas such as etoy, morph,
concurrency and network.
Stef
On Mercredi, oct 8, 2003, at 17:05 Europe/Zurich,
goran.krampe at bluefish.se wrote:
> Personally I think that during the 3.7 iteration we should at least
> consider doing these things:
>
> 1. We (guides) have started trying to formulate a vision that we stand
> by. This is still very much in its infancy, but I think one goal for
> 3.7 is to get that out.
>
> 2. I think we should at least try to rotate one Guide. Rotation was a
> key idea from the beginning and I think it is healthy for the
> community.
>
> 3. Make a targeted effort at "harvesting" many of the enhancement
> packages currently living on SM. Many of those actually belong in the
> base image packages.
>
> 4. Get the new Compiler in. The word is out that SmaCC is now
> available under MIT so the license question is out of the way. Let's
> get this stuff in! It would be a real shame if all that work Anthony
> did got wasted...
>
> 5. Get Babel in and squeeze out a few translations. Already much on
> the way.
>
> 6. Split out at least ... 3 (?) more packages from Basic.
>
> 7. Get the TimeStamp/DateAndTime-whatever-package in. I am getting
> bored at including that in SM...
>
> 8. Whatever stuff that comes out of KCP and MCP of course. :)
>
> 9. General harvesting, and perhaps have a "BFAV crash course" during
> the iteration to pick up more users and thus speed through more
> eyeballs.
>
> 10. Come up with *anything* regarding bug tracking. Both for the image
> and for packages. SM2 can help a bit.
>
> 11. Start thinking about Stewarding areas of the image using
> PackageInfo definitions (without necessarily splitting it out). This
> way we get someone "in charge" and bug tracking, decision making etc
> gets much more defined.
>
> 12. And of course... get SM2 up and running. :-)
>
>
> Now, this is by far a full list of candidate tasks. There are tons
> more that I both didn't think of rightnow or even purposefully left
> out so that other people get a chance to pipe up.
>
> over and out for now, Göran
>
> PS. If people simply throw out candidate tasks I will gather them up
> to a grand list which we then can prioritize.
>
More information about the Squeak-dev
mailing list
|