[development] installation profiles on drupal.org
Frando (Franz Heinzmann)
frando at xcite-online.de
Sat Feb 17 12:03:16 UTC 2007
Larry Garfield schrieb:
> On Friday 16 February 2007 6:57 pm, Frando (Franz Heinzmann) wrote:
>> So there is some kind of consesus that, generally, installation profiles
>> should be hosted on drupal.org. And there seem to be some voices in
>> favor of improving the cvs packaging script to be capable of packaging
>> the contrib modules that a distribution needs together with the install
>> profile and maybe drupal core, in which I also am in favor of. See 
>> for details.
>> However, I agree with Boris Mann here:
>> If there are some install profiles, the hosting requirements on
>> drupal.org should be created. But install profiles should come first.
> Until the chicken-and-egg issue is taken care of (why host profiles until
> there are enough to be worth it), what about simply having a page on d.o
> somewhere (probably in the handbook, linked from /handbooks so it's easy to
> find) that points to provided profiles that are hosted off-site? That shows
> that they're actually being built and gives a common place to find/publicize
> new profiles. Then, when/if they reach some critical threshold (defined
> as "when Dries and/or Derek decide it's worth it"), CVS can be enhanced as
I'd just add a top-level cvs directory right now, and have the profiles
hosted there. No packages would be built for now, and they wouldn't be
browseable via project.module, but they could be developed collaborative
in drupal cvs.
Of course you could (should) then still have a handbook page explaing
the current situation.
But I think adding a top level cvs dir is a simple-enough step that
could foster collaboration quite a bit here (instead of 10 people
developing the same things at different places because there is no
single spot where collaboration could/should happen).
Everything else (adding project.module support, enhancing the package
script) can come later then.
More information about the development