How to collaborate on our style-guide (?)

[zampino]

I turned Issues and Wiki on on this repo.

we can branch edit push but this should be for drafts we think are fine.
where do we put comments on the single points?

shall we open an issue for each discussed poin?

[PragTob]

Totally pro on opening issues for each discussion point.

[andi-dev]

Best thing would probably be to really have a tool where to discuss it.
maybe if the a-n-i-m-a-t-e tool is ready.

don't know, i think one issue for each point could be difficult. maybe
everyone could make a sign (like initials) behind every point they
disagree with.

On 11/22/2012 11:37 AM, Andrea Amantini wrote:

I turned Issues and Wiki on on this repo.

we can branch edit push but this should be for drafts we think are fine.
where do we put comments on the single points?

shall we open an issue for each discussed poin?

---

Reply to this email directly or view it on GitHub:
#1

[janlelis]

Totally pro on opening issues for each discussion point.

[zampino]

@andi-bs let's not "over-tool" this discussion.
As usual: ideas and content first.
Do you think we loose control over many tickets?
will there be that many?
And it's also maybe not just a matter of disagreeing,
one may want to propose his different version of the statement.

I like the essentialness of one-statement in the README.md,
however after each line there could be a link to the wiki with dedicated commented examples.

But in a phase of discussion I re-vote for one-issue per style statement.

[PragTob]

Yep and someone may suggest new guidelines.

I like the one issue policy because that way we can have small focused discussions. We use the same way over at the shoes4 repository, ever since the mailing list has been nearly empty :-)