Re: [gentoo-project] RFC: GLEP - Require Projects to report to Council Monthly

[Kent Fredric]

On Thu, 19 Jan 2017 16:59:09 -0500
"William L. Thomson Jr." <wlt-ml@××××××.com> wrote:

> On Friday, January 20, 2017 10:39:49 AM EST Kent Fredric wrote:
> >
> > The framing here is that this structure is a stick to keep everyone in line,
> > and that the beatings shall continue to drive up morale.
>
> You are taking this completely out of context.

> The reports I am suggesting, could be linked into the status board your
> suggesting. So your basically proposing the same thing in a different way.

Right. I suspect we're probably closer to the same page than we think overall,
just your initial statements seemed to give me the wrong subtext, and I wanted
to steer clear away from it.

> Oh yes, create more positions and roles no one wants to fulfill. Are you going
> to do that? Just another area/project/team to be understaffed. FYI this is
> what used to happen as part of the newsletter.

There will still be a person or persons submitting data, and there will
be a person or persons receiving and collating that data.

All my framing concerns itself with is assigning the responsibility for this
interaction towards the recipient, and making it clear from the nature of the
interaction that feedback is regularly wanted, but not mandatory.

> > As an adjunct, it might also be useful to have some sort of active "status
> > board" for different projects that can be edited by anyone easily and can
> > easily be displayed in bulk, and not have any real requirements on its
> > frequency of change.
>
> That is something that could be programmed into wiki pages for each project
> tracking commit activity. However it would still not tell you where the
> project/team is going or information about its activities.

By "displayed in bulk", if I was unclear, the idea was to be able to have a
global "Gentoo Right now" status page where one could just skim-read through
all the given statuses, ( maybe sort them by freshness )

Commit stats could be displayed on the side, but I wouldn't consider them
the most important part of this design, it would just be a bit of polish
on the finished product, mostly because the signal it gives from the overview
of all of gentoo is very weak, and doesn't really tell you much more
than "alive/dead" ( and of course, not all projects even have commit data )

>
> > And for groups who want to bother to sit down and have meetings,
> > brief outcomes from those meetings could be part of that status board,
> > perhaps with longer contents in links.
>
> That is in part what I am suggesting in a report provided to the council.
>
> The reports I am suggesting, could be linked into the status board your
> suggesting. So your basically proposing the same thing in a different way.