Link to extension and proposed file with requirements#65
Open
jfaurelacroix wants to merge 2 commits intoOpenRefine:masterfrom
Open
Link to extension and proposed file with requirements#65jfaurelacroix wants to merge 2 commits intoOpenRefine:masterfrom
jfaurelacroix wants to merge 2 commits intoOpenRefine:masterfrom
Conversation
Added a link to the guidelines instead of just skipping ahead to the writing guide
Added the requirements for General release in a separated file that could be automatically parsed in the future to ensure compliance.
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
1 participant
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.
The current version assumes that the contributor has read the playbook. I added a link to the playbook instead of only providing a link to the writing guide.
I'm also proposing a separate file for the general release requirements so we can eventually easily parse an existing file instead of scanning through the whole repository (in most cases). We could even add that to the playbook (i.e. Please ensure that your repository contains a file named GeneralRelease.md with the following information for your extension to be added to the OpenRefine extension directory)