Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 UTC on 18 March 2024, to get $100 off your ticket.
Since project* has been designed with use on d.o in mind, there are sometimes features that don't make a lot of sense when used on smaller, less complicated sites. Since everyone has access to d.o, it would be good to give a detailed explanation of how project* on d.o is configured to work as it does. In this description it might be helpful to point out why certain choices of configuration are right for d.o but may be wrong for a smaller site.
There is already a d.o testing install profile (http://drupal.org/project/drupalorg_testing) and a write up of this might also be helpful.
Comments
Comment #1
aclight CreditAttribution: aclight commentedI'm splitting this up into two separate issues. Let's keep the task of creating documentation of the Drupal.org testing profile in this issue (and move to the drupalorg_testing queue).
For discussion of writing documentation about why things on d.o are set up as they are, see this issue: http://drupal.org/node/199377
For a first attempt at documenting the d.o testing profile, see the handbook page at: http://drupal.org/node/199369
We might want to put this under a different parent, but I didn't see anything that made much more sense.
Also, we should probably point the documentation link of the d.o testing profile project to this handbook page. I'll take care of that unless anyone has any objections.
Comment #2
dwwThat's a great start, thanks! Seems like a reasonable parent item to me, and yes, please point the profile's doc link there.
Additionally, it'd be great to have a page that describes what steps the d.o testing profile takes to configure those modules and generate content.
Comment #3
hunmonk CreditAttribution: hunmonk commented