[Zope3-dev] Re: [Zope3-checkins] CVS: Zope3/lib/python/Zope/App/schemagen Zope3/lib/python/Zope/App/schemagen - New directory

Casey Duncan casey@zope.com
Thu, 12 Dec 2002 09:03:09 -0500


On Thursday 12 December 2002 03:07 am, Steve Alexander wrote:
> > That wasn't everyone's reaction, though.  Mine, at any rate, was that
> > the schema generator was getting stuck in a non-obvious place in the
> > hierarchy.
> >=20
> > I rather expected something like this would show up inside some other
> > package related to schemas.
>=20
> Sure. Martijn and I debated this, and we decided that seeing as we're=20
> sprinting and we don't yet know how it will turn out, we'll just put it=
=20
> somewhere moderately sensible, and think about moving it later.
>=20
>=20
> Meta-comment directed at no-one in particular:
>=20
> When a sprint is going on, as a sprinter, it is kind of irritating to=20
> have a running critique of the ongoing work at the sprint. I feel=20
> copmelled to respond to this, and try to explain the rationale and=20
> direction of the sprinting. However, I also think that this is=20
> counter-productive, and my time and attention would be better spent on=20
> the sprinting activities.

I completely disagree, just because someone is not at the sprint should n=
ot=20
make it impossible to interject something or create a discussion. That sa=
id,=20
email is wholly ignorable until later, so if the person is uninformed (wh=
ich=20
is likely the case since they aren't there), just ignore them until you h=
ave=20
time to rebuke their comments. Or just send a "bear with it until we can=20
explain" reply.
=20
> I suggest a general principle that refactoring and moving stuff around=20
> and renaming stuff can happen after a sprint.  The sprinters are people=
=20
> who are best informed to discuss such refactoring. However, we don't=20
> want to distract them during a sprint, so we'll have such discussions=20
> after the end of a particular sprint.

I agree that such refactoring is best done when no sprint is underway. It=
=20
should probably be done on a branch anyway so as not to upset everything =
in=20
the process.

-Casey