Joseph Scott: we can definitely use more people looking at the XML-RPC and AtomPub code.
My experience matches Jeff’s, namely that post 2.3; contributions of time in terms of showing up on the IRC channel; producing and commenting on both bug and feature requests; and in terms producing actual patches, rarely produces the desired result. An en example, this ticket was explicitly opened based on a request from Joeseph in order to obtain feedback, and to date it has received none.
That’s fine — I for one certainly have plenty of other places to focus my attention — but if the WP team wants more people looking at ares such as XHTML, Atom and/or AtomPub code, IMHO there needs to be a person with commit access to the codebase who is actively engaged in facilitating these efforts.
I appreciate the frustration of not getting the kind of feedback you are looking for from WordPress. I wonder if this is a situation where it would be better to decide the desired best practice apart from WordPress in particular, and then you would have some behavior to endorse as “appropriate” for not only WordPress but for other blog systems as well.
It’s one of the big limiters on AtomPub right now, that blog systems who are overloading XMLRPC to provide many extra features, such as support for custom fields, don’t have a clear path to follow with regard to exposing those same features via AtomPub. I do think it’s a good idea to use a real-world example such as WordPress to test proposed extensions to AtomPub, but what comes out at the end should be a set of conventions that any blog system could adopt.
Getting more attention for tickets and issues is one of the reasons why I included a call for interested folks to come and participate. Having more people involved with these features will make it more likely that tickets like that will get responses.
Send me an email and let’s see if we can get some momentum going behind those tickets again.