[wp-hackers] How does code make it into core?
Peter Westwood
peter.westwood at ftwr.co.uk
Thu Nov 22 21:49:57 GMT 2007
-----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-----
More information about the wp-hackers
mailing list