New plan for the future of objectives reports (and editions too!)

[Matthew Miller]

Hi Objective leads, Edition leads, and Council representatives!

I’d like to try something new to replace some of our meetings.

Every four weeks, the Fedora Council has a meeting devoted to Objectives
updates, and in a separate meeting a similar thing for the Engineering and
Mindshare sides of the project and the Diversity and Inclusion team. The
idea is that this gives these leads the opportunity to share the current
status of their work with the Council and the community at-large. However,
these meetings are sometimes hard for people to attend and don’t provide
updates in a reliable or consumable way.

I have asked the FPgM (hi Ben!) to create a repository[1] that leads can use
to provide updates. Each Objective and Edition has a file with a “traffic
light” status indicator (red, yellow, or green) and the ability to provide
status information. I’d like to ask you all to update this file at the end
of each week. (That is, every Friday, please.)

Nothing complicated: just make sure the color is right for your current
status (green: on track, everything is cool; yellow: there’s something that
might be a concern and the Council should be aware; red: there’s an active
problem and help from the Council is needed).

The idea behind this is that you won’t have to think back too far about what
has happened. About once a month, Ben will aggregate your status updates
into a post on the Community Blog so that we can share this information with
the Fedora community.

We'd like to have this for the Council Objectives, but also for the official
Fedora Editions, and for Mindshare and Engineering overall from the Council
representatives for those areas. (I'm posting this to the council list but
will also send privately or to area mailing lists because I know it's hard
to keep up with all the lists!) 

We want to make it easy for you to report what is going on in your area and
for the community to find it. With this, we’ll be able to publish your
current status to docs.fedoraproject.org and the regular Community Blog
posts will give a meaningful diff to the community. If you have suggestions
for how we can improve this process, please let us know.

[1] https://pagure.io/Fedora-Council/status_reports


-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Matthew Miller]

PS: still doing objective update meeting today but we can talk about this
plan. :)

-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader

[Adam Samalik]

So I was wondering what would be the best way to do a periodic update for
Minimization so that's everything is on one place and people can see what's
going on — and this feels like a really nice high-level place for people to
start looking for updates.

I imagine that — in addition to the green/yellow/red status — I'd include
weekly/monthly highlights? So there would be a history also. And I could
always link to a blog post or whatever for more details if people are
curious.

And this for all the objectives and editions at one place feels useful, too.

I like it!

Cheers,
Adam



On Wed, Jul 3, 2019 at 2:44 PM Matthew Miller <mattdm(a)fedoraproject.org&gt;
wrote:

>  Hi Objective leads, Edition leads, and Council representatives!
>
>  I’d like to try something new to replace some of our meetings.
>
>  Every four weeks, the Fedora Council has a meeting devoted to Objectives
>  updates, and in a separate meeting a similar thing for the Engineering and
>  Mindshare sides of the project and the Diversity and Inclusion team. The
>  idea is that this gives these leads the opportunity to share the current
>  status of their work with the Council and the community at-large. However,
>  these meetings are sometimes hard for people to attend and don’t provide
>  updates in a reliable or consumable way.
>
>  I have asked the FPgM (hi Ben!) to create a repository[1] that leads can
>  use
>  to provide updates. Each Objective and Edition has a file with a “traffic
>  light” status indicator (red, yellow, or green) and the ability to provide
>  status information. I’d like to ask you all to update this file at the end
>  of each week. (That is, every Friday, please.)
>
>  Nothing complicated: just make sure the color is right for your current
>  status (green: on track, everything is cool; yellow: there’s something that
>  might be a concern and the Council should be aware; red: there’s an active
>  problem and help from the Council is needed).
>
>  The idea behind this is that you won’t have to think back too far about
>  what
>  has happened. About once a month, Ben will aggregate your status updates
>  into a post on the Community Blog so that we can share this information
>  with
>  the Fedora community.
>
>  We'd like to have this for the Council Objectives, but also for the
>  official
>  Fedora Editions, and for Mindshare and Engineering overall from the Council
>  representatives for those areas. (I'm posting this to the council list but
>  will also send privately or to area mailing lists because I know it's hard
>  to keep up with all the lists!)
>
>  We want to make it easy for you to report what is going on in your area and
>  for the community to find it. With this, we’ll be able to publish your
>  current status to docs.fedoraproject.org and the regular Community Blog
>  posts will give a meaningful diff to the community. If you have suggestions
>  for how we can improve this process, please let us know.
>
>  [1] https://pagure.io/Fedora-Council/status_reports
>
>
>  --
>  Matthew Miller
>  <mattdm(a)fedoraproject.org&gt;
>  Fedora Project Leader
>  _______________________________________________
>  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]...
>  

-- 

Adam Šamalík
---------------------------
Senior Software Engineer
Red Hat

[Ben Cotton]

On Thu, Jul 4, 2019 at 3:47 AM Adam Samalik <asamalik(a)redhat.com&gt; wrote:

>  I imagine that — in addition to the green/yellow/red status — I'd
> include weekly/monthly highlights? So there would be a history also. And I could always
> link to a blog post or whatever for more details if people are curious.
>  
Yes. The idea is that you'd include whatever summary information is
useful every time you update. So if you invented the shrink ray one
week, you'd put that as an item in your update at the end of the week.

On Thu, Jul 4, 2019 at 4:24 AM Amita Sharma <amsharma(a)redhat.com&gt; wrote:
>  Sometimes a ticket can be in Red state where things are pending due to some other reason
> (there can be several) and not because there is an active issue where council's
> attention is required. 
On Thu, Jul 4, 2019 at 9:36 AM María Leandro <tatica(a)fedoraproject.org&gt; wrote:
>  Would be nice to add a purple or other tag for the completed tasks and have an historic
> that can later be gathered on monthly reports of success? 
The color code is for the area overall, not for individual items. So
if D&I has a bunch of open tickets, but they're working through them
well, then they're probably green. If they have one ticket open and
are also facing an existential crisis, that's yellow or red.


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis

[Amita Sharma]

This sounds good.

I am just thinking about this description though " (green: on track,
everything is cool; yellow: there’s something that
might be a concern and the Council should be aware; red: there’s an active
problem and help from the Council is needed)."

Sometimes a ticket can be in Red state where things are pending due to some
other reason (there can be several) and not because there is an active
issue where council's attention is required.

Thanks,
Amita

On Wed, Jul 3, 2019 at 6:13 PM Matthew Miller <mattdm(a)fedoraproject.org&gt;
wrote:

>  Hi Objective leads, Edition leads, and Council representatives!
>
>  I’d like to try something new to replace some of our meetings.
>
>  Every four weeks, the Fedora Council has a meeting devoted to Objectives
>  updates, and in a separate meeting a similar thing for the Engineering and
>  Mindshare sides of the project and the Diversity and Inclusion team. The
>  idea is that this gives these leads the opportunity to share the current
>  status of their work with the Council and the community at-large. However,
>  these meetings are sometimes hard for people to attend and don’t provide
>  updates in a reliable or consumable way.
>
>  I have asked the FPgM (hi Ben!) to create a repository[1] that leads can
>  use
>  to provide updates. Each Objective and Edition has a file with a “traffic
>  light” status indicator (red, yellow, or green) and the ability to provide
>  status information. I’d like to ask you all to update this file at the end
>  of each week. (That is, every Friday, please.)
>
>  Nothing complicated: just make sure the color is right for your current
>  status (green: on track, everything is cool; yellow: there’s something that
>  might be a concern and the Council should be aware; red: there’s an active
>  problem and help from the Council is needed).
>
>  The idea behind this is that you won’t have to think back too far about
>  what
>  has happened. About once a month, Ben will aggregate your status updates
>  into a post on the Community Blog so that we can share this information
>  with
>  the Fedora community.
>
>  We'd like to have this for the Council Objectives, but also for the
>  official
>  Fedora Editions, and for Mindshare and Engineering overall from the Council
>  representatives for those areas. (I'm posting this to the council list but
>  will also send privately or to area mailing lists because I know it's hard
>  to keep up with all the lists!)
>
>  We want to make it easy for you to report what is going on in your area and
>  for the community to find it. With this, we’ll be able to publish your
>  current status to docs.fedoraproject.org and the regular Community Blog
>  posts will give a meaningful diff to the community. If you have suggestions
>  for how we can improve this process, please let us know.
>
>  [1] https://pagure.io/Fedora-Council/status_reports
>
>
>  --
>  Matthew Miller
>  <mattdm(a)fedoraproject.org&gt;
>  Fedora Project Leader
>  _______________________________________________
>  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]...
>

[Adam Samalik]

On Thu, Jul 4, 2019 at 10:24 AM Amita Sharma <amsharma(a)redhat.com&gt; wrote:

>  This sounds good.
>
>  I am just thinking about this description though " (green: on track,
>  everything is cool; yellow: there’s something that
>  might be a concern and the Council should be aware; red: there’s an active
>  problem and help from the Council is needed)."
>
>  Sometimes a ticket can be in Red state where things are pending due to
>  some other reason (there can be several) and not because there is an active
>  issue where council's attention is required.
>  
As I understand it, the help could come in many ways, even if that means
working with the objective lead to reset expectations, restructure the
objective, deprioritize other efforts to concentrate our focus on this, or
simply move deadlines, etc. But I can't imagine a project/objective being
out of control and council just watching and hoping for the best. :)


>  Thanks,
>  Amita
>
>  On Wed, Jul 3, 2019 at 6:13 PM Matthew Miller <mattdm(a)fedoraproject.org&gt;
>  wrote:
>
> > Hi Objective leads, Edition leads, and Council representatives!
> >
> > I’d like to try something new to replace some of our meetings.
> >
> > Every four weeks, the Fedora Council has a meeting devoted to Objectives
> > updates, and in a separate meeting a similar thing for the Engineering and
> > Mindshare sides of the project and the Diversity and Inclusion team. The
> > idea is that this gives these leads the opportunity to share the current
> > status of their work with the Council and the community at-large. However,
> > these meetings are sometimes hard for people to attend and don’t provide
> > updates in a reliable or consumable way.
> >
> > I have asked the FPgM (hi Ben!) to create a repository[1] that leads can
> > use
> > to provide updates. Each Objective and Edition has a file with a “traffic
> > light” status indicator (red, yellow, or green) and the ability to provide
> > status information. I’d like to ask you all to update this file at the end
> > of each week. (That is, every Friday, please.)
> >
> > Nothing complicated: just make sure the color is right for your current
> > status (green: on track, everything is cool; yellow: there’s something
> > that
> > might be a concern and the Council should be aware; red: there’s an active
> > problem and help from the Council is needed).
> >
> > The idea behind this is that you won’t have to think back too far about
> > what
> > has happened. About once a month, Ben will aggregate your status updates
> > into a post on the Community Blog so that we can share this information
> > with
> > the Fedora community.
> >
> > We'd like to have this for the Council Objectives, but also for the
> > official
> > Fedora Editions, and for Mindshare and Engineering overall from the
> > Council
> > representatives for those areas. (I'm posting this to the council list but
> > will also send privately or to area mailing lists because I know it's hard
> > to keep up with all the lists!)
> >
> > We want to make it easy for you to report what is going on in your area
> > and
> > for the community to find it. With this, we’ll be able to publish your
> > current status to docs.fedoraproject.org and the regular Community Blog
> > posts will give a meaningful diff to the community. If you have
> > suggestions
> > for how we can improve this process, please let us know.
> >
> > [1] https://pagure.io/Fedora-Council/status_reports
> >
> >
> > --
> > Matthew Miller
> > <mattdm(a)fedoraproject.org&gt;
> > Fedora Project Leader
> > _______________________________________________
> > 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]...
> >
>  _______________________________________________
>  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]...
>  

-- 

Adam Šamalík
---------------------------
Senior Software Engineer
Red Hat

[María Leandro]

>  Sometimes a ticket can be in Red state where things are pending due to
>  some other reason (there can be several) and not because there is an active
>  issue where council's attention is required.
>
>  
From what I was able to understand, the color code will only correspond for
Council's attention. A green label wouldn't mean that a task is done, but
that it's on track (even if there are pending tasks)

Would be nice to add a purple or other tag for the completed tasks and have
an historic that can later be gathered on monthly reports of success?

-- 
tatica
Maria Gracia Leandro
http://www.tatica.org
http://fedoraproject.org/wiki/User:tatica
LinuxUser= 440285  GPG Public Key: E1CDCC56

[Justin W. Flory]

Hi all,

I like this idea, but have three suggestions:

(1) Better publicize a link to the published docs site
(2) Create example of how this might look 12 months later
(3) Collect better resources for infrequent git / AsciiDoc users

First, I couldn't find a link to the published status reports. I opened
the issue below to add a link to the published docs site to the README
and Pagure repository. It would be helpful to visually understand how
status reports look today when rendered:

    https://pagure.io/Fedora-Council/status_reports/issue/1

Secondly, could someone create an example page for a team of how this
might look 12 months down the road? I was initially confused by this
explanation:

On 7/8/19 7:20 AM, Ben Cotton wrote:
>  The color code is for the area overall, not for individual items. So
>  if D&I has a bunch of open tickets, but they're working through them
>  well, then they're probably green. If they have one ticket open and
>  are also facing an existential crisis, that's yellow or red. 
A detailed example for the Foobar Objective and a snapshot of status
reports at "green" or "red" states is helpful to understand the
Council's expectations from status reports.

Additionally, please consider updating these status reports is a
"technical" contribution. For groups like D&I and Mindshare, elected
persons may not be familiar with AsciiDoc, Antora, or any of the Fedora
Docs tooling. An elected person might not use git on a daily basis too.
I don't think it is unfair to ask someone to learn these tools, but it
should be easier than it currently is for someone to learn about them.

Overall though, I support this idea. From my POV, I am *super*
appreciative of the added help with out-bound reporting on the Community
Blog from status reports. I see that as a double-effect: it makes
out-bound reporting easier for objectives/editions/sub-projects and also
extracts more information from the new and exciting areas deep within
Fedora out into the wider public.

-- 
Cheers,
Justin W. Flory
justinwflory.com
TZ=America/Chicago
Pronouns: he/him/his

[Ben Cotton]

On Mon, Jul 15, 2019 at 6:26 PM Justin W. Flory <jflory7(a)gmail.com&gt; wrote:
>  First, I couldn't find a link to the published status reports. 
That's because they're not being published yet. We set this up as
Asamalik was on PTO and right before I was out for a week, so I
figured I'd let people have a couple of weeks to get used to it (and
actually submit reports) before we started publishing them.

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis

[Justin W. Flory]

On 7/22/19 8:00 AM, Ben Cotton wrote:
>  On Mon, Jul 15, 2019 at 6:26 PM Justin W. Flory
> <jflory7(a)gmail.com&gt; wrote:
> >
> > First, I couldn't find a link to the published status reports.
>  
>  That's because they're not being published yet. We set this up as
>  Asamalik was on PTO and right before I was out for a week, so I
>  figured I'd let people have a couple of weeks to get used to it (and
>  actually submit reports) before we started publishing them.
>   
Perfectly understandable. Hope you enjoyed your time off. :)

To this end, I see it as a helpful next step to have a common example of
what these reports might look like in 6-12 months. This way everyone has
the same understanding of what is expected from these updates.

-- 
Cheers,
Justin W. Flory
justinwflory.com
TZ=America/Chicago
Pronouns: he/him/his

[Amita Sharma]

On Tue, Jul 23, 2019 at 9:24 AM Justin W. Flory <jflory7(a)gmail.com&gt; wrote:

>  On 7/22/19 8:00 AM, Ben Cotton wrote:
>  > On Mon, Jul 15, 2019 at 6:26 PM Justin W. Flory <jflory7(a)gmail.com&gt;
>  wrote:
>  >>
>  >> First, I couldn't find a link to the published status reports.
>  >
>  > That's because they're not being published yet. We set this up as
>  > Asamalik was on PTO and right before I was out for a week, so I
>  > figured I'd let people have a couple of weeks to get used to it (and
>  > actually submit reports) before we started publishing them.
>  >
>
>  Perfectly understandable. Hope you enjoyed your time off. :)
>
>  To this end, I see it as a helpful next step to have a common example of
>  what these reports might look like in 6-12 months. This way everyone has
>  the same understanding of what is expected from these updates.
>  
+1, It will help setting right expectations. Thanks.


>  --
>  Cheers,
>  Justin W. Flory
>  justinwflory.com
>  TZ=America/Chicago
>  Pronouns: he/him/his
>
>  _______________________________________________
>  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]...
>

[Matthew Miller]

On Mon, Jul 22, 2019 at 10:54:33PM -0500, Justin W. Flory wrote:
>  To this end, I see it as a helpful next step to have a common example
> of
>  what these reports might look like in 6-12 months. This way everyone has
>  the same understanding of what is expected from these updates. 
It's now rather than 6-12 months, but the CoreOS one:


https://pagure.io/Fedora-Council/status_reports/raw/852cae3dd56f25ff06e78...

is a good example. 


-- 
Matthew Miller
<mattdm(a)fedoraproject.org&gt;
Fedora Project Leader