Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / samvera-labs/hydra_plugins_wg issues and pull requests

#88 - Updated README

Pull Request - State: open - Opened by kelynch over 3 years ago

#86 - RENAME: Update CONTRIBUTING.md to match the maintenance template

Issue - State: closed - Opened by kelynch over 3 years ago - 1 comment

#85 - RENAME: Add language to README about branch naming

Issue - State: open - Opened by kelynch over 3 years ago

#83 - Rename master branch to main

Issue - State: closed - Opened by kelynch over 3 years ago - 1 comment

#82 - Changes 'Hydra' to 'Hyrax'

Pull Request - State: closed - Opened by afred over 6 years ago

#81 - Change references of "Hydra" to "Hyrax"

Issue - State: closed - Opened by afred over 6 years ago

#80 - Define plugin

Pull Request - State: closed - Opened by afred over 6 years ago

#79 - Do not violate open/closed principle

Pull Request - State: closed - Opened by afred over 6 years ago

#78 - Revert "Do not violate open/closed principle"

Pull Request - State: closed - Opened by afred over 6 years ago

#77 - Do not violate open/closed principle

Pull Request - State: closed - Opened by afred over 6 years ago

#76 - Add initial final report

Issue - State: open - Opened by afred over 7 years ago

#75 - Fix guidelines justification formatting

Pull Request - State: closed - Opened by eliotjordan over 7 years ago

#74 - Add allignment

Pull Request - State: closed - Opened by carolyncole over 7 years ago - 1 comment

#73 - Removes guideline to abort install

Pull Request - State: closed - Opened by afred over 7 years ago - 1 comment

#72 - Add a YARD doc for private classes which aren't meant to be used externally.

Issue - State: open - Opened by tpendragon over 7 years ago - 3 comments

#70 - Add examples to points

Issue - State: open - Opened by tpendragon over 7 years ago

#69 - Create an example for Architecture issue 7.

Issue - State: open - Opened by tpendragon over 7 years ago

#67 - Update Guidelines.md

Pull Request - State: closed - Opened by jenlindner over 7 years ago - 1 comment

#65 - Guidelines should have a definition for plugin.

Issue - State: closed - Opened by jcoyne over 7 years ago - 1 comment

#64 - Minor corrections to guidelines

Pull Request - State: closed - Opened by danhorst over 7 years ago - 1 comment

#63 - Adds justification for using generators

Pull Request - State: closed - Opened by afred over 7 years ago - 3 comments

#62 - Adds justification for notifying of host app changes

Pull Request - State: closed - Opened by afred over 7 years ago - 3 comments

#61 - Adds justifcation for documenting install options

Pull Request - State: closed - Opened by afred over 7 years ago - 2 comments

#60 - Adds justification for screenshots

Pull Request - State: closed - Opened by afred over 7 years ago

#59 - adds justification for custom error classes

Pull Request - State: closed - Opened by starsplatter over 7 years ago

#58 - adds justification for error recovery tips

Pull Request - State: closed - Opened by starsplatter over 7 years ago

#57 - add justification for interface documentation

Pull Request - State: closed - Opened by starsplatter over 7 years ago

#56 - Add Generated Code Guideline & justification

Pull Request - State: closed - Opened by mbarnett over 7 years ago - 1 comment

#55 - Adds undo any changes made during a failed installation justification

Pull Request - State: closed - Opened by mbarnett over 7 years ago

#54 - Adds abort installation if required dependencies are missing justification

Pull Request - State: closed - Opened by mbarnett over 7 years ago - 7 comments

#53 - Adds meaningful error messages justification

Pull Request - State: closed - Opened by mbarnett over 7 years ago

#52 - Adds justification for YARD api tags

Pull Request - State: closed - Opened by eliotjordan over 7 years ago

#51 - Adds justification for tutorial guideline

Pull Request - State: closed - Opened by eliotjordan over 7 years ago - 2 comments

#48 - Add justification for "A plugin's interface must be documented."

Issue - State: closed - Opened by afred over 7 years ago
Labels: Guidelines

#40 - Add justification for "Plugins should abort installation if required dependencies are missing."

Issue - State: closed - Opened by afred over 7 years ago - 1 comment
Labels: Guidelines

#36 - Add justification for "Plugins should follow established Hydra coding conventions..."

Issue - State: open - Opened by afred over 7 years ago
Labels: Guidelines

#35 - Add justification for "Plugins should use semantic versioning."

Issue - State: open - Opened by afred over 7 years ago
Labels: Guidelines

#34 - Add justification for "Plugins must have a unique namespace ... "

Issue - State: open - Opened by afred over 7 years ago
Labels: Guidelines

#33 - Add justification for "Plugins should be Railties or Rails engines."

Issue - State: closed - Opened by afred over 7 years ago - 1 comment
Labels: Guidelines

#32 - Add justification for "Plugins must be Ruby gems."

Issue - State: closed - Opened by afred over 7 years ago - 1 comment
Labels: Guidelines

#31 - Plugins should not monkey patch classes from other gems

Issue - State: closed - Opened by afred over 7 years ago - 8 comments
Labels: Guidelines

#30 - How to monkey patch

Issue - State: closed - Opened by afred over 7 years ago - 5 comments
Labels: Guidelines

#29 - Plugins should only generate code into the host app when necessary

Issue - State: closed - Opened by afred almost 8 years ago - 4 comments
Labels: Guidelines

#28 - Generated code counts as the public interface

Issue - State: closed - Opened by afred almost 8 years ago - 2 comments
Labels: Guidelines

#27 - Plugins should not overwrite classes or modules.

Pull Request - State: closed - Opened by afred almost 8 years ago - 2 comments

#26 - Plugins must be defined under a specific namespace

Issue - State: closed - Opened by afred almost 8 years ago - 6 comments
Labels: Guidelines

#25 - Adds *must* use routing proxy to guidelines

Pull Request - State: closed - Opened by afred almost 8 years ago - 10 comments
Labels: Guidelines, PR needs modifications

#24 - Add guidlines for using YARD and @api tags

Pull Request - State: closed - Opened by afred almost 8 years ago - 1 comment

#23 - Named route helpers should be explicit in which route set is being used

Issue - State: closed - Opened by afred almost 8 years ago - 9 comments
Labels: Guidelines

#22 - Will plugins be more specific than a Rails Engine or Railtie?

Issue - State: closed - Opened by grosscol almost 8 years ago - 2 comments

#21 - Plugins should use YARD with @api tags.

Issue - State: closed - Opened by afred almost 8 years ago - 2 comments
Labels: Guidelines

#20 - Remove contingency language from 'should' statements

Pull Request - State: closed - Opened by afred almost 8 years ago - 1 comment

#19 - Installing a plugin should not overwrite classes or modules in the host application.

Issue - State: closed - Opened by afred almost 8 years ago - 13 comments
Labels: Guidelines

#18 - Adds link to Duraspace wiki page.

Pull Request - State: closed - Opened by afred almost 8 years ago - 1 comment

#17 - Create initial Guidelines

Issue - State: closed - Opened by afred almost 8 years ago
Labels: Guidelines

#16 - Initial Guidelines

Pull Request - State: closed - Opened by afred almost 8 years ago - 9 comments

#15 - Updating dates to 2017

Pull Request - State: closed - Opened by jeremyf almost 8 years ago

#14 - Create repo for Google Analytics Hydra plugin

Issue - State: closed - Opened by afred almost 8 years ago - 11 comments

#13 - Create branch in GeoConcerns for turning into a Hydra Plugin

Issue - State: closed - Opened by afred almost 8 years ago - 2 comments

#12 - Should "Social Media Features" be be one of our proofs-of-concept projects?

Issue - State: closed - Opened by afred almost 8 years ago - 1 comment
Labels: Proof Of Concept

#11 - Should Questioning Authority be a proof-of-concept project?

Issue - State: closed - Opened by afred almost 8 years ago - 1 comment
Labels: Proof Of Concept

#10 - Initial users stories

Pull Request - State: closed - Opened by afred almost 8 years ago - 1 comment

#9 - Should BrowseEverything be one of our proof-of-concept projects?

Issue - State: closed - Opened by carolyncole almost 8 years ago - 1 comment
Labels: Proof Of Concept

#8 - Should Google Analytics be be one of our proofs-of-concept projects?

Issue - State: closed - Opened by carolyncole almost 8 years ago - 1 comment
Labels: Proof Of Concept

#7 - Should GeoConcerns be one of our proofs-of-concept projects?

Issue - State: closed - Opened by eliotjordan almost 8 years ago - 6 comments
Labels: Proof Of Concept

#6 - Installing and configuring a plugin is predictable and straightforward.

Issue - State: closed - Opened by carolyncole almost 8 years ago - 2 comments
Labels: User Story

#5 - The interfaces and conventions for plugins are well documented for the developer.

Issue - State: closed - Opened by carolyncole almost 8 years ago
Labels: User Story

#4 - The community expectations of plugins are well documented for the developer.

Issue - State: closed - Opened by carolyncole almost 8 years ago
Labels: User Story

#3 - The software expectations of plugins are well-documented for the developer.

Issue - State: closed - Opened by carolyncole almost 8 years ago - 3 comments
Labels: User Story

#2 - User Stories Vocabulary

Issue - State: closed - Opened by carolyncole almost 8 years ago - 4 comments
Labels: User Story

#1 - Adds a roadmap

Pull Request - State: closed - Opened by afred almost 8 years ago