[wp-hackers] Trac etiquette

[Kurt Payne]

Hi Gavin,

See the Core Contributor Handbook here:
http://nacin.com/projects/core-contributor-handbook/the-bug-tracker-trac/

And there's some supplemental info here:
http://codex.wordpress.org/Reporting_Bugs

And you can always ask in IRC (conditioned upon availability).

--Kurt


On Tue, Jun 19, 2012 at 1:31 PM, Gavin Pearce <Gavin.Pearce at 3seven9.com> wrote:
> Could someone take a moment to clarify Trac 'etiquette' for me please?
> Or point me in the right direction?
>
>
>
> Having just submitted a [albeit stupidly simple] patch
> (http://core.trac.wordpress.org/ticket/21017), I've added the keywords,
> and assigned to nacin for review (as nacin suggested the patch). Is this
> what people want and what works best for them? Don't want to offend
> anyone by assigning them work.
>
>
>
> The Action section at the base of a ticket (leave as reviewing, resolve
> as fixed, reassign review to, accept etc)  all seem like tasks that
> should be left to core committers, perhaps with the exception of
> reassign review to someone to test/feedback?
>
>
>
> Any guidance much appreciated. The Codex touches on the various tags and
> actions, and what they mean, but not when to use them (in the case of
> actions) - or more importantly: who should  be using them.
>
>
>
> Gav.
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers