Dear Harvesters,
First of all, I also want to thank you for doing this work, it's really
important.

And now a request - is it possible to make sure the you give some
indication as to the fate and faults of anything considered for
inclusion but rejected?

I'm assuming that you scan everything submitted. Some things have
problems, some things seem to be of no interest to the public, and so
forth. As a contributor, I'd like to know which felled my contributions,
and seeing as you already review everything, it should not be hard to
get this feedback to the authors. I know this is more work, and you're
already undertaking quite a bit, but I think it's really important.

Otherwise people have to either ask (which is more of a bother) or
assume things that are probably not encouraging them to contribute
further...

A mail to the list enumerating the issues with each submission not
accepted seems like a good way to do it.

This could also be a spur for people to talk about what submissions they
do and don't care about, and for fixing/improving those that merit it. 

I think this feedback/disscussion/improvement is a really important part
of an open source community, and making decisions about contributions
more visible would help it a lot.

On another side of the same coin -
There are a few of us (Lately - Mike R., Lex, Leandro and myself,
sometimes other members too) that are maintaining and enhancing Celeste
over time. On one hand we'd like to tighten the release loop in order to
have a clear platform to work on, and on the other hand we know you
Harvesters are busy, so we prefer to give you less work, not more.

We were thinking of starting to maintain Celeste on a repository, so we
can integrate changes into one official version independently of the
Harvesting process. This would give us and Celeste users a faster
evolving package, and we hope you will find it easier to simply take our
integrated changes from time to time, and update the image accordingly.

Does this sound reasonable, am I missing something, or do you have other
ideas?

Daniel Vainsencher

Doug Way <dway at riskmetrics.com> wrote:
> 
> Speaking as one of the Harvesters, I should clear up a little confusion about recent submissions being left out:
> 
> The last set of [Updates] actually covered submissions from the period of December 4, 2000 to August 23, 2001.  So, we still need to review the submissions from the last month or so.  Since Dan is about to move 3.1alpha to beta status, we would probably consider mostly just bug fixes for the 3.1beta stream, not enhancements/goodies.  (SUnit 3.0 might be an exception.)  Tim's fix definitely counts as a bug fix, for example.
> 
> Goodies/enhancements will definitely be reviewed for inclusion in the 3.2alpha stream, of course.
> 
> - Doug Way
>   dway at riskmetrics.com
> 
> 
> Tim Rowledge wrote:
> > 
> > Dan Ingalls <Dan at SqueakLand.org> is widely believed to have written:
> > 
> > > Folks -
> > >
> > > As promised, here are a bunch of recent updates from SqC, along with 35 others harvested from the past by Doug Way (many thanks, Doug!).  This brings us pretty much up to date, and I plan to take 3.1 to beta tomorrow, as per my message yesterday ("Re: About Squeak evolution").
> > I still need the attached fix to AcornFileDirectory incorporated. Unless
> > people want this to be the first release in years to break platform
> > portability? I think that would be a shame.
> > 
> > tim
> > --
> > Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
> > Disc space, the final frontier!
> > 
> >   ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> >                                                     Name: AcornFileDirectory-directoryContentsFor.st.gz
> >    AcornFileDirectory-directoryContentsFor.st.gz    Type: application/riscos
> >                                                 Encoding: base64