On Thu, Oct 27, 2016 at 3:01 AM, Michał Górny <mgo...@gentoo.org> wrote:
>
> Please review the following draft:
>
> https://wiki.gentoo.org/wiki/User:MGorny/GLEP:TPC
>

Regarding this paragraph: "Gentoo project provides a specific set of
official channels of contribution in which all project members are
required to participate. The exact list of these channels is outside
the scope of this specification."

i'm not actually certain that the first sentence is true.  I think the
only "official channel" of any kind that project members are required
to participate in is gentoo-dev-announce, and maybe gentoo-core.  I
don't think devs are actually required to either file or look at or
resolve bugs, for example.  Obviously it is encouraged.

I'd suggest just rewording this section to something like:
"Contributions can be accepted via any channel (whether official or
unofficial), as long as there is at least one project member willing
to support the particular channel and either commit or proxy the
contributions appropriately."

I think this reflects reality.  You can submit all the patches you
want via bugzilla but it isn't like we punish developers for not
getting around to accepting them, unless they're completely inactive
Gentoo-wide.

I do think the copyright issues belong in their own policy for the most part.

Part of me wonders if this really needs to be a GLEP (a mostly
inward-facing policy document) when it mostly documents existing
practices and policies.  Maybe what is needed is a more outward-facing
document, or some workflow documents?  The motivation states "Multiple
developers have noted various suggestions on Gentoo git workflow but
it never became an official policy," but I don't see any kind of
workflow really being solidified here either.

I guess my question on that front is what is the actual gap today, and
does this GLEP close it, and if not, is there either a better way, or
can we make the GLEP stronger to actually close the gap?  Just because
a workflow is optional doesn't mean that we can't standardize how it
is done.

-- 
Rich

Reply via email to