Shtml removal #1234
Open
Shtml removal #1234
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
horazont
reviewed
Nov 8, 2022
xep-0019.xml
Outdated
| @@ -19,6 +19,12 @@ | |||
| <supersededby/> | |||
| <shortname>N/A</shortname> | |||
| &stpeter; | |||
| <revision> | |||
| <version>1.1</version> | |||
There was a problem hiding this comment.
Why did you create a revision block for this XEP only? And why did you use a minor level bump instead of a patch level bump?
Ppjet6
force-pushed
the
shtml-removal
branch
from
8eb047a
to
7afa008
Compare
linkmauve
reviewed
Dec 14, 2022
xep-0019.xml
Outdated
| @@ -72,6 +78,6 @@ | |||
| <li>Continue to use the Standards SIG as the preferred forum for discussion of experimental specifications before they are submitted to the XMPP Council.</li> | |||
| <li>If the Standards SIG cannot reach a working consensus on a given topic, let the document author(s) continue to rework their proposal informally outside the context of the Standards SIG. <note>One option would be to send interested parties off to their own ad-hoc mailing list (e.g., on JabberStudio, <link url="http://www.jabberstudio.org/">http://www.jabberstudio.org/</link>). Unlike the current SIGs, such a list would be established on the initiative of the document author(s) and would not require any formal approval by the XMPP Council.</note></li> | |||
| </ol> | |||
| <p>There may be value in bringing back specialized SIGs in the future when the Jabber/XMPP community becomes larger. However, at this time I urge that we face the facts and proactively implement the solution I have outlined in this document. <note>Lest there be any concern that disbanding the SIGs is outside the power or purview of the XMPP Council, I note that Section 8.2 of the Bylaws of the XMPP Standards Foundation states in part that "The XMPP Council or the Members of the Corporation may, by resolution, ... terminate a Special Interest Group at any time for any reason." (An electronic copy of the Bylaws may be found at <link url="http://xmpp.org/xsf/docs/bylaws.shtml">http://www.jabber.org/bylaws.html</link>.)</note></p> | |||
| <p>There may be value in bringing back specialized SIGs in the future when the Jabber/XMPP community becomes larger. However, at this time I urge that we face the facts and proactively implement the solution I have outlined in this document. <note>Lest there be any concern that disbanding the SIGs is outside the power or purview of the XMPP Council, I note that Section 8.2 of the Bylaws of the XMPP Standards Foundation states in part that "The XMPP Council or the Members of the Corporation may, by resolution, ... terminate a Special Interest Group at any time for any reason." (An electronic copy of the Bylaws may be found at <link url="https://xmpp.org/about/xsf/bylaws/">http://www.jabber.org/bylaws.html</link>.)</note></p> | |||
There was a problem hiding this comment.
The link and its text are still not synchronised here, in addition the jabber.org text points to a 404.
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
|
What is the right thing to do here? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I replaced a few shtml links with their corresponding page. I've split what I could in various commits as I wasn't sure what would be needed and/or if everything was going to pass as is. Feel free to squash parts or all of it.