Central Plugin Directory
|Assignee:||Jean-Philippe Lang||% Done:|
create a central repository for all redmine plugins, as well as a way to collaborate with the project leads. I assume this wouldnt be too difficult to do, but would help immensely in tracking down relevant plugins for both use and possibly assisting others in development.
I think this could catapult the use of redmine as it would allow for a large base to get involved in periphery activities besides core redmine development.
#1 Updated by Vinod Singh over 8 years ago
IMHO it would be great to follow Apache style management of the plugins. Where all mature plugin are at one place and new/experimental plugins at some incubator location. That will help people know about the status of plugins and increase their comfort level in using them.
#2 Updated by Eric Davis over 8 years ago
- Category set to Plugin API
- Status changed from New to 7
- Assignee set to Eric Davis
- Priority changed from Normal to High
I agree with your reasoning but I don't think having a central repository would be good because it would require every plugin developer to use that system. And some developers are already established and might not want to move.
If there was a central directory of plugins, that would be useful. Ideally the directory would let a developer signup and enter some details about each of their plugins. This would include:
- Short description of the plugin
- Categories or tags to organize the plugins
- Compatibility - what versions of Redmine it works with
- Where the bug tracker is located
- Where the official code repository is located
- How to contact the author
- Maybe some news about updates
I've talked with Mischa and a few maintainers of some other open source Rails systems, and everyone has agreed it would be good to work together to build a common application that can serve as a directory of plugins. That way, each community could build on each other and share the development load. The Spree team has a really nice directory already released that I'm going to take a look at adapting for Redmine.
#4 Updated by Mischa The Evil over 8 years ago
As expected, I vote +1 for the directory solution proposed by Eric.
My past work on creating the current Redmine plugin list and Redmine theme list pages in the Redmine Wiki (which still is not properly announced by myself) was meant as a first step in a transitional-process working towards a state as proposed by Eric where we would use an application like the listed Tension application for this purpose.
Currently we have most of the basic info about the extensions complete and up-to-date (to a certain level) in one dedicated page, in a more (but hopefully better) standardized format and with a useful TOC. That will help a lot untill the transition has been actually done and it will help the actual migration to such system wehereas the basic info for most extensions in now available in a more structurized and maintained format and in is general more up-to-date.
I'm, as always, open to further comments/dicussions...
#9 Updated by Eric Davis about 8 years ago
Jean-Philippe Lang wrote:
I'm on it.
You going to try and use tension? Another option would be to use the code that powers gemcutter.org (http://github.com/qrush/gemcutter). It's gem based but I've been able to convert my plugins into gems which makes them easy to release. (example: http://gemcutter.org/gems/redmine_prefix_issue_with_author)
#11 Updated by Jean-Philippe Lang over 7 years ago
- Subject changed from Central Plugin Repository to Central Plugin Directory
- Category changed from Plugin API to Website (redmine.org)
- Status changed from 7 to Closed
- Resolution set to Fixed
The plugins directory is now available at http://www.redmine.org/plugins.