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

doc: make template more concise, add ref to CONTRIBUTING.md on template #357

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

luisschwab
Copy link
Contributor

@luisschwab luisschwab commented Jan 28, 2025

What is the purpose of this pull request?

  • Bug fix
  • New feature
  • Documentation update
  • Test
  • Other:

Description

Made the PR template cleaner: the description section should be enough (Which aspect of floresta its being addresed? is redundant).

Added CONTRIBUTING.md to checklist section

Fixed typos on CONTIBUTING.md

Checklist

  • I've signed all my commits
  • I ran just lint
  • I ran cargo test
  • I've checked the integration tests
  • I've followed the contribution guidelines
  • I'm linking the issue being fixed by this PR (if any)

PS: this PR is using the new template

@luisschwab luisschwab force-pushed the doc/nits-on-pr-issue-template branch from 5e607f2 to 12896a2 Compare January 28, 2025 01:53
@jaoleal
Copy link
Contributor

jaoleal commented Jan 28, 2025

Nack.

The positional changes just makes worse to make a superficial read of the PR.

Which aspect of floresta its being addresed? is redundant

No, its not... This project has more code than quantity of people reviewing it and the section "Which aspect of floresta its being addresed?" lets you know the complications of the code being added and how dangerous the codebase of that specified module is... If none of the other sections gives this information without the need of reading the code, its not redundant.

the description section should be enough

Description is an open text field and the understanding, of the contributor, about whats being addressed can differ depending on how familiar the contributor is with the codebase... Also, most contributors, as you can see from the contribution history, are not native English speakers and this can lead to difficulties in writing and understanding for both contributor and reviewer.

So, check boxes makes life easier for everyone.

@luisschwab
Copy link
Contributor Author

Description is an open text field and the understanding, of the contributor, about whats being addressed can differ depending on how familiar the contributor is with the codebase...

Do you mean from the reviewer perspective? Because if not, I think that if someone makes a PR they should be able to explain their work.

most contributors, as you can see from the contribution history, are not native English speakers

Google translate is more than enough for this.

@Davidson-Souza
Copy link
Collaborator

Davidson-Souza commented Jan 31, 2025

I think there are some nice changes here. Could you bring this section back and not remove the sample title from issues?

@luisschwab luisschwab force-pushed the doc/nits-on-pr-issue-template branch from 12896a2 to f0c8fe3 Compare January 31, 2025 19:51
@luisschwab
Copy link
Contributor Author

@Davidson-Souza do you mean the "Which aspect of floresta its being addresed?" section?

@Davidson-Souza
Copy link
Collaborator

@Davidson-Souza do you mean the "Which aspect of floresta its being addresed?" section?

Yes

@luisschwab luisschwab force-pushed the doc/nits-on-pr-issue-template branch from f0c8fe3 to 2c7783b Compare January 31, 2025 21:12
@luisschwab
Copy link
Contributor Author

Done. I added the individual crate names:

+### Which crates are being modified?
+
+- [ ] floresta-chain
+- [ ] floresta-cli
+- [ ] floresta-common
+- [ ] floresta-compact-filters
+- [ ] floresta-electrum
+- [ ] floresta-watch-only
+- [ ] floresta-wire
+- [ ] floresta
+- [ ] Other: <!-- Please describe it -->.

@jaoleal
Copy link
Contributor

jaoleal commented Feb 1, 2025

Do you mean from the reviewer perspective? Because if not, I think that if someone makes a PR they should be able to explain their work.

Its totally possible to contribute without knowing all the project in details, isnt it ?

I understand, the point is to make the template more concise but, few lines with check boxes will not hurt anyone and will help reviewers to provide better and faster reviews.

Done. I added the individual crate names:

Nice but, "Which aspect of floresta its being addresed?" is not about the crates and yes about the functionality being changed... Still a working in progress to separate things in their proper crates here.

Also, I see a way to make it more concise to complement the objective of this PR.

What you think about:

+ ### Which aspect of LibFloresta its being addresed?

+ - [ ] Blockchain;  <!--  Block validation and management. -->
+ - [ ] Wire;  <!--  Communication and control over other nodes. -->
+ - [ ] I/O or Database  <!--  Control over the data flow for the OS. -->
+ - [ ] Other: <!-- Please describe it -->.

Smaller but still expressive.

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

Successfully merging this pull request may close these issues.

3 participants