You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by lapstjup October 3, 2021
Hi @Progyan1997 , I was going through the CONTRIBUTING.md for this project and found subtle grammatical nuances that I think can be corrected. Also the README link in the same redirects to 404 Page. Since the guidelines state that an issue shouldn't be opened up by a user until a maintainer picks it from discussions and these kind of changes don't fall under bug report, can I proceed with creating an issue and submitting a PR that addresses it ?
BTW, this is a really cool project 💯 . I haven't really worked in the same space so the code is new but interesting. I think a diagrammatic workflow would be good addition to README as well so that new comers can familiarize themselves quickly with terminologies like "Operational Transformation", "Editor Adapters" and "Database Adapters".
Out of Scope: Diagrams and further analysis.
The text was updated successfully, but these errors were encountered:
The CONTRIBUTING markdown file is updated with correct link(s) to relevant files and linguistic corrections.
Fixes: 0xTheProDev#64
Signed-off-by: Lakshya Thakur lapstjup@gmail.com
The CONTRIBUTING markdown file is updated with correct link(s) to relevant files and linguistic corrections.
Fixes: #64
Signed-off-by: Lakshya Thakur lapstjup@gmail.com
Repository owner
locked as resolved and limited conversation to collaborators
Oct 3, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Discussed in #63
Originally posted by lapstjup October 3, 2021
Hi @Progyan1997 , I was going through the CONTRIBUTING.md for this project and found subtle grammatical nuances that I think can be corrected. Also the README link in the same redirects to 404 Page. Since the guidelines state that an issue shouldn't be opened up by a user until a maintainer picks it from discussions and these kind of changes don't fall under bug report, can I proceed with creating an issue and submitting a PR that addresses it ?
BTW, this is a really cool project 💯 . I haven't really worked in the same space so the code is new but interesting. I think a diagrammatic workflow would be good addition to README as well so that new comers can familiarize themselves quickly with terminologies like "Operational Transformation", "Editor Adapters" and "Database Adapters".
Out of Scope: Diagrams and further analysis.
The text was updated successfully, but these errors were encountered: