Proposal: Create product for each derivative's documentation

[Cody A.W. Somerville]

On Tue, Mar 31, 2009 at 10:46 AM, Matthew East <mdke at ubuntu.com> wrote:

> On Tue, Mar 31, 2009 at 2:26 PM, Cody A.W. Somerville
> <cody-somerville at ubuntu.com> wrote:
> > Hello Matthew,
> >
> > On Tue, Mar 31, 2009 at 9:53 AM, Matthew East <mdke at ubuntu.com> wrote:
> > Anyhow, I think the reasoning for taking this approach is stronger than
> > ever. The launchpad model is designed to have a single codebase
> associated
> > with a project and allow for the grouping of related codebases via
> project
> > groups. By having projects for the different flavours, we're able to take
> > full advantage of the different features that launchpad provides while
> still
> > maintaining a high level of cohesion and teamwork. In this particular
> case,
> > I was motivated by the desire to be able to take advantage of the
> launchpad
> > bazaar branch shortcut lp:$project as well as the translation features.
>
> My view hasn't changed - I'm keen to use a single project to ensure
> that the team doesn't fragment initiatives and branches don't end up
> getting too diverged. It's very useful to have all the project's
> branches on one page - https://code.launchpad.net/ubuntu-doc and
> setting up an xubuntu-docs project is essentially a statement that
> xubuntu-docs is not part of the ubuntu-doc project. That's even more
> pronounced in circumstances where it's been done without discussion
> and contrary to previous majority consensus of the team. Since it was
> discussed, nothing has changed in Launchpad's design or the group's
> setup (except that we've stopped tracking bugs in the upstream
> project).
>
> I'm very keen to avoid that stigma, because xubuntu-docs *should* be
> part of the same project.
>
> In fact, the reality is that all these projects are part of the Ubuntu
> project, and aren't separate upstream projects at all. The only reason
> we have an upstream project on Launchpad at all is because of
> deficiencies in Launchpad's design.


This will continue to occur using a project group.


> I don't think the two advantages you've mentioned are at all
> significant. First, the bzr branch shortcut lp:project can still be
> used (e.g. lp:~ubuntu-core-doc/ubuntu-doc/kubuntu-jaunty), even if the
> form is ever so slightly longer. It doesn't take very long to type,
> and once you have got the branch, it will remember the location.
> Secondly, translations of documentation aren't done under the project
> at all, they are and should remain to be done under the Ubuntu project
> at https://translations.launchpad.net/ubuntu/jaunty/+source/xubuntu-docs.


Yes and it still is because the series (which we didn't have when we were
all in one project) are connected to the corresponding packages in Ubuntu.
Further, in an upcoming release of Launchpad, I believe translations will
also be able to be automatically imported from series - another benefit not
otherwise possible if we keep our current setup.

So it seems like we both get what we want with different projects by using a
project group.

Cheers,

-- 
Cody A.W. Somerville
Software Systems Release Engineer
Foundations Team
Custom Engineering Solutions Group
Canonical OEM Services
Phone: +1-781-850-2087
Cell: +1-506-471-8402
Email: cody.somerville at canonical.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-doc/attachments/20090331/05b80f12/attachment.html>