[wp-hackers] wp-hackers Digest, Vol 81, Issue 21

[sam auciello]

Thanks Mike,

I actually got a couple of smaller patches in this past week myself.

The class is actually self designed so it's pretty open ended.  My hope is
to make a significant contribution of some sort to a collaborative effort,
so a plugin would be less interesting to me.  The class is a semester long
so it ends in December.  What is the timeline for 3.3, is there a place I
can find that in trac?  It doesn't matter much if my contributions don't
come into effect until the next release.  I'll start looking in {32} for now
but if anyone has any ideas, I have a good deal of PHP/CSS/JavaScript
experience so please feel free to send me ideas.

Peace
~Sam

Sam,
> I'm new to the WordPress project myself, but managed to squeeze a few
> patches in before the 3.3 cutoff.
>
> The WP Trac statuses seem to be managed by consensus, so patches may need
> review before the status is updated. Also any tasks slated for the upcoming
> release are typically assigned or at least actively managed by the core
> team. So tasks listed as needing patches but having patches attached
> sometimes are just waiting on those people to review them.
>
> What's the timeline for your class project? If it's longer than a few weeks
> you can pick a feature request task. If it's shorter then the timing of 3.3
> hitting beta means many tasks to be included with this rev are near-done or
> going to get punter to the next release. ...which means you'll need to
> figure if your class just wants you to contribute, or if you actually need
> to get code included in a release.
>
> Another valid option is to write a plugin or theme for WP. These are all
> tied to WP and thus GPLed too. They're also a part of the WordPress
> ecosystem and essential to make the core successful. Plus, you can control
> the timeline and size of these better than core tasks too. If your class
> requires you to do something collaborative you could always start one of
> these and then ask this hacker's list for someone with time to
> co-contribute.
>
> -Mike
>
>