WordPress.org

Making WordPress.org

Opened 4 years ago

Closed 3 years ago

#316 closed enhancement (fixed)

Reference documentation for those with elevated Trac privileges

Reported by: danielbachhuber Owned by: kpdesign
Milestone: Priority: normal
Component: Handbooks Keywords: close
Cc:

Description

This ticket might just have a target of one, me, but I'm thinking it would be nice to have reference documentation for those who have elevated Trac privileges.

In Trac, I can do all of this:

https://dl.dropboxusercontent.com/s/kacdr7vc8bh60wx/2014-02-06%20at%2011.14%20AM.png

The existing Trac documentation is a good reference point for what fields mean. For the most part, it's descriptive of how you use each field to describe different values.

However, some fields require decisions to be made: Milestone, Resolution, and Priority. The Triaging and Punting documentation starts to cover how new tickets are addressed, but doesn't go into enough depth (at least for me).

I guess my questions are:

  • At what point does a ticket go from "Awaiting Review" to a given release milestone, or "Future Release"?
  • If a ticket ends up in "Future Release", what does it need to end up in a release milestone?
  • Besides marking tickets as duplicate, which is mostly obvious, what is the decision making process to close a ticket as wontfix or maybelater?

Context: I came across a 10 month old ticket of mine this morning (#WP24170) that I'd like to get a decision on (commit or punt) and realized I don't know the process. Well, I know the process as "ping someone in IRC" or "try to make a core chat." I'd also like to help go through all of the tickets "Awaiting Review" to help move them along.

Change History (11)

#1 @siobhan
4 years ago

  • Owner set to kimparsell
  • Status changed from new to assigned

Meta trac is generally for code changes across WordPress.org. We're working on a new issue tracker specifically for docs that issues like this will belong in.

In the meantime, I'm assigning to Kim Parsell to bring to her attention.

#2 @siobhan
4 years ago

  • Owner changed from kimparsell to kpdesign

#3 @nacin
4 years ago

There are some code aspects here. We should, for example, offer links directly to the handbook from these ticket fields, to explain their use.

There is a page written by tierra a year ago: http://make.wordpress.org/core/handbook/bug-gardening/. I'm not sure how much it answers your questions. I am all for improving our documentation on triaging tickets.

#4 @kpdesign
4 years ago

Daniel, my apologies for not responding to this sooner.

I read the IRC logs from last night. That information would be best included in the Bug Gardening page in the handbook. Please feel free to edit that page as needed to bring all of that in.

If you have questions, you can also ping me (@kimparsell on Twitter or kimparsell in IRC).

#5 @TobiasBg
4 years ago

Thanks for bringing this up, Daniel! I've also asked my self questions like this.
While triaging bugs is usually rather straightforward, doing the same for enhancements is much more tricky, especially with finding the correct Milestone or deciding on a resolution (For me personally, it's making the decision for wontfix or not.) So, the points made in that chat excerpt are really helpful.

#6 follow-ups: @danielbachhuber
4 years ago

I co-opted Nacin's comment on yesterday's post to introduce a Giving Feedback section. Pretty happy with that now. Doesn't seem to be a way for me to close this ticket, however.

#7 in reply to: ↑ 6 @kpdesign
4 years ago

  • Keywords close added

Replying to danielbachhuber:

I co-opted Nacin's comment on yesterday's post to introduce a Giving Feedback section. Pretty happy with that now. Doesn't seem to be a way for me to close this ticket, however.

Looks good Daniel - thank you. :)

I can't resolve the ticket as fixed and close it either (no Trac privs here), but I did add the "close" keyword. Can someone with privs here close this as fixed please?

#8 in reply to: ↑ 6 ; follow-ups: @TobiasBg
4 years ago

The apostrophes in the Giving Feedback section are all broken for me (I see a diamond with a ? in it.)
Probably some copy/paste/wptexturize issue.
Unfortunately I can't seem to edit that page. When I click "Edit page", I'm taken to the post editor but both Visual and Text Editor are empty :-/

#9 in reply to: ↑ 8 @kpdesign
4 years ago

Replying to TobiasBg:

The apostrophes in the Giving Feedback section are all broken for me (I see a diamond with a ? in it.)
Probably some copy/paste/wptexturize issue.
Unfortunately I can't seem to edit that page. When I click "Edit page", I'm taken to the post editor but both Visual and Text Editor are empty :-/

Tobias, we had an issue this afternoon with the handbook, and I had to restore several pages, that page being one of them. Please don't try to edit it (or any other pages) - I'll get with nacin to get it fixed.

#10 in reply to: ↑ 8 @SergeyBiryukov
4 years ago

Replying to TobiasBg:

The apostrophes in the Giving Feedback section are all broken for me (I see a diamond with a ? in it.)

Related: #195

#11 @kpdesign
3 years ago

  • Resolution set to fixed
  • Status changed from assigned to closed

The original intent of this ticket was to add content to the Core Contributor Handbook, which has been completed.

The encoding issues will be handled in #195.

Note: See TracTickets for help on using tickets.