[wp-hackers] Inline documentation

[Alex King]

I think the conversation should change to: What is the best way to  
create and maintain inline documentation if it won't be checked into  
core.

A number of features currently in/or being added to WP were initially  
rejected when first proposed. This is a good idea, and it shouldn't  
be stopped cold because Matt doesn't like it right off the bat.

This is still an OS project - if the community is willing to support  
and create this documentation, it should be included. I'd bet a  
nickel that Matt might be willing to reconsider if presented with a  
full set of documentation. Of course, the flip side to this is that  
if the documentation isn't completed, it's easy for it to be dismissed.

My recommendation is that the documentation effort be revived,  
perhaps on a local branch that someone is willing to maintain, and  
that the finished documentation be presented to WP for consideration  
when it is complete.

Cheers,
--Alex King

Personal             Business               FeedLounge
http://alexking.org  http://kingdesign.net  http://feedlounge.com




On Mar 29, 2006, at 7:16 PM, Kirk Steffensen wrote:

> Yeah.  It made sense and would have helped plugin writers, so it  
> was put to
> a quick death.
>
> -----Original Message-----
> From: wp-hackers-bounces at lists.automattic.com
> [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of Chris  
> Davis
> Sent: Wednesday, March 29, 2006 8:37 PM
> To: wp-hackers at lists.automattic.com
> Subject: Re: [wp-hackers] Inline documentation
>
> It was killed, it did not die off.