Behavior of Shift+arrow

goran.hultgren at bluefish.se goran.hultgren at bluefish.se
Mon Nov 18 16:36:55 UTC 2002


Andreas.Raab at gmx.de wrote:
> Goran,
> 
> > I was thinking of adding an SM top category called "Package type" with
> > these subcats:
> > 
> > "Image refactoring"
> > "Package removal"
> 
> Put in [ENH], [FIX], [GOODIE] as well - these are categorizations people
> already know and it would make some automated filtering from stuff posted to the
> list easier. Why not browsing SM for a certain fix?!

Well, Doug and I (and some others) are planning to build a "harvest"
tool similar to SM but accessible to all. It would be for ENH and FIX.
And also BUG I think.

But in the meantime SM would do fine - for those things that people want
more feedback on.

> Also, I think that the perception of SqueakMap is currently more along the
> lines of "large stuff" (for no good reason). It'd be trivial to make a simpler
> registration page just for fixes and collect them right there - fixes and
> goodies often have no "maintainer" no "version" etc. and having to fill in all
> this stuff makes it time consuming (=less attractive) for people to register
> these changes.
> 
> Here's what I'd do: Make up a simpler registration page for "small things"
> which just contains:
> * the title (like "[Fix] ParagraphEditor selection" "[ENH] VMCrashing made
> simple")
> * the author (joe schmoe)
> * the squeak version
> * (optionally) an extra description, and

Yes, perhaps I should. I will think about it.

> * most importantly: an UPLOAD field which allows the upload of up to 50k of
> stuff (everything above would require "full registration")

Yes, we will be adding an upload facility in general I think.

> Then we could even integrate this into the change set handling and have
> something like "post [FIX]/[ENH]" which would auto-register the package and send
> a notification about this to Squeak-Dev (all of the above info is implicitly
> present when you prepare a CS).

That is of course the final goal. But that would be the harvest tool we
are planning.
The idea is that the harvest tool works more or less exactly as SM but
with added features for "reviewing" stuff and marking them as "Ok" etc.
And then finally queueing them up for the update stream. So everyone
should be able to watch the "crop field" and follow a FIX or ENH all the
way through the process. No more wondering what happened etc.

But this tool stuff is typically something you don't want to mix with
SM.

But in the meantime I will add "Package type" with subcats:

"Image refactoring"
"Package removal"
"Enhancement"
"Fix"

And describe what they are intended for. A fix is only interesting to
post there if it is a substantial fix that needs reviewing etc.

regards, Göran




More information about the Squeak-dev mailing list