Too long web developers have been held hostage by working groups, with exclusive membership and each member with their own agendas. The aim of this group is to take the technologies now being provided by the browser vendors and use them to our advantage.
The Web Components Organisation has been created to encourage the web development community at large - rather than browser vendors and commercial organisations - to come together and discuss, build and improve standards with web components. The organisation has been set up on Github to allow development to happen in the open.
The organisation structure is one of Anarchy - that is, there is no central body or authority dictating how these components are agreed upon. Anyone can propose a new tag using Github wiki pages and issues - allow discussion and iteration to happen
All development happens as living documents - all in the open, through issues and pull requests - where all developers are free to debate, discuss and argue the good and bad points.
The process is still in flux at the moment, but after initial proposal the first milestone of any component is to agree up on a draft spec that allows the component to be built (currently) with the X-Tag Polyfill. The end game of any tag is to iterate and agree a potential final spec that allows the tag to become a native browser tag in the HTML spec.
Web Components are at set of technologies available (or soon to be available) in all modern web browsers. Using custom elements aka X-tags, templates, CSS decorators and the Shadow DOM they allow standard components (such as calendars, lightboxes and image galleries, modals, etc) to be defined and distributed as HTML markup - there is no W3C or WHATWG organisation to slow developers down, all these standards are defined by us.
We need to stop this madness!
You will see the Tag Proposal page on the Wiki, and along with that an issue for discussion linked to the proposal. This is the main place to start discussion - some parts may be spun off into separate issues, or even xtags, but we use this to get the ball rolling. Follow the same style (beware - the style is still in an early stage)
You are free to create an repository on your own account and create the wiki page there, along with other assets - however the issue for discussion to be considered a proposal must be then posted in the main site issues if only to provide a canonical place for these to live. If a proposal has a general consensus of yes, then the repo will be added to the organisation - then discussion could move there (and there is no rule that says you cannot have discussion on your own repo, it's just it may be missed by the larger community).