-
Notifications
You must be signed in to change notification settings - Fork 122
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
Feature request: quick xep remarks #774
Comments
We have trouble getting enough people to build and maintain even basic tooling; a big project on this scale (and make no mistake, this is a big project) is probably outside the scope of what the XSF should be spending its time on. |
then use something 3rdparty. |
The XMPP wiki has a section on XEP errata: XEP and RFC Remarks. I suggest we keep using that. We might ask the community whether it makes sense to link to the wiki pages from the XEP pages themselves (that would require some wiki page renaming, but that should be doable). |
Well it's almost impossible to find the link above or figure out it exists. So yes it definitely has to be linked to XEP pages. |
While XEP web pages look good it becomes quite a procedure to fix any inaccuracies (fix xep source code, make PR, wait for feedback, update PR.... eventually it's merged).
But most of the time a regular developer doesn't want to do all of this. Instead usually there is just a desire to point out for responsible people it's something wrong in this exact part of XEP text. And maybe even start some discussion. Mail list could be good for this but again it requires some extra actions like quoting parts of XEP in the email, wait for feedback, ping people on XSF chat to pay attention to the problem, ensure it's overlooked etc..
That would be much easier if a developer or whoever could just click on some part of XEP right in web interface and put his notes there, starting a discussion thread right in place. And of course such remarks have to be visible for all "registered" users. It's like in Google Docs you can mark a part of text in a shared document and comment on it.
Eventually such threads can be resolved and hidden. Maybe a thread starter will be involved in a PR creation or reviewers will do that on their own, it doesn't matter in this case.
The text was updated successfully, but these errors were encountered: