On Sun, Jul 26, 2009 at 18:51, Michael Jakl<[email protected]> wrote: > Hi! > > I'm currently plotting the features and tasks for the coming weeks. I've > summarized the completed, planned and "not yet planned" features on our > Wiki[1]. > > My current plan would be to > 1) Implement "affiliations" > 2) Implement the "authorize" access-model > 3) Make the features configurable > 4) Plan further > > The affiliations are described in chapter 4.1[2], and allow a more fine > grained > access control (as opposed to the current "all or nothing"). I think this step > requires the most work. > > The "authorize" access-model allows a node-owner to approve subscription > requests (currently everyone can subscribe). There are more access-models > described in chapter 4.5[3] which I don't plan to implement in the near > future. > > The third step would be to make the new features accessible to the outside. > This is done via the configure-node feature described in chapter 8.2[4]. > > I think this are the most important features to make the extension useful. > > WDYT? > Michael > > 1: > http://cwiki.apache.org/confluence/display/VYSPER/XEP-0060+Publish-Subscribe > 2: http://xmpp.org/extensions/tmp/xep-0060-1.13.html#affiliations > 3: http://xmpp.org/extensions/tmp/xep-0060-1.13.html#accessmodels > 4: http://xmpp.org/extensions/tmp/xep-0060-1.13.html#owner-configure
+1, sounds good. Bernd
