Hi Everyone, This topic was touched upon in a recent "Enabling Github Issues for Infusion project <http://fluid.2324889.n4.nabble.com/Enabling-Github-Issues-for-Infusion-project-td10666.html>” Fluid-Work mailing-list thread. However, what I’m proposing here is slightly different from that particular discussion so thought it best to move off into a new thread.
TL;DR: Use GitHub issues for repos that don’t have their own JIRA space The problem: A couple of things that I personal find confusing and/or have seen others trip over are: That a repo has GitHub issues active and is also tracked in JIRA (e.g. the floe project website - GitHub Issues <https://github.com/fluid-project/floeproject.org>, JIRA <https://issues.fluidproject.org/issues/?jql=project%20=%20FLOE%20AND%20component%20=%20%22FLOE%20Website%22>) That a project/repo is tracked in a JIRA space but doesn’t follow the same release and versioning. (e.g. fluid-publish <https://issues.fluidproject.org/issues/?jql=project%20=%20FLUID%20AND%20component%20=%20fluid-publish>) Proposal: Use Fluid JIRA project only for Infusion. Move other repos/projects to other JIRA projects or GitHub issues as needed When migrating issues from between JIRA spaces or GitHub issues, the existing issues should be migrated as well Use GitHub Issues for existing repos that do not have a corresponding JIRA project Use GitHub Issues for new repos, unless/until there are features and etc needed that aren’t supported by GitHub issues but are available in JIRA, at which point a new JIRA project should be created. For projects/repos that use JIRA, GitHub issues should be disabled and information provided in the README and/or other appropriate location to indicate that issues are tracked in JIRA. The previous thread also discussed having JIRA and GitHub issues synced together, or migrating everything to GitHub Issues from JIRA. I’m not intending to weigh in on those questions with this proposal. I’m taking this from the point of view of how things are currently being done. If one or more of those other suggestions/proposals are accepted, my suggestions above can be modified as needed. In general I want to reduce the confusion that may be happening in our issue trackers at the moment. Thanks Justin
_______________________________________________________ fluid-work mailing list - fluid-work@lists.idrc.ocad.ca To unsubscribe, change settings or access archives, see https://lists.idrc.ocad.ca/mailman/listinfo/fluid-work
