Taiga board for tracking CPE epic briefs

[Ben Cotton]

Hi all,

Following on from our conversation with Aoife at the post-DevConf meeting,
I have created a Taiga board we can use to track the epic briefs we draft
and send to the CPE team:

https://teams.fedoraproject.org/project/fedora-council-infrastructure-pri...

All council members have the ability to create and modify the cards and the
board is public for community transparency. I have created epics for each
quarter. We can adjust the settings as we start using this board more
heavily.

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis

[Neal Gompa]

On Mon, Feb 10, 2020 at 3:41 PM Ben Cotton <bcotton(a)redhat.com&gt; wrote:
>  Hi all,
>
>  Following on from our conversation with Aoife at the post-DevConf meeting, I have created
> a Taiga board we can use to track the epic briefs we draft and send to the CPE team:
>
>  https://teams.fedoraproject.org/project/fedora-council-infrastructure-pri...
>
>  All council members have the ability to create and modify the cards and the board is
> public for community transparency. I have created epics for each quarter. We can adjust
> the settings as we start using this board more heavily.
>  
The card descriptions seem to lack a description and link to an
internal Confluence instance that isn't externally visible. Is that
intentional? It makes it a bit difficult to figure out what some of
these cards mean. For example, I'm not sure what "dist-git merge"[1]
means...

[1]:
https://teams.fedoraproject.org/project/fedora-council-infrastructure-pri...


--
真実はいつも一つ！/ Always, there's only one truth!

[Ben Cotton]

On Mon, Feb 10, 2020 at 4:10 PM Neal Gompa <ngompa13(a)gmail.com&gt; wrote:
>  The card descriptions seem to lack a description and link to an
>  internal Confluence instance that isn't externally visible. Is that
>  intentional? It makes it a bit difficult to figure out what some of
>  these cards mean. 
The link to the internal tools are intentional, as that's where CPE
tracks their work. The cards aren't very descriptive now, but we'll go
through and fill out more detail. (I created this board a few hours
ago). And of course future cards will start with more detail because
they won't have been copied from a variety of unstructured places.

-- 
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis

[Leigh Griffin]

On Mon, Feb 10, 2020, 21:17 Ben Cotton <bcotton(a)redhat.com&gt; wrote:

>  On Mon, Feb 10, 2020 at 4:10 PM Neal Gompa <ngompa13(a)gmail.com&gt;
> wrote:
>  >
>  > The card descriptions seem to lack a description and link to an
>  > internal Confluence instance that isn't externally visible. Is that
>  > intentional? It makes it a bit difficult to figure out what some of
>  > these cards mean.
>
>  The link to the internal tools are intentional, as that's where CPE
>  tracks their work. 

While this is true, our intention is to have a wiki (or docs page) with the
maturer versions of the spec available for public visibility. The internal
confluence setup allows us iterate and pull together multiple internal comm
streams, meetings, questions, tickets and lots of other noise. Once a spec
transitions into stable we share that for comments and input. We do this
already via devel posts (Rawhide Gating is a great example) and our
intention is to improve that and have more ODF (see gitforge convo) style
phases to get input on the specs. This Taiga board is a great first step
and when details emerge on the cards I'd love to see that ideation
transition into discussions to improve and move the idea forward.
Ultimately I'd love to see where the community can help us progress or
accelerate some backlog ideas.

The cards aren't very descriptive now, but we'll go
>  through and fill out more detail. (I created this board a few hours
>  ago). And of course future cards will start with more detail because
>  they won't have been copied from a variety of unstructured places.
>
>  --
>  Ben Cotton
>  He / Him / His
>  Senior Program Manager, Fedora & CentOS Stream
>  Red Hat
>  TZ=America/Indiana/Indianapolis
>  _______________________________________________
>  council-discuss mailing list -- council-discuss(a)lists.fedoraproject.org
>  To unsubscribe send an email to
>  council-discuss-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct:
>  https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
>  https://lists.fedoraproject.org/archives/list/[e-mail]...
>