ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Create a separate project for plugin directory (Task #136)

Added by Muntek Singh at 2011-02-03 03:58 pm. Updated at 2011-02-05 01:09 am.

Status:Open Start date:2011-02-03
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:ChiliProject - Organization
Target version:-
Remote issue URL:

Description

I'd like to propose the creation of a second project on chiliproject.org to house the plugin directory. If we choose to base it on the rubygems code, or turn it into a core plugin of some sort - either way the functionality and bug/feature/task/support/codebase will be separate from core chiliproject itself. I believe the needs of this work call for the creation of a separate project, rather than a category or some sort of minor distinction within this one.

Any objections or alternative proposals?

History

#1
Updated by Holger Just at 2011-02-03 04:00 pm

I support that. The plugin registry can be developed completely independently from ChiliProject core, by different developers. Also we would be able to use the repository integration, as the registry would live in a different repository.

#2
Updated by Eric Davis at 2011-02-04 01:34 am

So what would go into the project? (what modules)

#3
Updated by Holger Just at 2011-02-04 07:54 am

All the same we have on the main project. Maybe minus the forums to keep discussions in a common place.

Content in there should be strictly relevant to the registry. General frontend usage documentation should be (also) in the chiliproject project. Things like API documentation and advanced usage could/should live in the registry wiki.

#4
Updated by Yohann Monnier at 2011-02-04 09:56 am

I think we should think about something really larger that was is implemented in Redmine now.

I mean , it would be very cool to have a repository of plugins, hosted on github, with one click install.

ChiliProject should make a git clone of the plugin in the plugin repository by itself, do db:migrate plugins and ask for relaunch in order to finish installation.

By the way, it should also be considered to add "update plugin" button, based on git, that would do a git pull, a db migrate plugin and eventually ask for relaunch in order to finish installation.

#5
Updated by Muntek Singh at 2011-02-04 02:03 pm

Eric Davis wrote:

So what would go into the project? (what modules)

I'm unclear exactly what Holger is planning specifically, but the separate project would house a separate repository and issue tracker, as so-far the planned plugin directory is a completely independent product based on the rubygems plugin directory. There would be additional bits of code to integrate specific functionalities into chiliproject core, which would be here.

The only necessary modules I think will be issues, repository, and possibly wiki.

@Yohann: This is all future planned functionality for the directory and chiliproject.

#6
Updated by Eric Davis at 2011-02-05 01:02 am

So the "Plugin Registry" project would be for the development of the actual registry?

I read it as a project where any plugin developer could post their plugin. E.g a hosted "sourceforge" for third party developers.

#7
Updated by Eric Davis at 2011-02-05 01:04 am

Yohann Monnier wrote:

By the way, it should also be considered to add "update plugin" button, based on git, that would do a git pull, a db migrate plugin and eventually ask for relaunch in order to finish installation.

I've been thinking about this idea for at least 3 years now. I think we might be getting to a point where it could be an option ("browse list of plugins" > "click install" > git installs the plugin > ChiliProject restarts). Wordpress has a really nice system we can base ours on.

#8
Updated by Muntek Singh at 2011-02-05 01:09 am

That's correct, it would be for development of the actual directory, that will tie into chiliproject directly.We can discuss setting up a "sourceforge" for plugins separately, cause it's actual a solid idea. However this project would be for development of the chiliproject equivalent to:

http://wordpress.org/extend/plugins/

and based on this codebase: https://github.com/radiant/radiant-extension-registry

Also available in: Atom PDF