[wp-trac] [WordPress Trac] #11651: Welcome Screen concept

[WordPress Trac]

#11651: Welcome Screen concept
----------------------------------------------+--------------------------
 Reporter:  dd32                              |       Owner:  koopersmith
     Type:  task (blessed)                    |      Status:  assigned
 Priority:  normal                            |   Milestone:  3.3
Component:  Administration                    |     Version:
 Severity:  normal                            |  Resolution:
 Keywords:  has-patch dev-feedback 3.3-early  |
----------------------------------------------+--------------------------

Comment (by jane):

 Replying to [comment:38 edwardw]:
 > Replying to [comment:36 jane]:
 > > Replying to [comment:35 edwardw]:
 > > Hi @edwardw. Only a member of the core team should change the owner
 field, and it will generally be a member of the core team that "owns" the
 ticket/is responsible for overseeing it and committing it. Please don't
 change that field.
 >
 > So basically what you're saying is that developers interested in feature
 development such as myself are simply shafted, ignored and then told to go
 away.

 No, in that comment I was trying to politely let you know about the
 protocol. Some fields (milestone, owner, setting component as task
 (blessed)) are meant for the core team only, and are used to manage the
 entire project. Anyone can contribute the patch that will be committed, it
 has no relation to ticket ownership.
 [[BR]]

 > This ticket sat almost untouched for 20 months, then I thought I might
 come and help to try to make a welcome screen, then this "koopersmith"
 user comes in and pays no attention to my work whatsoever.

 "This 'koopersmith'" is a member of the core tam and is the person who was
 assigned the task in our IRC meetings and listed on the
 [http://wpdevel.wordpress.com/2011/07/27/wordpress-3-3-proposed-scope/ 3.3
 project scope doc]. We probably should have linked to when it was
 confirmed, and noted the change in direction. Putting communication in all
 channels (IRC, wpdevel blog, Trac, hackers, etc) is something we need to
 get better at, but no malice was intended here.
 [[BR]]

 > Same thing with the other patches I've submitted - they sit there stale
 and then some narcissistic user will come along and ignore my work.

 Every release we have an open scoping meeting in IRC that is publicized
 ahead of time on wpdevel. Once the scope has been set in that meeting,
 those are the tickets that will get core team attention (aside from
 interruptive security issues). Anyone who wants to advocate for a ticket
 they'd like te see get in (that isn't on the approved version scope) can
 get core team attention by getting traction on the ticket and getting
 people to test the patch. If a patch is well-tested, you can ask in IRC
 for it to be reviewed even if it's not in scope, if it is before freeze.
 [[BR]]

 What you ascribe to narcissism is in this case merely the agreed upon
 scope and assignments for 3.3. I'm sorry there was a communication gap,
 but we have thousands of tickets on trac between the current version,
 future release, and awaiting review, so it's impossible to follow all the
 tickets while also working on our tasks for a release. We often work a bit
 heads down on our assigned tasks until we have something that's ready to
 post for feedback. Hopefully now that you know the process, it will be
 less frustrating in the future. Sorry for the frustration and poor
 communication.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/11651#comment:39>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software