[GRASS-dev] GRASS at GForge first steps
jachym.cepicky at centrum.cz
Tue Nov 7 02:10:59 EST 2006
On Tue, Nov 07, 2006 at 06:11:08PM +1300, Hamish wrote:
> Jachym Cepicky wrote:
> > I will do it (try to do it). What exactly am I supposed to do? My
> > imaginatio is following:
> > - Someone will submit some patch to wald
> > - I (or someone else) will examine the patch, look if it does what
> > it is supposed to do and paste my comment about this patch to
> > grass-dev list
> > - If it will be only small correction, I'll apply the patch to CVS
> > immediately
> > - If it will be bigger change and nobody will complain in
> > grass-dev
> > within a week or so, I'll commit the change too.
> > Anything else? Or do I understand this task completely wrong?
> I prefer to be more conservative, adding code to CVS should be opt-in
> not opt-out. A patch needs a developer-supporter to give it the ok,
> versus falling into CVS by default.
So if I understand it right, the last point in my decision tree will
- If it will be bigger change and there will be no consensus
agreement, I'll leave the patch uncommited.
Is it right?
> (see PSC code accountability
> requirements) I don't think it is bad that many patches could collect
> there, or at least that is better than bad patches falling into CVS by
> default because devels were busy that week.
> 10c, (NZ just abolished the 5c coin, and abolished the 1,2c coins in the
> early 90s; but after the exchange rate the 10c is a lot less than it
> sounds ;)
e-mail: jachym.cepicky at centrum.cz
Department of Geoinformation Technologies
613 00, Brno
e-mail: xcepicky at node.mendelu.cz
Tel.: +420 545 134 514
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 191 bytes
Desc: Digital signature
Url : http://lists.osgeo.org/pipermail/grass-dev/attachments/20061107/45054817/attachment.bin
More information about the grass-dev