Hi!

On Thu, Apr 9, 2009 at 16:32, Bernd Fondermann <[email protected]> wrote:
> would you mind to give us a rough draft timeline of when you would like to
> implement what part of the XEP, so we get a better idea of your approach?
> This list should contain no more than a dozen or so bullet points.

I'll concentrate on the things between now and Google's suggested
"pencils down" date (2009-08-10).

As stated earlier on the list my task until the student notification
(2009-04-20) would be to improve the test-coverage of Vysper. This
should give me a good overview of the project and of its features.

Until 2009-05-23 my plan would be to continue to explore the current
Vysper capabilities and shortcomings as well as to read the XEP-060 in
detail.
The pubsub specification is quite large (170 printed pages), so I
think a month is a good time frame. Maybe I can start coding earlier,
though.

In the following "Node" stands for "A virtual location to which
information can be published and from which event notifications and/or
payloads can be received (in other pubsub systems, this may be
labelled a "topic")."

Between 2009-05-23 and 2009-07-07 I plan to implement the following
parts of the specification (including the chapter within the XEP-060
spec):
 - Publish an Item to a Node (7.1)
 - Subscribe to a Node (6.1)
 - Affiliation to a Node (4.1)
 - Discover Node Information (5.3)
These are the minimum requirements a XEP-060 implementation must
fulfill to be conforming to the standard (see Chapter 3).

Recommended features (creating and configuring a node for example) may
also fit within this time frame. Chapter 10 of the XEP-060 gives an
overview of the required, recommended and optional features.

After the midterm evaluations I think it is best to concentrate on
completing the extension with recommended features. And to integrate
the new features cleanly into the Vysper server.

In the end (around 2009-08-10) I'd like to have the required and
recommended features of XEP-060 implemented and integrated into the
Vysper server.

The main focus should be to deliver a fully working, but possibly not
full featured, module for Vysper rather than a complete but bug ridden
one.

What do you think? Is it too much, too less or just right?

Cheers,
Michael

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to