Just FYI, admin privileges aren't necessary for editing the wiki or issues.
Only for accepting pull requests into the repo.

On Monday, October 6, 2014, John Caron <[email protected]> wrote:

> Thanks to John and Chris for summarizing. I think we are almost ready to
> go. Heres my summary:
>
>
> Charter/Scope
>
> (1) What use-cases cannot be met with the classic model, or could be met
> much more easily with the extended model?
>
> (2) Possible things to deprecate (because there is a better way to do it)
>
> (3) Backwards compatibility is desirable, but not required if there is a
> substantial advantage in simplicity and clarity. So respect precedent and
> dont constrain important innovation. There has to be a strong advantage for
> making incompatible changes.
>
> (4) If we introduce a new way to do something, we should carefully
> consider removing the old way, because it is easier for users of the
> convention if there is only one way to do something.
>
>
> Process:
>
> We will try out using github for the discussion and the "discussion
> summary" document.
>
> 1) We will use the CF github account if possible.
>
> 2) We will create a new repo under https://github.com/cf-convention, say,
> https://github.com/cf-convention/CF-2.
>
> 3) We will use the "Issues" feature to discuss. Essentially this allows
> threaded discussion, and new issues are created as needed to keep things
> on-topic.
>
> 4) We will use the wiki to create a "discussion summary" document. It
> looks adequate in that we can create various pages and link them together.
> It will be a collaborative document where anyone can write (add your name
> to your edits perhaps?) At some point we will probably transition to a
> collection of documents in the repo.
>
> Anyway, we can get started and refine this set of guidelines as we go.
>
> Questions:
>
> - Who has admin rights to the CF github account?
> - How do people get permission to write?
> - Any other ground rules needed?
> - Any changes to the above?
>
>
>

-- 
Excuse my brevity, Sent from Gmail Mobile.

Reply via email to