[geeklog-devel] Proposal - plugin repository

Matt West matt.danger.west at gmail.com
Sun Mar 29 14:47:31 EDT 2009

Hi Pawel, I'm glad to see your interest in the plugin repository  
project. My name is Matt West and I'm the mentor for this project. I  
read over your proposal and have a few comments.

> 1. Plugin Repository – this plugin contains the functionality of  
> providing plugins for download. There should be a possibility of  
> adding some kind of authorization. So the access to the. repository  
> can be public or limited to a group of users. Of course all of these  
> features are going to be configurable.

Our outline[1] of an "open" vs. "closed" repository was more with the  
idea of whether uploaded plugins needed to be approved before  
appearing in the repository. You're suggesting that access to the  
repository itself could be configured to be public or private. This is  
something I hadn't thought of, and am not sure that it's necessary.  
Could you give an example of why a site or developer may want to keep  
their repository private?

> Plugin Repository is just a normal plugin, so each user of Geeklog  
> can create his own plugin repository. Some other features of that  
> module: automatic validation of added plugin (if the structure of  
> plugin is correct), possibility to download the plugin in  
> traditional way (via browser), feeds information about changes of  
> plugins in repository. User can also upload his plugin(or modify his  
> plugins), which after approving become available for to download  
> other users.

Here you're kind of just rewording what we've outlined in the project  
summary[1]. This is fine but I would like to see some details on how  
you would address each of the topics.

> 2. Plugin admin panel – Plugin panel should be modified. So it will  
> have functionality of adding new repository (and maintain already  
> added repositories. I think it should be so). There will be a list  
> of plugins from added repositories. Admin will choose interesting  
> plugin and will instal it by one click. There is also a news  
> perspective, which keeps admin up-to-date about plugins in  
> repositories.

Again, I would like to see how you would develop some of these  
features and how they would function. How will the "one click install"  
work? What types of checks will need to be performed before installing  
the plugin? What is the "news perspective" and how will it work?

So, I would like you to go back through each point you've mentioned  
and elaborate in detail. Then submit a revised proposal and we can go  
from there. If you have any questions feel free to contact me on IRC  
or you can email me directly or on this list.


[1] <http://wiki.geeklog.net/index.php/SoC_plugin_repository>

More information about the geeklog-devel mailing list