Background

Now that we're nearly down to single figures for beta-blockers a few of us have started organizing around a D8CX initiative similar to that run during the Drupal 6->7 update. Talk on irc over a month-or-so led to a formal kick-off meeting to set down some goals and get some action items.

What is D8CX I hear you say

Back in the Drupal 6 -> Drupal 7 cycle the D7CX initiative promoted/assisted contrib modules porting from Drupal 6 to 7.
The CX stands for 'Contrib experience', ie its about ensuring the best contrib-module experience for building sites with Drupal 8.

Kick off meeting
Attendance

Present at the meeting were Nick Waring (nickwaring89) (PreviousNext), Dave Reid (davereid) (Lullabot), Tim Plunkett (tim.plunkett) (Acquia) and myself (larowlan) (PreviousNext). Apologies were received from Angela Byron (webchick) (Acquia), Michael Schmid (schnitzel) (Amazee Labs) and Kim Pepper (kim.pepper) (PreviousNext). Although Kim did drop in for the last few minutes.

Goals

Introductions aside we turned our attention to the group's goals which were agreed as follows:

• Promoting the status of Drupal 8 ports of key contrib modules
• Establishing a curated list of modules to report on
• Facilitating communication to the wider community of key contrib module maintainers' needs (eg testing, funding, sprinters)
• Providing a centralized location/point of call for those willing to help/sponsor to make first contact

Tools/Process

We decided that our primary objective should be to reboot a site similar to drupalcontribstatus.com (via wayback machine). We discussed re-purposing d8cx.org but @webchick kindly offered the drupalupgrade.info domain.

Screenshot of drupalcontribstatus.com from Internet Wayback Machine

Proposed features

We settled on the following feature-set for the site:

• Dashboard on home page showing status/% of modules with links to more detail
• Call to action 'get involved'.
• Possible 'pledge/chip-in/sponsor' links where module maintainers identify a need?
• For each selected module
  • Status (none/dev/alpha/beta/rc/full)
  • Percent complete (manually set)
  • Status description (text)
  • Upcoming sprints
  • Links to crowd-sourcing campaign if applicable
  • How to help blurb (priority tasks)?
  • Maintainer details/bio
  • Port team/sponsor details/acknowledgements/thanks
  • Latest news/updates
• News feed (of updates/progress) for syndication (twitter/rss)

In addition we planned to have regular (fortnightly) meetings to discuss progress.

Promotion

We discussed proposed ways to promote the work being done and our status as follows:

• groups.drupal.org/core post to announce initiative and goals with details on how to get involved (you're reading it - spooky)
• Regular blog article on port status/milestones reached (eg module x reached beta) - see news feed feature above
• Regular podcast/lightning talk? (hangouts on air) Regular catch-up with selected maintainer to flag where they're at and where audience can help?
• @schnitzel has proposed a session on D8 Contrib Module status for a session at DC Amsterdam

Education

One of the key items identified is that Drupal 8 might mean some significant refactoring of modules during porting. To this end a Contrib mentoring session similar to core mentoring was proposed, essentially contrib office hours where maintainers/those helping with ports can come to irc and ask questions like 'how should I do this?' 'what happened to y?' 'what's the best way to architect x?'. This is informally happening in #drupal-contribute already but a dedicated Q/A session at regular timeslot(s) via irc made sense. The caveat here would be that the knowledge captured/shared during these sessions be distilled into handbook/documentation pages and/or the examples project. Yes, you must take a blood oath to do so. Seriously.

Action items

Meeting action items were as follows:

• Decide on a domain and organize hosting (@timplunkett).
• Start building the site functionality (@larowlan)
• @nickwaring89 kindly volunteered to co-ordinate site updates/collaborate with maintainers to gauge their needs/status
• Post minutes on g.d.o/core (@larowlan)
• Start building a list of candidate modules to report on(@davereid, @kim.pepper)
• Assess state of upgrade status for support querying 8.x status (@larowlan, @webchick)
• Reach out to other large Drupal shops/service providers to seek their involvement in the initiative (@timplunkett, @kim.pepper)
• Reach out to module maintainers of modules identified(@nickwaring89)

Next meeting

Next meeting 10pm UTC Wednesday 9th of July. This is a rough time-slot for European community members but falls around 8am for Australia and at the end of the working-day for the US. We aim to move to a rolling schedule that would allow the three time-zones of participants (Europe, US, Australia) to be able to reasonably attend two of every three meetings.

Want to get involved?

Get in touch with nickwaring89 to register your interest in getting involved.

AttachmentSize Screenshot 2014-06-27 14.23.17.png88.72 KB