On Thu, Jul 9, 2015 at 3:39 PM, Paul Merlin wrote:
> So, we should review theses to ASF-ize them, shouldn't we?
Yes, I think so...
> BUT, I can't find a Version property on issues, nor the "Roadmap" view
> I'm used to. Do I need some JIRA privileges to handle this?
I have added you (and Jiri)
Niclas Hedhman a écrit :
> The pages you reference;
>
> Participate & Codebase -> Doesn't follow what ASF expects, where everyone
> are peers.
>
> Playing Field - talks about "reverts", where in ASF there is a concept of
> "Veto a change", which would lead to discussion and resolution. Whether
> th
The pages you reference;
Participate & Codebase -> Doesn't follow what ASF expects, where everyone
are peers.
Playing Field - talks about "reverts", where in ASF there is a concept of
"Veto a change", which would lead to discussion and resolution. Whether
that is a revert, amendment or something
Gang,
FIY, we already have some "by-laws" content divided in:
https://zest.apache.org/community/participate.html
https://zest.apache.org/community/playing_field.html
https://zest.apache.org/community/codebase.html
What we don't actually do, and maybe should, is maintain a CHANGES files.
I like
A discussion erupted recently on ComDev (Community Development mailing
list, open to all I think) about project specific by-laws.
It was highlighted that the Board resolution for creating projects
instructs the PMC to create the by-laws for the project.
The conclusion of that thread was roughly;
