Closed weiji14 closed 3 years ago
The downside of keeping BUILDING.md and MAINTENANCE.md separate is that there will need to be more redundancy to make setup easier for new developers. But, I think it is necessary to keep them separate because the GMT website links to BUILDING.md for instructions on how to build from source and there are likely many people who want to build from source without needing debugging flags, testing instructions, etc.
Might it be an option to add a DEVELOPER.md that links to the two others but helps in describing the overall workflow?
Might it be an option to add a DEVELOPER.md that links to the two others but helps in describing the overall workflow?
Rather than adding a new document, we could add a 'setting up your environment' section (similar to PyGMT's section in their contributing guide) and a more complete description of the overall workflow to CONTRIBUTING.md.
Related issue: #364
Description of the desired feature
The steps to build and run tests in GMT to produce new postscript (*.ps) files is not very intuitive for first timers. In particular, it's a little confusing having to jump between the BUILDING.md and MAINTENANCE.md documents.
Originally posted by @meghanrjones in https://github.com/GenericMappingTools/gmt/issues/4838#issuecomment-783445471
See also https://github.com/GenericMappingTools/gmt/pull/4838#issuecomment-782954781 and https://github.com/GenericMappingTools/gmt/pull/4838#issuecomment-782964119
Suggested changes:
admin/bashrc_for_gmt
(https://github.com/GenericMappingTools/gmt/blob/master/admin/bashrc_for_gmt) (added in #4529) in MAINTENANCE.md, and briefly mention how to use themAre you willing to help implement and maintain this feature? Happy to review the Pull Request!