[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 edwardw):

 Replying to [comment:39 jane]:
 > 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 to 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

 How might I do that? So far my other patches have been sitting stale for
 over a month and I'm getting the general feeling of apathy/narcissism
 towards new contributors.

 > 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.

 For example, I've tried making patches for open "feature requests" and
 "bug reports", but they either sit stale and ignored like #14960 or closed
 by biased, politically-motivated people like #17048. It really has an
 effect of turning away potential or interested contributors.

 Again, thank you for taking the time to explain and clarify how the
 process works - I've read around documents on the WP Codex and the
 WordPress development blog, but your explanation certainly helps. Is there
 a more appropriate forum to discuss this and for developers interested in
 feature development such as myself to bring tickets to your (core devs)
 attention?

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