Foundation decision-making and community involvement

[ncoden]

The decision-making tools we have now are:

• discussions in issues : dispersed and became old
• discussions in Slack : not organized or formatted
• this Yetinaut repo : private

The code standard https://github.com/zurb/foundation-code-standards seems abandoned and totally ignored by contributors. Having it in another repo does not help to give it visibility.

So we could use :

• Wiki to centralize code standard and contributing advices with a public roadmap. Anyone could know (without reading all the issues and PR) the problems that Foundation is meeting and planned solutions. It would help users a lot to open issues and explain what they expect for future releases.
• Projects to organize and sort these issues more easily than with tags and milestones.

That would be the first step for a centralized, organized and active decision-making, with the community involved.

What do you think ?

[kball]

I very much like this direction - have any of the @zurb/yetinauts used projects enough to have a sense of their strengths and weaknesses yet?

I'd also like us to have a clear picture of what should live in the wiki vs the docs (which are also included in the repository). One challenge with the wiki is that it does not really support a pull request/review style workflow, which I think is very valuable for discussions about direction, roadmaps, etc.

Perhaps instead these should live in pages (md or other) within the repo, rather than on the wiki?

[ncoden]

The doc is what about the project currently is. It is generated from the code : components usage, Js or Sass elements, settings... The wiki would be what the project should be and how : roadmap, code standard, advices...

Maybe the standard and advices could also be in the repo. But not roadmap, which is too temporal. However, I think Wiki would be easier to use, with issues. PR are too complicated to set up and should be reserved for possibly breaking changes (obviously like code).

[brettsmason]

So I'm still learning Git/Github so my input probably isn't hugely useful. Generally I'll be totally happy going with what the general consensus is.

However I do like the idea of a public facing summary for the roadmap and code standards. I'll leave that up to the more knowledgeable on where that should be though 😄

Generally more transparency for the community can only be a good thing.