search

pdurbin / druthers

crowdsourced issue ordering
3 stars 1 forks source link

Use multiple GitHub Projects (boards) under an GitHub organization as data source for crowdsourced issue ordering #1

Open pdurbin opened 5 years ago

pdurbin commented 5 years ago

In my "Jupyter Notebooks and crazy ideas for Dataverse" talk in June 2019 I suggested that each of the 46 installations of Dataverse could create a "project" under @IQSS which is the GitHub organization that Dataverse is under. Below are screenshots of the relevant part of the talk, which can be found in full at https://scholar.harvard.edu/pdurbin/blog/2019/jupyter-notebooks-and-crazy-ideas-for-dataverse

Screen Shot 2019-09-28 at 11 13 21 AM Screen Shot 2019-09-28 at 11 13 53 AM

The part to focus on above is "What if installations had a board" and the example from the Odum institute. Here's that slide again:

Screen Shot 2019-09-28 at 11 17 38 AM

Since I gave that talk I've been encouraging installations to go ahead and create boards. As of this writing there are 10 installations of Dataverse who have created boards. Here they are:

I highlighted these boards and encouraged other installations to make their own board in a thread called "boards for prioritizing issues (for each installation of Dataverse)" on the Dataverse mailing list: https://groups.google.com/d/msg/dataverse-community/z8ugn2KzNSc/zt7COeRYBQAJ

The response was positive and we ironed out a few things:

@stevenmce had some great feedback, saying the following

"Just one thought - is there any means of aggregating these boards - so that there is a joint board which the sum of each installation’s boards?

It would require we all use the same board headings, but that seems doable."

I totally agree with this and I think Druthers might be the right place to start working on this aggregation.

I hacked together some scripts and this is what I have so far to at least seeing what the column headings are for each board:

dataverse.scholarsportal.info To do In progress Done

dataverse.lib.virginia.edu Smaller Wishes Bigger wishes (More important to UVA) Real Bugs Closed

dataverse.no Needs triage High priority Low priority Closed

catalogues.cdsp.sciences-po.fr Interest Needed Done

data.qdr.syr.edu Papercuts (Smaller issues) Larger issues IQSS!!!! (Annoying bugs) ✊ Implemented at QDR Closed

data.inra.fr To do In progress Review in progress Reviewer approved Done

dataverse.ada.edu.au To do In progress Done

dataverse.harvard.edu Community Dev 💻❤️ UI/UX Design 💡📝 Ready 🙋 IQSS Sprint 9/25 - 10/9 IQSS Team Dev 💻 Code Review 🦁 QA Done 🚀

dataverse.unc.edu would like to do should do on fire put it out put it out Closed

Next I need to iterate through each column to pull out the cards.

pdurbin commented 5 years ago

I hacked together some scripts

I just pushed this scratch work to 8ddb854

pdurbin commented 5 years ago

In c6af59b I started getting the cards in and 49b320a I started getting issue titles.

pdurbin commented 5 years ago

I posted on https://groups.google.com/d/msg/dataverse-community/z8ugn2KzNSc/3xf4TXIqCQAJ a TSV file and the following screenshot of the aggregated issue list. The thing to notice is that three of the issues have multiple installations that are interested in them. You can also see how it might be good to herd these cats into using the same column names as @stevenmce suggested in the quote above.

Screen Shot 2019-09-28 at 6 16 00 PM

Here's the data, the list of issues across installations who have created a board and put issues on it: issues.tsv.txt

pdurbin commented 2 years ago

I cleaned up the aggregate script a bit and committed it here: https://github.com/IQSS/dataverse-installations/commit/e87b64c