[wp-hackers] How does code make it into core?

Callum Macdonald lists.automattic.com at callum-macdonald.com
Fri Nov 23 01:01:48 GMT 2007


Hey westi,

Thanks for the tip, I'll write that up onto the Wiki if that's ok.

So, to confirm, the way code makes it into core is through one of the 
core devs. Is that correct?

Is there a list of core devs somewhere and relevant specialities? Should 
an appeal be made to an individual dev specifically?

I'm keen to find a way of consulting with one or two key people before 
writing a bunch of code. I understand that a patch on trac is the end 
result, my aim is to find out if there's a way to get "soft feedback" 
before going down that route. I'm not expecting firm commitments, just a 
general position on "yes, sounds like a good idea" or "no, doesn't sound 
like a good idea".

Cheers - Callum.

Peter Westwood wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Callum Macdonald wrote:
>   
>> Following the discussion on WP login cookies[1], how is code committed
>> to core? Is it a case of making an ad-hoc request to someone with commit
>> access? Raising a ticket on trac and hoping it gets accepted? Is there a
>> more formal process?
>>     
>
> In general, to get me interested in your patch you need:
>
>  1. To have a clearly defined, explained, demonstrable problem or
> feature request.
>  2. To have tested this patch and provide enough information to allow me
> to test it.
>  3. To have documented using phpdoc any new functions you are adding.
>  4. For all the above to be on trac.
>
> Things that make you patch even more appealing:
>
>  1. A history of good contributions to the community
>  2. Constructive response to feedback.
>
> Cheers
>
> westi
> - --
> Peter Westwood
> http://blog.ftwr.co.uk
> http://westi.wordpress.com
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFHRfmFVPRdzag0AcURAmaeAJ9uwCT5QTNzABvKEsMCD7D/Fqni/wCfanBg
> Ey7+T00nVTpdCUp6tlHJVTc=
> =ZoB+
> -----END PGP SIGNATURE-----
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>
>
>   



More information about the wp-hackers mailing list