Skip to content
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.

Sign up for GitHub

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

Jump to bottom

XEP-0077: Release version 2.5 #1299

Closed
wants to merge 1 commit into from
Closed

XEP-0077: Release version 2.5 #1299

wants to merge 1 commit into from

Conversation

melvo
Copy link
Contributor

@melvo melvo commented Nov 25, 2023

Specify account creation via HTTP as non-exclusive alternative to XMPP

@melvo
XEP-0077: Release version 2.5
005c376 
Specify account creation via HTTP as non-exclusive alternative to XMPP
@Kev Kev added the Needs Council The affected XEP has the Council as Approving Body and it needs to decide on the change. label Dec 11, 2023
mar-v-in
mar-v-in reviewed Dec 12, 2023
View reviewed changes
xep-0077.xml
<example caption='Host Redirects Entity to Web Registration'><![CDATA[
<section1 topic='Alternative Registration Medium' anchor='alternative-registration-medium'>
<p>A given deployment MAY wish to provide an alternative medium (e.g., a website) for registration.</p>
<section2 topic='Web Registration' anchor='web-registration'>
Copy link
Contributor

@mar-v-in mar-v-in Dec 12, 2023 •
edited
Loading

Choose a reason for hiding this comment

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

This invalidates prior links to this subsection (https://xmpp.org/extensions/xep-0077.html#redirect). I propose we keep that URL as is (by keeping anchor='redirect'). But this is probably editorial and thus is on the editor to decide.

Copy link
Contributor Author

@melvo melvo Dec 25, 2023 •
edited
Loading

Choose a reason for hiding this comment

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

I thought about that as well when I changed the anchor but keeping it would result in a misleading URL. Is there any solution for aliases/redirections from old URLs to new ones even if they do not exactly match?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@Kev What should I do?

@iNPUTmice
Copy link
Contributor

Council has rejected this for the following reasons:

  • -1 from my side. The language is weird. The justification for the change is now in the xep. I don't like changing final xeps without prior discussion
  • I even have doubts about the usecase in general. That itself makes it rather unacceptable for me to do this change to something that's already Final. -1, but might change after discussion and wording change

@iNPUTmice iNPUTmice closed this Mar 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mar-v-in mar-v-in mar-v-in left review comments

Assignees
No one assigned
Labels
Needs Council The affected XEP has the Council as Approving Body and it needs to decide on the change.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@melvo @iNPUTmice @mar-v-in @Kev