Next Doc team meeting: Aug 6

Peter Matulis peter.matulis at canonical.com
Wed Jul 30 01:23:46 UTC 2014


On 07/29/2014 08:12 PM, Doug Smythies wrote:
> 
> On 2104.07.29 11:27 Peter Matulis wrote:

>> It depends on whether we want to be in the web design *and*
>> documentation business or just the documentation business.  You are
>> evidently comfortable in both but as a *team* we need to decide what we
>> want.
> 
> Sorry. I am not comfortable with the theme design at all.
> However, and even though it takes a great many hours per issue,
> I do look into investigating and fixing issues with the theme.
> Often, but not always, these end up being upstream issues with
> yelp and yelp-tools.

I don't know the issues you refer to but wouldn't updating the other
ubuntu.com sites encounter the very same ones?  Isn't this another
reason for allowing for a more centralized mechanism?

>>  My opinion is that if Canonical is updating other ubuntu.com
>> sites due to, say, a theme change, it makes sense for them to do it on
>> all sites in one go.
> 
> Yes, and that stuff is in "our" master bzr branches.

Yep.  And this means Canonical will be performing some community work.

>> Having to depend on one person to do it for
>> help.ubuntu.com is not great.  And indeed it does free us up.  It frees
>> us up from having to do that.  :)
> 
> The point I was trying to make further above was that I do not want
> to give up the ability to push the master help.ubuntu.com bzr branch directly,
> and have it automatically picked up and published within 24 hours. (as we do
> today.)

We won't lose any abilities.  Canonical would only assist with web site
design.

> At the same time I do not want to deal with the canonical pages.

This raises a question in my mind.  I'll look into the details of this.

/pm



More information about the ubuntu-doc mailing list