Finally Atom

Atom Community Meeting

Wednesday, 2 June 2004, Menlo Park or Santa Clara (TBD)

This meeting is open to everybody who wants to help with the topics listed on the agenda. However, in order to attend, one must RSVP by listing your name below by Wednesday, 26 May, 2004

Agenda:
1. Expectations of process & progress going forward (possibly/probably in the IETF)
2. Editorial work to prepare Internet Drafts
3. Discussion of one outstanding tech issue, namely multi-part non-textual postings
4. Gather additional requirements for syntax and/or protocol.

AtomMeeting - Atom Wiki

IetfCharter

Atom has a draft Ietf Charter, with Sam Ruby and Tim Bray as chairs. The only date fixed on the agenda is Aug 04 : Meet at the 60th IETF to discuss current drafts.

CategoryProposals

A list on the Wiki CategoryProposals page has been quietly growing, each item containing specific proposals for changes to the specs.
So far we have :

• PaceEntryDates
• PaceLinkConstruct
• PaceLinkRelMechanism
• PaceNoInfoSet
• PacePutDelete
• PaceXmlBaseEverywhere
• PaceXmlBaseId

What does "Pace..." mean? Answers on a postcard please...

Draft Atom IETF charter

Sam Ruby has posted a Draft Atom IETF charter to the Wiki:

I've presumptuously placed my name as (one of the) chairs of this group, but there really shouldn't be any surprises in this draft.

In March, I expect the names of the IETF director(s) and advisors to be filled in, each bullet in the description to be replaced by a paragraph, and dates to be determine in the goals and milestones section.

Atom going to the IETF

Announced in Sam's ETCon slides:

• A draft charter will be prepared in time to be informally discussed at the IETF meeting is Seoul, Korea on the week of 29 February to 5 March
• Hopefully, the Working Group itself will be approved in March/li>
• Most of the work will be done on mailing lists/li>
• Ideally, a face to face meeting of the Working Group will be scheduled to coincide with the August 1-6 meeting of the IETF in San Diego/li>

!Echo Wiki, lessons learned

Sam Ruby's slides from ETCon, discusses the pros and cons of using a mailing list, Wiki and blogs for a project like Atom.

Issue Tracking

To expidite Atom 1.0, Ken MacLeod has stepped forward to start tracking issues.

"My role is to list them, track the main points (particularly so that less vocal, yet clear arguments are surfaced), and report on them."..."...To be clear: my role is *not* to define the issues, document solutions, or prepare spec prose. Only to track."

Ken did this job for RSS 1.0, the issue list there gives a picture of the approach.

Official : it's now called Atom!!

Following the deadline of 30th September 2003, with 59 votes, we got beyond that impasse.

NameFinalVote

Gardening chat (today)

WikiGardening chat, Tuesday, August 12, 2003 15:30Z (local timezones) on #echo at irc.freenode.net for 90 minutes, then as participation permits.

Gardening PS.

Wiki discussion of the major refactorings (of the Wiki) has been opened at ThreadModeAndRefactorOk.