We, @Andre_Costa, @Alicia_Fagerving and myself, have done some planning for Wikimedia Sverige's development work on OperRefine. We had a look at the open issues on Github and some other places where bugs and feature requests could be found. This resulted in a table of prioritised tasks.
We gave each issue two scores "Development time" and "Impact". The former is how long I estimated it would take for me to solve it. The latter is how large positive impact it's expected to have once solved, judged by Alicia. Both are rough, relative values and only meant to be a way to compare the issues with each other.
Finally there is a weighted score that combines the two scores. This is lower for issues that have a high impact and low development time, and these are the ones I've started working on. Note however that this is not a strict order and I may work issues further down in the list when that makes sense.
3 Likes
Hi @Sebastian,
Do all of the linked issues in column "Link" of the spreadsheet table have the GitHub label "wikicommons" ? If not, I'd like to know which issues in the table have nothing to do with the Wikicommons extension. My hunch is that all of them do?, but perhaps a few are indeed only OpenRefine issues only with nothing to do with the Wikicommons extension (but simply makes things better for the Wikicommons extension)?
Basically, I just want to ensure that our OpenRefine GitHub issues are labeled correctly, first and foremost. Secondly, I'd appreciate if you could add another column that stipulates if it Touches OpenRefine Only, because the Link column with naming of "CE" or not, doesn't really reflect the issue itself.
Thanks in advance! Looking forward to the collaboration!
This is really great prioritization work, thank you @Alicia_Fagerving and @Sebastian!
Do all of the linked issues in column "Link" of the spreadsheet table have the GitHub label "wikicommons" ? If not, I'd like to know which issues in the table have nothing to do with the Wikicommons extension.
I looked through the ones in the main OpenRefine repo and found two that aren't labeled "wikicommons": #6767 and #6814. I don't know if these should be marked with "wikicommons". I think that depends on what you count as "related" in the label description: "Related to Wikimedia Commons integration".
My hunch is that all of them do?, but perhaps a few are indeed only OpenRefine issues only with nothing to do with the Wikicommons extension (but simply makes things better for the Wikicommons extension)?
I believe the Wikibase extension isn't technically connected to the Commons extension and some issues will result in improvements there. My work will be limited to improvements for using OpenRefine with Commons however, regardless of what parts of the code are changed.
Secondly, I'd appreciate if you could add another column that stipulates if it Touches OpenRefine Only, because the Link column with naming of "CE" or not, doesn't really reflect the issue itself.
I don't understand what you mean by "Touches OpenRefine Only". Could you elaborate?
Ah thanks for clarifying: your work is only going to be towards the Commons extension and not the Wikibase extension.
For "Touches OpenRefine Only", I meant your work where code changes to OpenRefine is done, and not in the /extensions directory. I.E. a regular OpenRefine issue that would not have a label of "wikicommons".
If you or the dev team feel that those 2 issues, #6767 and #6814 also affect "wikicommons", then I'd say we should also apply that label to both of them. In the end, it helps later on for provenance and understanding where the impacts are for our extension ecosystem. I guess that's how I should have phrased it before "what extensions are affected by this issue". Some extensions would have their own issues in their own repo (and properly I would expect them to) and simply link to an OpenRefine issue when appropriate. However, I am of the stance that we have so few extensions to begin with that having labels for them in our own repo probably makes things easier overall for both sides 
Those two issues apply to the Wikibase integration, so they are relevant for Wikidata, Wikimedia Commons and any other Wikibase instance.
I don't think it's very helpful to add the "wikicommons" label to all issues which have the "wikibase" tag, it would feel redundant to me.
1 Like
Ah thanks for clarifying: your work is only going to be towards the Commons extension and not the Wikibase extension.
I think my clarification wasn't quite clear enough🙂 I'm working on both the Wikibase and Commons extensions. The focus is on making things easier for working with Wikimedia Commons. Where in the code that changes are made are less relevant.
For "Touches OpenRefine Only", I meant your work where code changes to OpenRefine is done, and not in the /extensions directory. I.E. a regular OpenRefine issue that would not have a label of "wikicommons".
I doubt that I'll make any changes in OpenRefine core. If that's required for any of the issues I'll be working on, it probably means it's out of scope.