It is completely our choice who can change the keywords associated with an issue. Similar to nosy lists, it is probably best not to be restrictive, allowing anyone who can post an update (ie, in our case a logged-in user) to do so.
<br><br>There was a discussion on this topic that I think came to a conclusion although I don't know what it was; I thought it was that we would create appropriate keyword(s).<br><br>This should NOT be a showstopper in that whatever the scheme it should not take me much time to modify the weekly reporter appropriately, once I know the scheme. If in a worst case I missed a week or two the sky would not fall. The basic report works now.
<br><br><div><span class="gmail_quote">On 1/29/07, <b class="gmail_sendername">Brett Cannon</b> <<a href="mailto:brett@python.org">brett@python.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 1/29/07, "Martin v. Löwis" <<a href="mailto:martin@v.loewis.de">martin@v.loewis.de</a>> wrote:<br>> Paul Dubois schrieb:<br>> > I volunteer to be the person who fixes account problems, emails, etc. I
<br>> > am off 5 days a week so I think I can get it done faster than most of<br>> > you. I'm for letting it rip.<br>> ><br>> > I never got an answer to the question of how the patches would be marked
<br>> > so that I can make that report on the weekly.<br>><br>> I think this still is a show-stopper.<br>><br><br>Agreed.<br><br>Should we have a 'patch' keyword? Don't remember if anyone logged in
<br>can change the keywords, though, let alone attach a file to an issue.<br><br>-Brett<br></blockquote></div><br>