http://www.pli-images.org/forum/viewthread.php?forum_id=48&thread_id=19304&pid=215225#post_215225
I think it should be soon a necessity to have a common repository for system and major extensions plugins strictly open sources because of licenses that could limited all the official plugins to be used only on dmm hardware.
There are many teams that could contribute like Pli, Black Hole, Vti, Vix, Sif and so on.
All the teams could have a section in their boards about the project so the plugins should be tested by many users on all the boxes.
I think the man that have the skill and maturity to manage this kind of project are you: pieterg.
Here is a suggestion:
To start a Common Public E2 Plugin repository, the E2 OpenSource Community could start a GitHub account:
https://github.com/for example with a name like: "E2 OpenPlugins"
Git is an extremely fast, efficient, distributed version control system ideal for the collaborative development of software.
GitHub is the best way to collaborate with others. Fork, send pull requests and manage all your public and private git repositories.
Free public repositories, collaborator management, issue tracking, wikis, downloads, code review, graphs and much more…
Have a look at an example here:
https://github.com/Glimpse/GlimpseUsers can make there comments at the sourcode, also post bugs...
Or create a fork themselves, do a pullrequest if they have a functional patch instead of mailing them or posting it at a forum...
With the free public GitHub repositories you will also get an integrated issue tracker and also a wiki!
Also good to have: repository access over https, no issues anymore with firewalls in combination with ssh or git's own protocol...
How to use this together with several external E2 developers or E2 hobby teams?Every developer has his own github repository for his development of his plugin(s) or so called package(s), where he uses the git flow system.
A good idea is to use a centrall plugin repository, in this repository a fork is located of the master branches of the different repositories.
When there is a new release (which is a merge from a release branch to master, including a tag) it will be set into this fork.
The centrall repository set contains always the latest release of all E2 plugins.
Who controlls these repositories?The full controll is done by the individual repository developer.
Other developers will fork his repository, and send him a pull request for there updates.
When the main repository developer has a new release ready, he will do an update of his master.
Other external developers or hobby teams don't have more work using this method then to keep there masters in sync, which can be scripted.
