Improve CONTRIBUTING.md for new contributors#505
Open
AKSrivastava28 wants to merge 1 commit intopysal:mainfrom
Open
Improve CONTRIBUTING.md for new contributors#505AKSrivastava28 wants to merge 1 commit intopysal:mainfrom
AKSrivastava28 wants to merge 1 commit intopysal:mainfrom
Conversation
gegen07
reviewed
Feb 22, 2026
Member
gegen07
left a comment
gegen07
left a comment
There was a problem hiding this comment.
Hi there, is it ready for review?
The file seems work in progress with only installation development details.
Member
|
@gegen07 I am bit hesitant in merging individual changes across the federation as it means each sub package will have its own guidelines, complicating federation-wise maintenance. I think we should think about how to standardise this. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR improves CONTRIBUTING.md by adding clearer guidance for:
This follows up on the discussion in issue #481.