[Squeakfoundation] Harvesting rules (was Re: Harvester status for Marcus Denker)

Brent Vukmer bvukmer at blackboard.com
Tue Jun 10 16:13:42 CEST 2003


> 
> Anyway, a good start on getting a policy going might be to create a 
> standalone tool which operates on a changeset, which would check for 
> things like class comments being in place for newly defined 
> classes.  It 
> could also run some subset of SLint tests (whichever rules we 
> agree on), 
> so SLint would be a prerequisite of the tool.  (One issue I ran into 
> with SLint is that it would be nice if it could just be run on the 
> changed code, not the entire method.  That might not be simple to 
> implement, I realize.)
> 
> Plus the tool could have a few simple checks to make my life as the 
> update-stream manager easier, such as making sure the changeset name 
> isn't too long, doesn't have funny characters in it, etc.  (Simply 
> forcing it to be a changeset is even of some value... for example I'm 
> about to incorporate Michael's network rewrite, but that's a 
> SAR file, 
> so I have to incorporate the 10 or so changesets/fileins separately, 
> some of which could probably be combined, etc.  Not a huge 
> problem but 
> still it's a bit of extra work for me.)
> 
> Then the idea would be that any submission must pass through the tool 
> before it is [approved].  The harvesters could use the tool at first, 
> but eventually people submitting things would want to run submissions 
> through the tool themselves.
> 

Doug, it's like you're reading my mind.   The one thing I would add to
your list, is that this tool should register with the FileList.

If this tool existed, and registered with the FileList, it would
automagically be available in the BugFixArchiveViewer.


More information about the Squeakfoundation mailing list