Enabling Github Issues for Infusion project

Wed Jan 8 23:30:00 UTC 2020

Hi all,

I think there’s value in keeping all of our issue tracking and related communications in the same place. Indeed, having those in the same place as our code seems to make even more sense! We wouldn’t need to concern ourselves with either keeping everything lined up manually or maintaining a set of actions to transfer everything over and then update the relevant GitHub issues whenever progress is made. We would also gain the ability to have commit comments like “Closes #50” rather than having to manage webhooks to close/reopen issues with pull requests.

Furthermore, GitHub is a website that has a much larger userbase and higher traffic rate than our own Jira site(s), so in terms of attracting new participants to our work it might be a better choice to migrate to GitHub. We also wouldn’t need to worry as much about spam accounts. In eliminating our Jira sites, we also eliminate the need to support them. Of course that also means we’re beholden to GitHub and Microsoft and their licence agreements, though I don’t see this as much worse than depending on Atlassian for working software.

One thing to consider: would Confluence play as nicely with GitHub as it does with Jira? I.e. if I wanted to link an issue in the Iteration Plan, do we lose anything in terms of functionality?

The Spring Framework migration that Justin shared is promising, and it looks like the timestamps from comments were also preserved.

Lastly, as the Spring notes allude to, the markup issue is one we’ll have to deal with, though we’re currently experiencing issues with that anyway so I don’t see this as much of a factor.

I’d love to know your thoughts on these arguments! I don’t have a strong preference, but if we’re going to do anything at all, moving things to GitHub makes the most sense to me.

Cheers,
Gregor

From: fluid-work <fluid-work-bounces at lists.idrc.ocad.ca> On Behalf Of Jonathan Hung
Sent: January 8, 2020 11:45
To: Fluid Work <fluid-work at fluidproject.org>
Subject: RE: Enabling Github Issues for Infusion project

Taking a step back, the main motivation for using github issues is to reduce the barrier for users, and provide an optional way for these users to interact with the project.

For github issues to work well I think there needs to be a:

  *   clear definition of the purpose of github issues tracker
  *   guideline / process for project maintainers for dealing with items in the github tracker (perhaps a combination of curation and automation)

What if Jira remains the primary bug tracker, and github issues as a way to engage users with a clear guideline and process for dealing with bug reports / support tickets.

From: Ned Zimmerman <nzimmerman at ocadu.ca<mailto:nzimmerman at ocadu.ca>>
Sent: January 8, 2020 10:45 AM
To: Justin Obara <obara.justin at gmail.com<mailto:obara.justin at gmail.com>>; Jonathan Hung <jhung at ocadu.ca<mailto:jhung at ocadu.ca>>
Cc: Fluid Work <fluid-work at fluidproject.org<mailto:fluid-work at fluidproject.org>>
Subject: Re: Enabling Github Issues for Infusion project

GitHub Actions could almost certainly be used to automatically open a JIRA from a GitHub issue and close the GitHub issue. I think I’ve seen something like this demonstrated.

Cheers,
Ned
—
Ned Zimmerman
Senior Inclusive Developer
Inclusive Design Research Centre, OCAD University
https://idrc.ocadu.ca

From: fluid-work <fluid-work-bounces at lists.idrc.ocad.ca<mailto:fluid-work-bounces at lists.idrc.ocad.ca>> on behalf of Justin Obara <obara.justin at gmail.com<mailto:obara.justin at gmail.com>>
Date: Wednesday, January 8, 2020 at 8:44 AM
To: Jonathan Hung <jhung at ocadu.ca<mailto:jhung at ocadu.ca>>
Cc: Fluid Work <fluid-work at fluidproject.org<mailto:fluid-work at fluidproject.org>>
Subject: Re: Enabling Github Issues for Infusion project

Hi Jon,

It would be possible to turn it on. I guess we need to decide how to manage issues filed through GitHub. (e.g. create a related issue in JIRA, add a link to the GitHub issue, and close the GitHub issue immediately (or maybe along with the JIRA issue).

If it’s desirable we could also explore migrating infusion and other things over to GitHub issues. I initially thought it would be too late for Infusion but the Spring Framework migrated 15+ years of issues from JIRA to GitHub Issues, so it is possible. ( https://spring.io/blog/2019/01/15/spring-framework-s-migration-from-jira-to-github-issues ). Also, if I’m not mistaken, I believe GitHub Actions work on issues as well, so there may be some interesting automatons we could build in if needed.

Thanks
Justin

On Jan 8, 2020, at 10:25 AM, Jonathan Hung <jhung at ocadu.ca<mailto:jhung at ocadu.ca>> wrote:

Hi everyone,

I am in the process of updating documentation related to UI Options and would like to add a section about how a user can file bug reports or give feedback.

I noticed that Infusion does not have Github issues enabled, is it possible to turn this on? Many open source projects offer this as a communication path.

Input is appreciated.

Thanks!

-Jon.

---
Jonathan Hung, Inclusive Design Collaborator / Researcher
Email: jhung at ocadu.ca<mailto:jhung at ocadu.ca>
OCAD University
Inclusive Design Research Centre

_______________________________________________________
fluid-work mailing list - fluid-work at lists.idrc.ocad.ca<mailto:fluid-work at lists.idrc.ocad.ca>
To unsubscribe, change settings or access archives,
see https://lists.idrc.ocad.ca/mailman/listinfo/fluid-work

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.idrc.ocad.ca/pipermail/fluid-work/attachments/20200108/cd7fd077/attachment.html>