[wp-hackers] Atom Publishing Protocol work - Ticket 4191

[Matt Patenaude]

OK, good :P Thanks!

-Matt

On May 24, 2007, at 9:15 PM, Elias Torres wrote:

> APP, AtomPP, Atom API, Atom Publishing Protocol... all same thing.
>
> -Elias
>
> Matt Patenaude wrote:
>> OK, time for the n00bish question :P
>>
>> Atom Publishing Protocol vs. Atom API-- same thing, different things,
>> AtomPP = latest edition of Atom API?
>>
>> Thanks!
>>
>> -Matt
>>
>> On May 24, 2007, at 8:01 PM, Elias Torres wrote:
>>
>>> Thanks for the pointers. I'll definitely look at it in case there's
>>> anything I can use.
>>>
>>> -Elias
>>>
>>> On 5/24/07, Kevin Newman <CaptainN at unfocus.com> wrote:
>>>> Hi Elias,
>>>>
>>>> I wrote a validating atom mod a while back for WordPress 2.1.x (I
>>>> recently updated it for 2.2).
>>>>
>>>> If there is anything useful in it, please feel to use it:
>>>> http://www.adcstudio.com/blog/wp-includes/feed-atom.php.txt
>>>>
>>>> The validating feed:
>>>> http://www.adcstudio.com/blog/feed/atom/
>>>> http://feedvalidator.org/check.cgi?url=http%3A%2F% 
>>>> 2Fwww.adcstudio.com%2Fblog%2Ffeed%2Fatom%2F
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> Kevin N.
>>>>
>>>>
>>>> Elias Torres wrote:
>>>>> Hi hackers,
>>>>>
>>>>> I might have introduced myself before, but I'll do it quickly  
>>>>> again. I
>>>>> work at IBM for an innovations team in the CIO office (bleech),
>>>> anyways,
>>>>> I like to work in open source and standards. I use WordPress
>>>> personally
>>>>> and also participate in the Atom APP workging group at the IETF. I
>>>> have
>>>>> been working on the WordPress AtomPP implementation for sometime
>>>> now and
>>>>> that's what we have included in WordPress 2.2. Before today, the
>>>>> workflow was that I'd submit a patch and wait for Dougal to verify
>>>>> before it was committed. The turn around time and other things  
>>>>> make
>>>> this
>>>>>  really hard to make progress and leads to very large patches.
>>>>>
>>>>> After chatting with Matt, he suggested I write to the list for
>>>> everyone
>>>>> to be involved in the review process as well as me sending smaller
>>>> (more
>>>>> understandable) patches. I had a huge patch that did some
>>>> unconventional
>>>>> conversion from tabs to spaces making it very unreadable. I  
>>>>> fixed it,
>>>>> but it's still a bit larger then usual. I would like people to
>>>> review it
>>>>> and suggest we commit it. From now, I'll stay more closely aligned
>>>> with
>>>>> the releases and make sure we have a robust APP implementation as
>>>> the WG
>>>>> is hopefully???? near completion. We are I'd say 75% there and I'm
>>>>> willing to put in the time, but I need to know the commitment  
>>>>> of the
>>>>> group to quickly review small patches and commit without depending
>>>> on a
>>>>> single third-person to review.
>>>>>
>>>>> Behold the patch -> http://trac.wordpress.org/ticket/4191
>>>>>
>>>>> Looking forward to working with the community here at large.
>>>>>
>>>>> -Elias
>>>>> _______________________________________________
>>>>> wp-hackers mailing list
>>>>> wp-hackers at lists.automattic.com
>>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> wp-hackers mailing list
>>>> wp-hackers at lists.automattic.com
>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>>
>>> _______________________________________________
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers