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.

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

docs: updating the readme #65

Merged
merged 10 commits into from
Sep 16, 2021
Merged

docs: updating the readme #65

merged 10 commits into from
Sep 16, 2021

Conversation

Souvikns
Copy link
Member

@Souvikns Souvikns commented Sep 6, 2021

** Description**

As of now, the readme is very plain and it does not provide much help.

As a user, I would like to see the following things.

  • How to download the CLI
  • If CLI is currently under construction then what features does it currently supports.
  • What features does it aim to support
  • Documentation and usage examples of all the features currently supported.
  • Whom to reach out for any problems or doubt that I might have.

As an open-source contributor, I would like to see the following things.

  • How to setup developer environment
  • Where can I get closely involved with the project development process
  • Proper roadmap to understanding what issues or features are priority.
  • Whom to reach out for any problems or doubts that I might have.

@Souvikns Souvikns changed the title doc: updating the readme feat: updating the readme Sep 6, 2021
Copy link
Member

@derberg derberg left a comment

Choose a reason for hiding this comment

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

left few comments.

regarding contrib guide and CoC, please do not copy paste those. If you think we need file to be in the repo, them please have them but with simple into text and a link to original files from .github repo, can be a link with HTML a tag and target blank to trigger opening link in another tab

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@derberg
Copy link
Member

derberg commented Sep 8, 2021

@alequetzalli maybe you wanna have a look 😉

Copy link
Member

@quetzalliwrites quetzalliwrites left a comment

Choose a reason for hiding this comment

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

Hey @Souvikns ! 😀😀😀 Hope you are well! I went ahead and added writing suggestions to help you further improve our readMEs. Let me know if something doesn't make sense, I hope this is helpful 👯

CODE_OF_CONDUCT.md Outdated Show resolved Hide resolved
CODE_OF_CONDUCT.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@Souvikns
Copy link
Member Author

@derberg can you check once, I have made all the requested changes. Hade to change the CONTRIBUTING.md file after @alequetzalli reviewed it. Seeing asyncapi/community#65 I think it's better to reference that to copy the contents as it would make it easy to maintain the file in the future, so that's what I did taking inspiration from https://github.com/kyma-project/console/blob/master/CONTRIBUTING.md as suggested by @derberg

@derberg
Copy link
Member

derberg commented Sep 14, 2021

@alequetzalli I did not closely follow all suggestions you made to @Souvikns but definitely whatever suggestions were done to CONTRIBUTING and CODE_OF_CONDUCT files, should be ported to the same files in github and here and other repos we should just maintain links.

@Souvikns please remove CODE_OF_CONDUCT file. And sorry but CONTRIBUTION guide too 😓 . Why? because of this PR I got to my GitHub Action -> derberg/manage-files-in-multiple-repositories#22. Once I merge and release it, we will use it in AsyncAPI, so we will no longer only push with bot all global GitHub Action workflow files, but also the basic files like CONTRIBUTION guide or CODE_OF_CONDUCT 😄 so whatever you do now will be lost in few days because of killer bot 😄

Just leave the CODE_OF_CONDUCT and previous version of CONTRIBUTION file after fixes from Alejandra, and only in README under Contributing section write To contribute to this project, follow the rules from the general [contribution guide](CONTRIBUTING.md). In addition also follow below rules valid for this project only: <- and you paste below what you already have under CONTRIBUTION guide, about UX? makes sense? and yes, you link to CONTRIBUTION file that you will have there, and long term we can easily replace it with any new version we want. Does it make sense?

I hope you are not mad cause of the change in plans. It is fresh PR, something we thought to support too but waited for confirmation from other non-AsyncAPI related communities that it is actually valid thing to do with my GH action

@Souvikns
Copy link
Member Author

@Souvikns please remove CODE_OF_CONDUCT file.
Just leave the CODE_OF_CONDUCT and previous version of CONTRIBUTION file after fixes from Alejandra

@derberg so shall I delete the CODE_OF_CONDUCT file and CONTRIBUTING.md or revert it back to the changes @alequetzalli suggested a bit confused here.

@derberg
Copy link
Member

derberg commented Sep 15, 2021

@Souvikns sorry 😅 rever and then extend readme

@sonarcloud
Copy link

sonarcloud bot commented Sep 15, 2021

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@Souvikns
Copy link
Member Author

@derberg It is ready to be reviewed.

Copy link
Member

@derberg derberg left a comment

Choose a reason for hiding this comment

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

:shipit:

@derberg derberg changed the title feat: updating the readme docs: updating the readme Sep 16, 2021
@Souvikns Souvikns merged commit d79b98e into asyncapi:master Sep 16, 2021
Comment on lines +38 to +40
To run `@asyncapi/cli`, you'll need Node.js >=v10

Run this terminal command to check your Node.js version:
Copy link
Member

Choose a reason for hiding this comment

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

Maybe it was here, or maybe it was in another repo, but did I give you a hint to describe the requirements in table form, such as?

  • NodeJS >= v10

Was this removed during the review from Łukasz?

Overall good, I have only this question.

Copy link
Member Author

Choose a reason for hiding this comment

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

Maybe I missed it I will update it later, 👍🏻

@asyncapi-bot
Copy link
Contributor

🎉 This PR is included in version 0.6.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants