maas-devel team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

Hey,
In the past I've maintained maas ephemeral images, and used the maas
project for that code (well, being maintained from a
lp:~smoser/maas/<something>).

This has caused confusion on where exactly to file a bug against
the images, as they're not maas code (see http://pad.lv/1337538 for
example).

I'd like to get rid of ~smoser in the source for that and put a
team/project explicitly in charge of that code.  The code is currently at
  https://code.launchpad.net/~smoser/maas/maas-ephemerals-v2


My 2 suggestions:
 a.) keep using 'maas' as the project
     Agree on an upstream branch location:
        lp:~maas-maintainers/maas/maas-ephemerals
     Agree that bugs in maas images are explicitly maas bugs.
 b.) make a new project
     I'd just create a new project called 'maas-images' and add a team
     maas-images-maintainers that owned the code.

I don't have strong feelings.  I would tend to lean toward 'b' only
because I think that the members of the projects might differ, but I dont
think that is necessarily a problem.

Thoughts?