What would you like us to Ask The Agencies at March's OxDUG?

Events happening in the community are now at Drupal community events on www.drupal.org.
jp.stacey's picture

On Wednesday 4 March OxDUG will host an informal chat with three of Oxfordshire's Drupal agencies, where we'll discuss the basics of process management and deploying both changes and entirely new websites.

What would you like us to ask them?

We'll take submissions on the night too, but if you've got any specific questions about what constitutes good practice in shipping Drupal work, then do post them either here as a comment, or on the March OxDUG meetup page.

Comments

Join in, everyone!

jp.stacey's picture

I'm going to ask a few straightforward questions that will hopefully get us started, but please do join in!

  • How do you (technically speaking i.e. "devops") move requested and then approved changes from development to live?
  • What process do you go through with clients to ensure they're ready to do so i.e. how do you get approval, what do you or they test etc?
  • How do you version code and what's your backup strategy?

Quick one

retrodans's picture

Wanted to help keep this list going, so had one:
* How do you reliably ensure the code that goes live is the same that that has tested (possible a week or 2 earlier) and that no regressions are interested WHILST keeping costs down, and not wasting the clients/POs time with multiple tests

Security

jp.stacey's picture

Thanks, Dan. Regression testing is definitely useful to see across more than one agency. Another couple of questions, security-oriented but also testing-oriented:

  • How do you keep abreast of security issues? What sources do you use, and what's your policy for frequency of checking them?
  • What's your broader security policy; what's your process for testing updates; and how do you prioritize updates so that the most serious (e.g. Drupalgeddon) can bypass any slower processes?

Oxford

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: