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

Link to the Developer-Notes.md file in CONTRIBUTING.md #2260

Merged
merged 1 commit into from Sep 5, 2018

Conversation

PastaPastaPasta
Copy link
Member

No description provided.

Copy link
Collaborator

@thephez thephez left a comment

Choose a reason for hiding this comment

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

utACK

@nmarley
Copy link

nmarley commented Sep 4, 2018

This is already linked a few lines above -- search "The project coding conventions in the developer notes must be adhered to.".

Do we need to add the link twice? Or re-organize for clarity?

Seems like it might be a bit redundant (e.g. contributors should probably be expected to read this document in full anyway -- it's not really that long.)

@PastaPastaPasta
Copy link
Member Author

PastaPastaPasta commented Sep 4, 2018

Maybe I was just being oblivious, but when I was looking for it for the clean up pr I could not find it after reading over the doc twice. Can't hurt to add another reference to it imo. Potentially just changing the wording could help. For example I was scanning for 'style'

@thephez
Copy link
Collaborator

thephez commented Sep 4, 2018

IMO it is helpful to have the link at hand and not have to scroll back. The easier documentation is to use, the more likely it will be used. Just my 2 cents...

@nmarley
Copy link

nmarley commented Sep 4, 2018

I'm all for making it easier, but prefer not to have the redundancy. E.g. what if the location of the referenced doc changes? Then we'd have 2 places to update, instead of one.

We could re-word or re-organize the doc a bit though. I also would prefer not to make changes due to impatience, e.g. for those devs who are too impatient to look thru the docs or only do a quick search and can't find what they need. I think there's a balance between usability and just catering to impatience. E.g. we just maintain a single link, but can change the text to something like "The project code style conventions in the developer notes must be adhered to.".

If necessary we could also add a bullet here which references the above without adding a redundant link. But that seems to be catering to those just quick skimming w/o actually reading thru the doc.

Copy link

@UdjinM6 UdjinM6 left a comment

Choose a reason for hiding this comment

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

I think it's fine to have yet another link and making it easier to find. I wouldn't overthink this tbh :)

utACK

@UdjinM6 UdjinM6 added this to the 12.4 milestone Sep 4, 2018
@nmarley
Copy link

nmarley commented Sep 4, 2018

¯_(ツ)_/¯ 🙉 😄

@PastaPastaPasta
Copy link
Member Author

Oh no! You lost an arm! Here ya go: \

Copy link

@codablock codablock left a comment

Choose a reason for hiding this comment

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

utACK

@UdjinM6 UdjinM6 merged commit b998865 into dashpay:develop Sep 5, 2018
@PastaPastaPasta PastaPastaPasta deleted the Add-devnotes-contrib branch September 15, 2018 02:09
CryptoCentric pushed a commit to absolute-community/absolute that referenced this pull request May 20, 2019
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.

None yet

5 participants