Chair - self nomination

Dear all Group Members,

I've selected myself as Chair. Let's call it Chair pro tem, and the Chair
selection process is still open and available to anyone that's a group
member. This action was chiefly motivated by wanting to setup polls and
starting to organize a little bit of the infrastructure a little bit better.

HTACG was proposed and accepted in order to become the current, modern
gatekeeper and protector of HTML Tidy, and the use of a W3C Community Group
lends some air of legitimacy in the wider scope, and if we plan things
well, will ensure that HTML Tidy never again reaches the state of
stagnation that it recently suffered. Acting as a community we can work
together so that the time limits and priorities of a single member don't
inhibit things for us in the future.

Currently there's a huge flurry of activity over at our github site (
https://github.com/htacg), including a lot of discussions about commit
access rights, the best approach to bring the current, stale Master up to
speed, cmake vs. build system support, and so on. This is an _excellent_
sign that HTML Tidy still attracts interest and has relevance in the world.

It's also a very _bad_ sign and exhibits a real lack of leadership. Aside
from the disorganized manner of using "Issues" as a discussion forum,
there's noticeable dissatisfaction expressed in not having any true
direction. I take full responsibility for this because as the proposer
(founder?) of HTACG I suppose it was assumed that I would automatically
take charge.

If you will follow me, then I am willing to lead until you collectively
decide to boot me out of the Chair position. As such I will outline what I
consider our immediate priorities:

- We bring public discussion of things that will break regressions, break
APIs, and break build systems to the public mailing HTACG mailing list (
https://lists.w3.org/Archives/Public/public-htacg/).

- We encourage all of our Github members to join HTACG, because it is in
HTACG that the group will make public decisions based on the public mailing
list.

- We encourage any developer, user, or integrator of HTML Tidy to join
HTACG for the same reasons mentioned above.

- We decide who has commit and PR access. Many of you have a long and
stable history with HTML Tidy, and there's no reason to be suspicious of
anyone's motives. If you currently do not have access, request it on the
public mailing list. There's no guarantee that Ionel or I (repo owners)
know who you are, so please provide a justification.


Also,

- If you are having issues with access or privileges, that's not really in
the public interest. Use the contributor list (
http://lists.w3.org/Archives/Public/public-htacg-contrib/) or internal list
(https://lists.w3.org/Archives/Member/internal-htacg/).


I will now make these following executive decisions for the sake of
expediency and to get us to a stable track as soon as possible:

- We will move Tidy to a Semantic versioning system. Code contributions for
the new branch are appreciated, and I will look into this myself, too. The
first stable release of HTML Tidy for HTML 5 will be 5.0.0.

- If Geoff McLane is still willing after the misunderstanding over access
rights, he will push his current branch to "develop-500". All future PR's
will be against this branch only.

- Upon HTACG consensus of the develop-500 branch, we will merge it into
Master and declare that it's a stable, non-experimental release. I think
that a one week comment, testing, and code review period should be
sufficient for this.


-- 
---
Jim Derry
Clinton Township, MI, USA
Nanjing, Jiangsu, China PRC