Re: contributed plugins
Steven Armstrong <[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.devel |
|---|---|
| Message-ID | <[email protected]> |
will guaraldi wrote: > Someone else commented on a plugin in the registry that's marked as coming > with PyBlosxom. > > I don't really know what to do in regards to contributed plugins. I > really want it to be a separate project and I don't really want to deal > with it. Anyone want to pick up maintainence of contributed plugins? > > I'm thinking the first thing we could do is spin off a mailing list for > it. Something like pyblosxom-contrib or pyblosxom-plugins. I don't > really care which. Then that group of folks can go off and do their thing > with the contributed plugins including (if they want to) restructuring the > plugin registry and such. > > Anyone want to pick this up? If not, then I think what I'm going to do is > write a script that builds a contributed plugins pack and just release it > every now and then. And by "every now and then", I really mean "when I > get around to it". > > /will > I'll just quote myself here :) I have an idea on how to manage this automatically: - hack the plugin registry to allow file uploads. - when a user registers/uploads a plugin he gets a unique key (password) by mail. - using email and key he can update his plugin later on. - allow download of a single plugin and a tarball containing all of them. - when a plugin is registered/updated generate an email to pyblosxom-users informing about the new version and the changes made. Pros: - one single place to go for plugins - registered plugins are allwais available. no 404's when trying to download a plugin cause someone forgot to update a url. - everybody can maintain his own plugins. no extra work for the dev's. - users get informed about changes/updates. Cons: - someone has to write the code for this. I think this would be a good solution and am willing to code it if nobody else feels like it. Altough it'll take a few weeks till I find time as I have a new project starting this week. A few questions regarding the infrastructure at sourceforge: - cronjobs? - shell access? for running scripts and such. - access to a mailserver for generating notification emails? Maybe we could post this and any other available ideas to pyblosxom-users and see what 'the clients' think/want? cheers Steven ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click