Add an extension author checklist#927
Open
Kkkakania wants to merge 1 commit into
Open
Conversation
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.
Summary
This PR adds a short developer page for people preparing an externally maintained FieldTrip extension. It explains when an extension may be a better fit than a direct core contribution, what a useful extension repository should contain, and what information to include when requesting a listing on the website.
It also links the new page from the existing Extensions and Contribute pages.
Context
This follows the direction discussed in fieldtrip/fieldtrip#2578: keeping self-contained external functionality discoverable, while making maintenance responsibility clear.
Validation
git diff --checkpyspelling/aspelland the Jekyll bundle are not installed in this environment.