I like this idea, but it's really hard for me to do using only core modules. I don't think I've done a core-only site in three years. ;-) I suspect a lot of other people will have the same problem - certainly anyone of the skill level required to be able to actually write and maintain an install profile. Daniel F. Kudwien wrote:
Quoting Dries Buytaert <dries.buytaert@gmail.com>:
On 13 Nov 2007, at 20:06, Derek Wright wrote:
On Nov 13, 2007, at 12:25 AM, Dries Buytaert wrote:
I don't mind having two or three profiles ship with Drupal core. To clarify, you mean some install profiles that ship with core *which only include core modules*, right? Yes.
-- Dries Buytaert :: http://www.buytaert.net/
If we ship Drupal 6 with additional install profiles, we should also have a designated maintainer for each one of them. Each profile maintainer should be primarily using "his" profile for own sites and she/he should have deep insight into the market the profile deals with.
By writing this, I actually think that development speed in core could be too slow for having great install profiles. See: any improvements to a blogging profile would have to wait for D7.
Conclusion: I would rather suggest to write detailed documentation about developing install profiles and support Derek in realizing his efforts of pre-packaged install profiles, instead of shipping Drupal with poor "example profiles". Users evaluating Drupal for a blog would not know of contributed install profiles. So they would test that blogging profile in core and probably head over to another blog-ready system, because modules in Drupal core do not provide as much features as other blogging systems.
sun
-- Sean Robertson Web Developer NGP Software, Inc. seanr@ngpsoftware.com (202) 686-9330 http://www.ngpsoftware.com