WICG/speech-api

Transfer to WICG

marcoscaceres opened this issue · 19 comments

@siusin could you please transfer this repository for us to the WICG based on:
https://lists.w3.org/Archives/Public/public-speech-api/2019Oct/0001.html

I'll send a PR the w3c.github.io repo so links don't break.

@marcoscaceres Have been active in this repository before attempting to contribute to repositories under the WICG umbrella. Your decision to indefinitely ban this user from WICG umbrella repositories will certainly affect this proposed change. Your imposed ban from WICG should not be retroactively applied to this account should speech-api be moved to WICG. Meaning, should still be able to contribute to this repository in spite of your imposed indeterminate WICG ban.

If you agree to play by the rules, then I don’t see any reason not to lift the ban. You will need to join the WICG, abide by our code of conduct, and make the prerequisite IPR commitments tho.

@marcoscaceres As long as your parent organization fixes its current deliberate obfuscation practice re what they are actually asking for, can sign up to become a "member". Again, using the term "IPR" when the acronynm is not defined anywhere in W3C policy documents - even after being told exactly what to change the unknown term "IPR" after asking for the guidance cannot currently be described as anything other than deliberate deception.

I think it’s fair to know what you are signing. If I put you in touch with a W3C lawyer, would the help?

The lawyer already told the individual in charge of the repository what to do. There is no need for behind closed-door contact. Either individuals are being lazy re all of the documents that would need to be changed (let it be, hiding in plain sight) or intentionally deceiving people. The change is not only for this user, but for transparency, to avoid the issues at SE (https://judaism.meta.stackexchange.com/questions/5193/stack-overflow-inc-sinat-chinam-and-the-goat-for-azazel; https://meta.stackoverflow.com/a/389908) that warned the Mod Squad over there about each time they banned this user. Now they perhaps understand. Invested over 4 years into litigating in federal ct. over a single word (statutory construction). Cannot simply ignore the glaring issue of an organization that knows better using an acronym that currently has absolutely no citable defintion.

Again, own a trademark and filed for a patent. So have been through the intellectual property process entirely, from concept to post-examination. An undefined acronym in a patent application will not be missed by any examiner.

ok, but have you stopped to reflect that somehow Google, Apple, Microsoft, Mozilla, and countless other companies’ lawyers were ok to sign this agreement yet somehow you’ve found some profound conspiratorial deception with it? 🧐

Anyway, ball is in your court. You are clearly capable, smart, and articulate so hopefully you will reconsider your position so you can continue to participate.

(Also the fact that you’ve filed for a patent is precisely the reason for you to sign the agreement)

I'd like to request that the move doesn't happen until we've allowed for some time to react to this internally at Google, while I expressed support on the list there are other stakeholders. Please give us a week or so.

@guest271314 you are getting very far off topic now and I'm going to delete some of your comments. Please take @marcoscaceres's advice and talk to a W3C lawyer if you have concerns about joining the WICG.

FWIW Found the relevant language in an W3C document. Filed PR for reference and clarity. Joined W3C. Joined WICG.

Ok, but it looks like you joined without providing a legal name? Is that the case?

@marcoscaceres Not sure what you mean? Found at least one W3C document which expliticly defined "IPR" internally. Created a valid W3C account. Created a valid WICG account ("joined").

Do we now need to parse what "legal name" means, and evaluate historical and contemporary examples of what a "legal name" is?

@guest271314 no, please do not go down another rabbit hole on this thread. Whatever the requirements for joining the WICG are, please work them out off-thread.

@marcoscaceres @foolip sure, please let us know when it's ready to be transferred
(Cc @sideshowbarker as he has the owner access to both GitHub orgs).

Thanks @siusin. We'll wait for @foolip to give us a 👍.

We've discussed internally now and don't have any objection to transferring this to the WICG.

We'll continue to keep an eye on the repo/spec going forward as well, and given the pull request template I have high confidence that changes which wouldn't work at all for Chromium would surface quickly.

done