On Mon, May 11, 2009 at 07:18, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> Gavin 'Beau' Baumanis wrote on Mon, 11 May 2009 at 09:20 +1000:
>> Hi Everyone,
>> Since taking over the PM role I have occasionally sent an email directly to
>> Daniel Shahaf (the previous PM) for some assistance with threads that I didn't
>> quite know how to handle.
>> I have come to realise that there is a lot of information that goes along with
>> the role (any role, really) that is experienced-based and thought that I had
>> better get these details down for the next PM that comes along.
>> Eg. I only just found out that svnmerge has it's own list - and subsequently I
>> could / should CC that list into a ping email - or simply direct the OP to
>> that list in the first instance.
>> Anywho, my question is;
>> Where is the appropriate place to keep this information (the fine points what
>> to do as PM when "..." happens on the dev list)?
> What kinds of information do you want to document?
> i.e., I'm sure there are things to document --- I'm just not sure that
> "svnmerge has its own list" is one of them.
I didn't know that. I'd say "document it"
>> My initial thought is to submit a patch to HACKING for the PM role - but I am
>> not sure if the "Roles" in HACKING are deliberately "general" in content or
>> simply have lacked some attention.
Attention. It always boils down to that.
>> Finally, if HACKING is not the right placeholder for the "finer points" - then
>> is there more appropriate place for this detail?
> Depends on the level of detail, HACKING may/may not be appropriate. If
> not, the other options would be a new file in notes/ or www/, or to leave
> the information where it is now (in the mailing list archives).
The mailing list archives is obviously not the right answer. There is
absolutely no way to find out what "Patch Manager" means given nine
years of emails.
This stuff should go right into hacking.html. The audience is
*everybody* who develops for Subversion. This is not just some random
few paragraphs for each PM to consume. The developers should be aware
of their responsibilities from/to the PM also.
In short, let's go for MORE visibility. Why freakin' not?
Received on 2009-05-14 11:19:09 CEST