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

[Improvement] Add projects description, problems and expected outcome in README.md documentation #161

Open
1 task done
FrancoFrancis opened this issue Nov 1, 2022 · 9 comments
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧹 status: ticket work required Needs more details before it can be worked on 💬 talk: discussion Open for discussions and feedback

Comments

@FrancoFrancis
Copy link
Contributor

FrancoFrancis commented Nov 1, 2022

Problem

There is only documentation about setting up the project in the Projects README, although that may not neccessarily be a problem. We can work on ways to improve the README

Description

By adding a detailed description of the project, the problems associated with the project and the expected outcome just as on the outreachy website I believe the project will be more complete. if this issue is approved Would like to work with a mentor to add additional description if needed.

Additional context

Implementing this would make it that just by reading the README.md documentation you would be able to understsand the details and complete direction of the project.

Implementation

  • I would be interested in implementing this feature.
@FrancoFrancis FrancoFrancis added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Nov 1, 2022
@FrancoFrancis
Copy link
Contributor Author

hi @sara kindly check if this issue is to be worked on. thanks :)

@TimidRobot TimidRobot changed the title [Improvement] <Add projects description, problems and expected outcome in README documentation> [Improvement] Add projects description, problems and expected outcome in README documentation Nov 3, 2022
@possumbilities
Copy link
Contributor

@FrancoFrancis I'd be interested to see what suggestions anyone would have here on what should be appended to the README.md file to improve things.

@possumbilities possumbilities added 🧹 status: ticket work required Needs more details before it can be worked on 💬 talk: discussion Open for discussions and feedback and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Nov 4, 2022
@FrancoFrancis
Copy link
Contributor Author

FrancoFrancis commented Nov 4, 2022

@FrancoFrancis I'd be interested to see what suggestions anyone would have here on what should be appended to the README.md file to improve things.

Okay, Can I go on to the community to start an open discussion ? :)

@possumbilities
Copy link
Contributor

@FrancoFrancis You can direct them here to have the discussion so the record is on this Issue, but sure, please do! ❤️

@FrancoFrancis
Copy link
Contributor Author

@FrancoFrancis You can direct them here to have the discussion so the record is on this Issue, but sure, please do! ❤️

okay on it.

@dikehprosper
Copy link
Contributor

@possumbilities @FrancoFrancis.... I think the most important part is a documentation that talks about the functionality and what the project does in the README

@mbonamensa
Copy link
Contributor

@FrancoFrancis correct me if I'm wrong. Do you mean the readme of the project should include problems that are expected to be resolved within the project? For example "We're looking to refactor the code base, etc" Something like that?

@FrancoFrancis
Copy link
Contributor Author

FrancoFrancis commented Nov 5, 2022

@FrancoFrancis correct me if I'm wrong. Do you mean the readme of the project should include problems that are expected to be resolved within the project? For example "We're looking to refactor the code base, etc" Something like that?

Yes.... the issue is open for discussion on what should be appended to the README.md to make it as informative as possible this is to make sure getting started as a user or as a developer/contributor is as easy as possible and also to reduce noice, because it is the one of the most important parts of any Github project.

@FrancoFrancis FrancoFrancis changed the title [Improvement] Add projects description, problems and expected outcome in README documentation [Improvement] Add projects description, problems and expected outcome in README.md documentation Nov 5, 2022
@FrancoFrancis
Copy link
Contributor Author

Hi @possumbilities can I proceed to working on this issue while its still open for discursion?

@TimidRobot TimidRobot moved this to Triage in WebDev Sep 10, 2024
@possumbilities possumbilities moved this from Triage to Backlog in WebDev Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature 🟩 priority: low Low priority and doesn't need to be rushed 🧹 status: ticket work required Needs more details before it can be worked on 💬 talk: discussion Open for discussions and feedback
Projects
Status: Backlog
Development

No branches or pull requests

4 participants