community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Williams <william...@gmail.com>
Subject Re: Incubating, Graduating & Code of conduct @ The ASF (spin-off of Better specifying....)
Date Fri, 10 Jul 2015 10:37:13 GMT
On Fri, Jul 10, 2015 at 10:23 AM, Pierre Smits <pierre.smits@gmail.com> wrote:
> Branko,
>
> I am confident that the existing project with bylaws, policies and/or
> standing rules formalised has had its share of discussions regarding
> applicability of elements therein.. And have resolved those. I guess that
> when such an element is either to vague or to restrictive so that the
> situation becomes untenable to move things forward, the community will find
> ways to resolve it.
>
> This thread is about:
>
>
>    - why does the Board tasks projects to create a set of bylaws for some
>    graduating podlings (when so many seem to feel that it doesn't add value);
>    - and when it does, why doesn't it  follow up on the task or request the
>    VP of the project to report on its progress until the task is completed.
>
> It has to come from somewhere. It seems to come to light during the
> incubation phase. Don't mentors advice properly?

I reckon the answer to these questions is simply that we've all
realized over a long period of time that project-specific bylaws -
while once popular and thought necessary - aren't desirable.  We
thought they were necessary a decade ago and over the course of time
realized not so much. And, while we've all come to that realization,
no one has taken the time to change the TLP resolution to reflect
that. And that's likely because most of us don't have bureaucratic
itches - you apparently do, so why not just ask the incubator
PMC/board to drop that paragraph?

Thanks,
--tim

Mime
View raw message