What is rationale for proposing Forms Task Force in HCG?

I didn't get a clear idea from the minutes what is the rationale for 
considering the HCG as the 'home' of the forms task force.

By our charter, there is supposed to be a forms task force that is 
comprised of members of the *Forms WG*, not the HCG.
By the HTML charter, there is supposed to be a forms task force that is 
comprised of members of the *HTML WG*, not the HCG.

That both charters mention this obligation and both refer to it as a 
'joint' task force, it seems clear where the task force belongs... and 
where it doesn't.

It is unclear how anything is gained by moving it to the HCG.  One problem 
is that the HCG is member-only, whereas the Forms WG is public, and the 
HTML WG is something beyond public.  So it will be quite hard, I think, to 
home the joint forms task force in the HCG.

At some level, it makes sense that this is a coordination act, so it 
should be handled by a group with a 'coordination' label, but the current 
state of what a CG can do in the W3C is fairly limited, which is how, I 
think, the language about this task force has ended up in the charters of 
the actual working groups.

It would be good to hear the strategic benefits that might arise from a 
move to the HCG.

Cheers,
John