The issue has come up in IRC about how to manage the bluecheese theme in regard to:

  • Where will head/trunk for bluecheese exist. It has resided until now in https://svn.drupal.org/drupal/themes/bluecheese/trunk (apparently this matches the current precedent set by the bluebeach theme)
  • Where ever head/trunk exists, how will it be merged/included across D.O. sites? It could be merged from, included as an svn:external, and possibly other options.
  • Who, if anyone is the maintainer of bluecheese? At some point soon we will be facing commit/merge issues...

If the appropriate stakeholders could help us arrive at an actionable plan soon it would be great. We would like to implement whatever course we take as soon as possible on the redesign sites.

Comments

calebgilbert’s picture

calebgilbert commented

#1, I think it makes sense to keep things in https://svn.drupal.org/drupal/themes/bluecheese/trunk

#2 - doesn't make a lot of difference to me. Merging from trunk to the D.O. sites seems like it might be in keeping with how other things work, but I'm up for whatever.

#3 - For someone else than me to decide

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

This is easy enough stuff - I think the key is getting a maintainer.

My natural inclination would be for using the redesign branch's sites/all/themes/bluecheese as "the real thing". It would then be really obvious and easy to figure out what was the "real thing". No separate checkout or merging would be required. The maintainer could apply patches to it.

drumm’s picture

drumm
he/him
Location NY, US
commented

1. Keep it as-is, but be more-watchful for errant commits elsewhere.

The propblem with using the redesign branch's sites/all/themes/bluecheese, is that we need to merge changes out to production and staging of at least 4 websites.

2. svnmerge.py is documented at https://infrastructure.drupal.org/node/54, which is hard to get access to, find, and is long-winded. A very concise version should be on groups.drupal.org.
3. Yes, someone to step up and review patches and other maintainer tasks is needed.

Amazon’s picture

Amazon commented

I've asked Todd to take a look at the need for a maintainer. We are going to discuss this in our project management meeting on Thursday.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Active » Fixed

Calling this fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Component: staging.drupal.org » Other