Would it be useful to designate a Patch Master for each release of TWiki?
This role would be the person to which we could direct requests for getting patches made to the core.
I think it would be better than directing questions to 'CoreTeam' and then hoping that someone will read and decide to give an authorative answer to the message.
Comments?
--
MartinCleaver - 30 Aug 2002
Agree. This is how other
OpenSource project are managaed, IMHO. And let's call him/her
TWiKing for short!
--
PeterMasiar - 30 Aug 2002
Hmm
Let's not call him
TWiKing On second thoughts though I think it would be useful to have a category or keyword that a list can be generated from. Something like:
%SEARCH{"ForAttentionOfTWikiPatchMaster"} %
--
MartinCleaver - 01 Sep 2002
A patchmaster is a good idea - the Perl people call this person the Patch
PumpKing but we don't have to have the word King in there...
TWikiPatches already exists to list TWiki patches, so something a bit more structured than this would be fine. It should be a form field in Codev, not just a
Wiki:WikiBadge, to make it easier to log patches through states such as 'up for consideration', 'in rework', 'applied to alpha', and 'in release'.
With more active submission of
high quality patches, TWiki development could go a lot faster - by high quality, I mean with error checking, well tested, following the TWiki coding style and Perl version targets (see
ReadmeFirst, and also structured as a unified / context diff that is easily applied to TWiki. We should produce some
PatchGuidelines to help people do this.
Please let's take the opportunity to
rework the current Codev form fields - they are ridiculously hard to use at present, since the whole 'Project' idea doesn't seem to have taken off. I made quite a few suggestions in this area under
CodevFields - it would be good to see some discussion of this.
--
RichardDonkin - 02 Sep 2002