----- Original Message -----
> From: "Matt Micene" <nzwulfin gmail com>
> To: atomic-devel projectatomic io
> Sent: Friday, December 12, 2014 12:37:45 PM
> Subject: Re: [atomic-devel] Roadmap / tracking for Project Atomic top level
>
Looks good to me.> Colin,
>
> Those are both things that would likely fall in this repo, even if only as
> tracking upstream dependencies for an enhancement.
>
> Here's a rough cut of what I'm thinking at this point for the repo. We'd
> use issues to track various different items based on label categories. Any
> artifacts would be tracked in folders:
>
> Repo structure
> =====
>
> tracker/
> |-- proposals/
> |-- template.md
> |-- accepted/
> |-- opposed/
> |-- design/
> |-- packages/
> |-- Current minimum accepted for milestone
> |-- test plans/
> |-- Atomic Host Definition
> |-- Benevolent Dictators - the deciderers
> |-- Roadmap (?)
> |-- README.md - how to use this repo
>
> Labels
> =====
> Types
> -----
> proposal
> bug
> enhancement
> question
>
> Domains
> -----
> architecture - (don't like the name)
> tools - tooling
> docs - documentation problems
> ecosystem - Fedora / CentOS specific
> delivery - shipping issues (vagrant support, local compose)
> upstream - issue with upstream package
>
> Components
> -----
> rpm-ostree
> kubernetes
> flannel
> cockpit
> docker
> rocket
>
> Status
> -----
> helpwanted
> confirmed
> reviewing
> inprogress
> blocker
>
> Milestones
> -----
> Collections of issues
>
> So for the flannel docker-opts, I can see that as an issue with a 'why this
> impacts Atomic' labeled as flannel, blocker, upstream, enhancement. This
> could also be referenced by a larger issue tracker 'Add Flannel' that used
> the GitHub markdown checklists.
>
> Something like this tracker issue (though I don't know why they didn't use
> a Milestone here)
> https://github.com/atom/atom/issues/3684
>
>
> Am I off base here?
Jason
>
> -Matt M
>
> On Fri, Dec 12, 2014 at 3:12 PM, Colin Walters <walters verbum org> wrote:
>
> > On Fri, Dec 12, 2014, at 08:40 AM, Matt Micene wrote:
> >
> > Joe, sure I can take a first cut at a potential structure and labels for
> > the repo.
> >
> > Anyone have any particular labels they want to see or outstanding issues
> > they think can serve as exemplars
> >
> >
> >
> > A good example issue outstanding is the "environment" + flannel <-> Docker
> > <-> interlock. See this issue:
> > https://github.com/coreos/flannel/pull/85
> >
> >
> > For the Atomic Host, efficient deltas. There is some activity in
> > https://bugzilla.gnome.org/show_bug.cgi?id=721799
> > but more work needs to happen to support this in the rel-eng tools. And
> > if we do use Courgette, it would be a useful breakout to investigate for
> > RPMs and Docker layers as well.
> >
> > Is this the kind of things we're looking for on the list?
> >
>