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

Build & translation / Add all informations in the same guide. #83

Merged
merged 1 commit into from
Nov 26, 2019

Conversation

fxprunayre
Copy link
Member

Related to #82

@fxprunayre fxprunayre merged commit fc6b9e5 into develop Nov 26, 2019
@fxprunayre fxprunayre deleted the buildandtranslate branch January 22, 2020 07:58
@jodygarnett
Copy link
Contributor

This change (moving the instructions from README to manual) confused me and conflicts with plan in core-geonetwork to move developer instructions to README.md files

@fxprunayre
Copy link
Member Author

conflicts with plan in core-geonetwork to move developer instructions to README.md files

I was not aware of this plan but indeed :) but if you think it makes more sense to have the dev doc in README.md files, no objection to revert this.
The idea during the doc sprint last November (https://github.com/geonetwork/core-geonetwork/wiki/Documentation-codesprint-November-2019) was to try to remove redundant information in different places (with sometimes different information) to limit the number of places to maintain.

@jodygarnett
Copy link
Contributor

I am not PSC, just noticing when I went to update docs the different sections of the code are diverging in different ways. Can we coordinate on mailing list?

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.

2 participants