Re-opening Islandora Issue Queues in Github

[Kirsta Stapelfeldt]

Apologies for cross-posting.

 

Dear Islandora,

 

As part of the upcoming Islandora sprint (November 29^th – December 15) we are planning to re-open the repository-specific issue queues in Github. This means that issues will be moved from their current centralized home in the Islandora Documentation repository and back to individual Github repositories. This change was discussed in last week’s open tech call.

 

Why are you making this change?

• We have received feedback that the current consolidation of issues in a single github repository queue creates challenges for newcomers to the community in understanding our issues approach, and challenges for repository maintainers to understand the issues that are relevant to a specific repository.
• The technology of Github has improved so that we no longer need to report all issues in one queue to get a global sense of issues.

 

How will I get an overview of all the issues currently reported in Islandora?

• Github’s project features are increasingly robust, and will be used to aggregate the issues in Islandora to provide a variety of views on existing issues.

 

Where do I put an issue when I’m not sure where it should go, or when it touches multiple repositories?

• Please put issues like this in the documentation queue, like always. These will be moved to the relevant repository, or broken down into issues for specific repositories (hopefully increasing the ability to work on these types of issues)

 

When will this work take place?

• We are planning on implementing this change during the next Islandora sprint (November 29-December 15). Please let us know if you can think of a reason this isn’t a good idea: through the Google email list, by coming to an open tech meeting, or by directly emailing comm...@islandora.ca.

 

Thanks for any feedback, and we will communicate further details during the sprint.

 

Best,

 

Kirsta (as part of the sprint planning group)