Re: [w3c/manifest] BREAKING CHANGE: remove beforeinstallprompt event (#836)

With my WebApps WG Chair hat on, the [charter](https://www.w3.org/2019/05/webapps-charter.html#working-mode) we all agreed to operate under states that:

> Additionally, support from two or more web platform implementers is required before a substantive change can be made to a specification. 

The above was explicitly put into the charter to prevent single implementer features being added into WebAppsWG specifications. I understand that we are in a very difficult situation, in that we added this feature with the hope that it would be adopted by multiple user agents. In hindsight, it was a mistake to do that - and this was added under the old charter, in which we allowed "aspirational features" to be added to the spec in the hope that other implementers would follow what was in the spec. But despite years and multiple implementations (Gecko + WebKit), BIP was not adopted. 

Additionally, the W3C Process requires us that things in a specifications have multiple implementations or otherwise will be removed before the specification enters the Proposed Recommendation phase - i.e., this will be "at risk". 

Even without any malice intended, and will only the best intentions, making this as a feature optional circumvents the W3C Process would set a bad precedence for the reasons @rniwa and myself have already outlined.  

Thus, we have the following W3C Process options: 

 1. A Working Group member can Formally Object - in which case, we will can escalate to the Director to weigh the evidence/proposal and make a decision to break the deadlock.
 1. We ask dissenting voices to concur, and respect the spirit of the Charter - and find a different place to put BIP (e.g., move it to the WICG for now).



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/pull/836#issuecomment-597935593