Skip to content

Shtml removal#1234

Open
Ppjet6 wants to merge 3 commits intoxsf:masterfrom
Ppjet6:shtml-removal
Open

Shtml removal#1234
Ppjet6 wants to merge 3 commits intoxsf:masterfrom
Ppjet6:shtml-removal

Conversation

@Ppjet6
Copy link
Copy Markdown
Contributor

@Ppjet6 Ppjet6 commented Nov 3, 2022

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.

Comment thread xep-0019.xml Outdated
<shortname>N/A</shortname>
&stpeter;
<revision>
<version>1.1</version>
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

Comment thread xep-0019.xml Outdated
<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>
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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>
@Ppjet6
Copy link
Copy Markdown
Contributor Author

Ppjet6 commented Jan 11, 2023

It looks like a previous version of the PR had been merged, without the fix on versions.
4d763ee
56c6de9

This fixes versions and also Link Mauve's suggestion.

@Kev
Copy link
Copy Markdown
Member

Kev commented Feb 28, 2023

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants