Notes from our 2009-07-07 call

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
You are viewing a wiki page. You are welcome to join the group and then edit it. Be bold!

Infrastructure: Development/testing instances

(Discussion in Infrastructure Requirements)

We are still hamstrung by the lack of dev/testing instances.

What we need from dev/testing instances

  • A test instance that the public can view and click around on. This will help us build interest and momentum.
  • Several dev instances (at least 5) split between developers and themers.
    • Nice to have: Script to roll out new instances on the fly
  • Sanitized DB for remote and local dev instances. Should be easily downloadable for those who want to set up local dev instances.
    • User 1's username and password should be pre-reset.
    • Nice to have: Script to clone a canonical, sanitized DB into remote dev instances as needed.
  • Apache Solr needs to be set up.

Next steps

  • Contact Damien to see if he can help plan and delegate infrastructure tasks.
  • Find additional infrastructure team members to help set up dev/testing instances.
  • Talk to David Strauss about Capistrano to manage scripts that automate various tasks (like dev instance rollouts and DB cloning).
  • Settle on a file-storing service for theme assets and move assets out of SVN. We are currently leaning towards Wuala.

Create a guide to getting started

We need a comprehensive guide to getting started. There are a number of posts in this group that contain elements of this guide; we need to compile and expand on them.

What a "getting started" guide needs

  • How to work with a dev instance (both local and remote)
    • Using SVN
  • How to set up a local dev instance
    • Using MAMP or other local dev environments
    • Checking out the drupal.org redesign branch locally
    • Setting up clean install
    • Importing d.o database
    • where to download database
    • importing database
  • How to keep up with the project: notifications, RSS, issue queue, etc
  • Asset management
  • How to find things to do
    • prototype

Communication with volunteers

  • Send a link to the "getting started" guide.
  • Explain the situation with the dev/testing instances. Emphasize that work can still be completed without a remote dev instance.
  • Enumerate what our plans will be once this is completed.

Communication with volunteers who already have SVN access

  • Set up times for local dev "installfests."
    • Find Linux and Mac experts willing to troubleshoot.
    • Use Doodle to arrange convenient times.
  • Gauge interest in creating and distributing Linux virtual machines.

Communication with designers

  • Send a designer-only email that omits all the technical details.
  • This email should contain only information on MB's prototypes, remaining design tasks, and links to the assets file-storing service.

Other remaining tasks

  • Kathleen is working on digesting all literature and issues related to the redesign. She will then conduct a site audit to determine what remains to be done.
  • Ensure new drupal.org functionality has been ported to the drupal.org redesign branch.
    • Establish a procedure for porting changes between branches.