Interesting idea but isn't it simpler to just use SVN? If this is only going to be used for designs to easily submit themes it's easier to remove this plugin from Trac and just code a little script to allow users to upload a zip file on the web, enter a theme name, then it could be added to the svn through a simple php, python, or perl script. If you want I can whip up some code to do this.
However, I think it'd be nicer to attempt to create our own impression of the "Wordpress Extend" site that directly relates to our svn. It could easily allow designs or plugin authors to update their code and then allow other users to get a nice interface to download these extensions and possible preview themes. Would also give us, the habari community, a better feel for our demand of themes and plugins. If we tracked searches and results we'd be able to tell what plugins are missing that people want and what types of themes people like. While all the time keeping the SVN updated for us. We could also related this to the Trac database and have designs and plugin authors accounts linked between this and Trac to keep updates as real as possible. (This may seem hard but I do not believe it would be.) (I liked the Mac files comment, I feel the same way.) On Wed, Jan 7, 2009 at 4:34 PM, ringmaster <[email protected]> wrote: > > It would be nice to have a web UI that would convert a packaged and > uploaded zip file into a subversion commit. > > The interface would include fields for Trac username/password, name of > the project, whether it's a plugin or theme, and an upload field. A > notice that only ASL-compatible projects should be uploaded should > appear on the form. > > Uploaded files would be searched for appropriate metadata before > addition. Also, those stupid Mac files would be removed from the > archive, if present. > > After upload, the SVN URL would be displayed. > > A second phase would allow a user to upload a zip file to make changes > to an existing project. The only differences would be that you would > select a project to update. The uploaded files may be validated > against the existing ones to prevent tampering, but you'd still need a > Trac login to update a plugin this way. > > A third (or earlier) phase would connect this all to the Habari plugin/ > theme directory, and let the user submit or update a plugin/theme > description via the UI. > > This would make a great Trac plugin, but I'm just interested in it for > what we have now. > > Owen > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
