are re-used time and time again and perhaps could be put in an official list.
However, I'm not surprised that people are not jumping towards codifying
the keywords list into a strict guildline. If you want to give the new users
advice, then grab the most popular ones you see and write some
description. Making keywords "official" at this point is probably overkill, but not so
far in the future as to be useless.
> or should I just tell potential contributors to ignore them?
I think that's overkill. How about, "If you notice your patch being ignored
or want to mark it for attention, then please use sensible keywords
when creating a patch or bug listing.
How does that work?
-hampton.
On 5/15/06, Josh Susser <
[EMAIL PROTECTED]> wrote:
Trying this again, since it was ignored last time (May 10). I've had
over 1700 downloads of the PDF slides from my presentation. Would be
nice to include the keyword list in the update I'm putting together
now. Is there any interest in using keywords on tickets, or should I
just tell potential contributors to ignore them?
-------------
In putting together my talk about contributing to Rails, I realized I
couldn't find any write-up anywhere of what keywords are used for
tickets in Trac. It seems that people just put any old keywords on
tickets, sort of like tagging photos in flickr. But I know there are
at least a few keywords that matter, like "docs" and perhaps "tiny",
and ones used at release time like "needs_review". Does someone know
of a standard list? If not, would it be possible to put our noggins
together and come up with a list of keywords that the core team cares
about?
--
Josh Susser
http://blog.hasmanythrough.com
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
_______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
