Sorry to come late to this thread . . . On Fri, 2009-11-20 at 22:40 -0500, Robert Fischer wrote: > I'm starting to stash plugins over on GitHub at my gradle-plugins project: > http://github.com/RobertFischer/gradle-plugins > > README for more info: > http://github.com/RobertFischer/gradle-plugins/blob/master/README.md > > ~~ Robert.
This raises a number of issues:
1. There needs to be a central index of plugins people are offering so
as to create a community.
2. There needs to be a process for plugins to migrate from the
community into a centrally maintained resource.
3. There needs to be two levels of centrally maintained plugin
resource:
a. Distributed as part of the core.
b. Centrally held and maintained but not core.
4. There needs to be a process for plugins to migrate from 3b to 3a.
5. There needs to be a process for plugins to migrate from 3a to 3b.
6. There needs to be a process for plugins to migrate out of the
centrally maintained resource back to being community held.
For me the Exec plugin should be in the 3a core.
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
