-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove TR reference from MIX2 #49
Conversation
annevk: Can you please also review this small change? Thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we could simply replace mixed-content and not introduce mixed-content-2, especially with the new process coming soonish.
We would first want to transition mixed-content out of CR and on to Rec. After that, I think we could effectively replace it with document that uses the new process. |
Looking at the new process, that sounds good to me since MIX2 will obsolete MIX anyways. I'll bring this up in the next meeting. (also cc @mikewest as editor of MIX, in case they have objections).
With the (big) caveat that I might be misunderstanding the new process, wouldn't replacing MIX with MIX2 while MIX is at CR fall under https://www.w3.org/wiki/Process2020#Updating_Candidate_Recommendations ? (In either case, I'll go ahead and merge this for now, to remove the 404 link while we have a TR to link to). |
…ove TR reference from MIX2 SHA: af9e38a Reason: push, by @carlosjoan91 Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
I’m honestly not sure. I have to admit that — despite reading the documentation about it — I don’t yet understand the new process well enough myself to be able to say. I think with the old process, if we made substantive/normative changes to a spec while it was at CR, then we had to restart the CR process. Since the current Mixed Content CR was published before new process started, I don’t know whether that means we’d need start the CR process again if we folded the Mix2 changes into it. I’ve already suggested this be put on the agenda for the WebAppSec telcon this week — so if you’re able to attend that, it would be a good opportunity to discuss it.
That seems like a question to take to the working group to make. I think whatever ends up happening with this, it needs to be a working-group decision. So, the chairs would need to announce a CfC and all that. But I think the best place to start would be by having a synchronous discussion about it in real time together on the WebAppSec telcon this week. |
Yeah, I agree that discussing the way forward in the next meeting would be good. As I mentioned on the previous comment, I'm planning to bring this up there (and was planning to PR into the agenda once it was up, but I see it's already included now that it's up), so I am indeed planning to attend. |
As mentioned in #25, the "Last Published Version" link in MIX2 currently leads to a 404, since there is none (as MIX2 is still only an Editor's Draft). This removes the link, which we can re-add once MIX2 moves to FPWD and there is a published version to point to.