Re: RFC: wnpp bugs tagging
On Wed, 12 Mar 2008, Luca Brivio wrote:
Yeah, I'm been doing this with a few RFPs, this is a best practise for me. Of
course there are two problems:
1) Many interested persons aren't subscribed to (all) the relevant mailing
lists (think of new maintainers, and so on).
Right. They probably are not subscribed because their time scale does
not allow to follow the list. If this is the reason they most probably
will also refuse to pick up a RFP bug and do not need to be informed
anyway.
2) Sometimes there's no really relevant place!
In this case there is nothing to do.
Anyway those problems don't change so much items we're discussing about. :)
Yes.
It is indeed (together with set lists of tags, perhaps policies, etc.).
There's just a difference between people each tagging their own bugs and me
tagging those left untagged by others. :-)
I agree that tagging is a really omportant thing. But tagging alone
does not really help if people do not check WNPP for tags that are set.
The tags are only relevant for those people who are querying the BTS
for tags which means tags are a source of information who actively seek
for it. But my aproach to push information to people by sending a
mail to those who are potentially interested will reach those who are
not actively running a query against BTS.
Alright. So we maybe should let external contributors put data on the wiki and
then remove them once they have been added to tasks. Including a disclaimer
about this in the wiki pages would be really useful! and I can do it myself.
This sounds like a reasonable idea. There should just be a hint in the
wiki to verify that the project you would like to mention is not yet
included in the auto generated page.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: