On Fri, Sep 5, 2008 at 7:56 AM, drzax <[EMAIL PROTECTED]> wrote: > > Habari is easily flexible enough to do this, but my gut feeling is > still that this probably isn't the right way to go. Apart from a > little bit of infancy still to be grown out of (ACL for example, which > I know is taking leaps and bounds) this is the only area that I feel > WP still out does Habari. wp.o/extend is something I really like, and > it was a long time coming. If we can get Habari's version of that > right it will be a huge boost for the community.
We could do it in a similar way, in that you add a plugin.xml file to you plugin, and the plugin explorer thing on hp.o would simply read that file to gather all necessary info. I would actually prefer this way over the the other, and it would still allow us to maintain the beacon data if all proper info is in the xml file. Using an xml file this way would however require that the plugin be "hosted" on the svn repo. You could still link to an external page with more info. > Maybe I'm just not seeing the potential, but the system you've > described doesn't sound awesome to me. It sounds unnecessarily > complicated. Yes, it seems rather complex, that is why I hesitate to go any further with the current method. Having to release then update a post is rather annoying. > Having said that, using Habari as the system for this might open up > one other possibility which I think would be awesome. How about having > some kind of aggregation system so that plugin authors could post > plugins on their own blogs and have them somehow automatically show up > and be downloadable on hp.o. Maybe that's already been considered. As > a potential plugin author I'd love that scenario. I like that idea, however this makes it extremely hard to maintain the update beacons, and hard to verify the download. I think a combination of the current way (creating a post on hpo) and using an xml file in the plugin to obtain the additional information, would be the best way. Then you would only make a post with name, description, and tags, and point it to the svn repo in such a way that the post->slug = svn directory. All additional information and updates would then happen automatically. -- Matt Read http://mattread.com --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
