issues
search
samvera-labs
/
hydra_plugins_wg
Work area for the Hydra Plugins Working Group
Apache License 2.0
1
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Updated README
#88
kelynch
opened
3 years ago
0
RENAME: Update references of hard-coded legacy master branch name to main branch name
#87
kelynch
opened
3 years ago
0
RENAME: Update CONTRIBUTING.md to match the maintenance template
#86
kelynch
closed
3 years ago
1
RENAME: Add language to README about branch naming
#85
kelynch
opened
3 years ago
0
RENAME: Recommendation for branch name testing - add CircleCI or update documentation
#84
kelynch
opened
3 years ago
0
Rename master branch to main
#83
kelynch
closed
3 years ago
1
Changes 'Hydra' to 'Hyrax'
#82
afred
closed
6 years ago
0
Change references of "Hydra" to "Hyrax"
#81
afred
closed
6 years ago
0
Define plugin
#80
afred
closed
6 years ago
0
Do not violate open/closed principle
#79
afred
closed
6 years ago
0
Revert "Do not violate open/closed principle"
#78
afred
closed
6 years ago
0
Do not violate open/closed principle
#77
afred
closed
6 years ago
0
Add initial final report
#76
afred
opened
7 years ago
0
Fix guidelines justification formatting
#75
eliotjordan
closed
7 years ago
0
Add allignment
#74
carolyncole
closed
7 years ago
1
Removes guideline to abort install
#73
afred
closed
7 years ago
1
Add a YARD doc for private classes which aren't meant to be used externally.
#72
tpendragon
opened
7 years ago
3
Remove point about aborting installation for unmet dependencies
#71
tpendragon
closed
7 years ago
0
Add examples to points
#70
tpendragon
opened
7 years ago
0
Create an example for Architecture issue 7.
#69
tpendragon
opened
7 years ago
0
Clarify point 6 of Architecture to be about scoping of methods and the impact on semantic versioning.
#68
tpendragon
opened
7 years ago
0
Update Guidelines.md
#67
jenlindner
closed
6 years ago
1
Add rationale why you should create a plugin and follow these directions
#66
tpendragon
opened
7 years ago
0
Guidelines should have a definition for plugin.
#65
jcoyne
closed
6 years ago
1
Minor corrections to guidelines
#64
danhorst
closed
7 years ago
1
Adds justification for using generators
#63
afred
closed
6 years ago
3
Adds justification for notifying of host app changes
#62
afred
closed
6 years ago
3
Adds justifcation for documenting install options
#61
afred
closed
6 years ago
2
Adds justification for screenshots
#60
afred
closed
7 years ago
0
adds justification for custom error classes
#59
starsplatter
closed
7 years ago
0
adds justification for error recovery tips
#58
starsplatter
closed
7 years ago
0
add justification for interface documentation
#57
starsplatter
closed
7 years ago
0
Add Generated Code Guideline & justification
#56
mbarnett
closed
7 years ago
1
Adds undo any changes made during a failed installation justification
#55
mbarnett
closed
7 years ago
0
Adds abort installation if required dependencies are missing justification
#54
mbarnett
closed
7 years ago
7
Adds meaningful error messages justification
#53
mbarnett
closed
7 years ago
0
Adds justification for YARD api tags
#52
eliotjordan
closed
7 years ago
0
Adds justification for tutorial guideline
#51
eliotjordan
closed
7 years ago
2
Add Justification for "Plugin documentation should include a tutorial on how to use each feature the plugin offers."
#50
afred
closed
7 years ago
0
Add justification for "Public instance methods, class methods, and module methods that are part of the plugin's interface must be documented with YARD, using @api tags to indicate which methods are part of the plugin's interface."
#49
afred
closed
7 years ago
0
Add justification for "A plugin's interface must be documented."
#48
afred
closed
7 years ago
0
Add Justification for "Custom error messages should include tips on how to fix the error when such information is known."
#47
afred
closed
7 years ago
0
Add justification for "Plugins should use custom error classes when raising errors"
#46
afred
closed
7 years ago
0
Add justification for "Plugin installation instructions should include screen shots of any expected changes to the UI."
#45
afred
closed
7 years ago
0
Add justification for "Installation documentation for plugins should include a list of all available installation options with a description of their effects."
#44
afred
closed
6 years ago
0
Add justification for "Plugins should not overwrite classes or modules in the host application."
#43
afred
closed
7 years ago
1
Add justification for "Plugins should provide information on any changes made to the host application that could not be undone after a failed installation."
#42
afred
closed
6 years ago
0
Add justification for "Plugins should undo any changes made to the host application during a failed installation."
#41
afred
closed
7 years ago
0
Add justification for "Plugins should abort installation if required dependencies are missing."
#40
afred
closed
7 years ago
1
Add justification for "Plugins should print meaningful error messages in case of a failure during installation."
#39
afred
closed
7 years ago
0
Next