Re: [atomic-devel] Roadmap / tracking for Project Atomic top level

I mocked up a repo with labels, a milestone, and READMEs at each level. I also grabbed a copy of the Atomic Host Definition Joe posted in a Gist not so long ago.

https://github.com/nzwulfin/oversight

Check it out, let me know. I'm not too keen on the labels, there needs to be some way to convey the usage (issue status vs type) better than the way I've done it, just not coming up with anything.

The checklist markdown isn't quite right in the milestone, still checking on that syntax too.

-Matt M

On Tue, Jan 13, 2015 at 8:59 AM, Matt Micene <nzwulfin gmail com> wrote:

The template.md was lifted idea from the OpenShift PEP repo and looks like https://github.com/openshift/openshift-pep/blob/master/template.md. That would be for the larger issues that needed revie. I'm not advocating that specific template, just thought it would be good to have a guideline for the more formal (as yet undefined) process.

The Atom issue was looking at a way to use issues for roadmap or complex issue tracking.

On Mon, Jan 12, 2015 at 6:28 PM, Colin Walters <walters verbum org> wrote:
On Mon, 2015-01-12 at 09:45 -0500, Matt Micene wrote:
> Bumping this for the post-holiday review, are we missing anything
> major to start this tracker repo?

I think so. The only question I have at the moment is: What would
be a sample "template.md"? Would that be like the
https://github.com/atom/atom/issues/3684
you linked to earlier?