Changes to Atlassian products

Tue Oct 20 14:54:13 UTC 2020

I wonder if the ILDH related issues are a good place to start with migrating from JIRA to GitHub Issues. We have been tracking issues for websites in GitHub Issues more recently and the ILDH currently has JIRAs tracked in two or three different JIRA projects. Also we’re starting to work on that project again. I was talking a bit with Ned about it in the IRC channel the other day and sounded like it would be preferred to use GitHub Issues going forward.

We should consider if we want to move all of the issues (closed and open), if there is an automated way to do the migration (I believe we’ll have to create our own script using the GitHub API), and what information we want to preserver.

The wiki is a really good question. My initial thought is that migrating to another wiki could be a nightmare, although this stackoverflow <https://stackoverflow.com/a/19280892> post suggests exporting as HTML and using Pandoc to convert to markdown for migration to GitHub Wiki. Breaking all of our links to the wiki is also really sad. I’m not sure what we can do about that though. 

Thanks
Justin

> On Oct 20, 2020, at 10:25 AM, Colin Clark <colinbdclark at gmail.com> wrote:
> 
> Hi Justin and Gio,
> 
> Thanks for looking into this. It sounds like realistically we may have a few different kinds of projects. Some have thousands of issues with lots of detail, discussion, and history associated with them. Others may have a smaller pool of issues. Maybe for that latter category, as we’ve already been exploring, we can consider migrating to Github Issues. We can use them as to evaluate whether migrating the larger projects will be feasible, or if we’ll have to move to a more restricted cloud-hosted version of JIRA for those.
> 
> The other question is what we do with the wiki…
> 
> Colin
> 
>> On Oct 20, 2020, at 8:12 AM, Justin Obara <obara.justin at gmail.com <mailto:obara.justin at gmail.com>> wrote:
>> 
>> Gio and I spoke a bit in the fluid-work IRC channel <http://irc-logs.fluidproject.org/#fluid-work/%23fluid-work.2020-10-20.log> this morning. Below is a quick summary:
>> 
>> People aren’t happy about forced migration and lack of custom domains for Atlassian Cloud
>> Atlassian said they’d review the roadmap for custom domains in January 2021
>> JIRA issue numbers will likely be preserved 
>> User accounts and workflows will be migrated
>> This seems like a good time to review our use of these tools and consider alternatives
>> 
>> Thanks
>> Justin
>> 
>>> On Oct 19, 2020, at 3:30 PM, Giovanni Tirloni <gtirloni at ocadu.ca <mailto:gtirloni at ocadu.ca>> wrote:
>>> 
>>> Hi Justin,
>>> 
>>> I've submitted a request for licenses for their cloud products so we can assess the situation. The ETA is 3 business days to hear from them.
>>> 
>>> Re: impact. Unfortunately, it's not possible to use custom domains with Atlassian Cloud products [0]. That means our links to wiki.fluidproject.org <http://wiki.fluidproject.org/> and issues.fluidproject.org <http://issues.fluidproject.org/> would be broken.
>>> 
>>> 0 - https://jira.atlassian.com/browse/CLOUD-6999 <https://jira.atlassian.com/browse/CLOUD-6999>
>>> 
>>> From: Justin Obara <obara.justin at gmail.com <mailto:obara.justin at gmail.com>>
>>> Sent: Monday, October 19, 2020 08:59
>>> To: Giovanni Tirloni <gtirloni at ocadu.ca <mailto:gtirloni at ocadu.ca>>
>>> Cc: fluid-work at lists.idrc.ocad.ca <mailto:fluid-work at lists.idrc.ocad.ca> <fluid-work at lists.idrc.ocad.ca <mailto:fluid-work at lists.idrc.ocad.ca>>
>>> Subject: Re: Changes to Atlassian products
>>>  
>>> Hi Gio,
>>> 
>>> Thanks for the update. I remember looking at their cloud offerings pre-pandemic. It seemed like they still offered free cloud options for open source projects. However, the plugins weren’t free anymore. Is that still the case and do we actually need the plugins we’re currently using if we migrate to the cloud? Also do you have a gauge on how else this might affect us? For example will existing links to the wiki and JIRA break once we move to the cloud?
>>> 
>>> Thanks
>>> Justin
>>> 
>>>> On Oct 16, 2020, at 8:41 PM, Giovanni Tirloni <gtirloni at ocadu.ca <mailto:gtirloni at ocadu.ca>> wrote:
>>>> 
>>>> Hello,
>>>> 
>>>> Atlassian will stop selling the Server version of their products. We use a self-hosted JIRA Server.
>>>> 
>>>> See the announcement and a timeline for the change here: 
>>>> 
>>>> https://www.atlassian.com/migration/journey-to-cloud?jobid=104830907&subid=1515944789 <https://www.atlassian.com/migration/journey-to-cloud?jobid=104830907&subid=1515944789>
>>>> 
>>>> https://www.atlassian.com/migration/key-offering-changes?tab=server-dates#important-dates <https://www.atlassian.com/migration/key-offering-changes?tab=server-dates#important-dates>
>>>> 
>>>> By Feb 2022 there will no more upgrades (new versions).
>>>> 
>>>> I think it's unrealistic to expect they will put any effort into releasing new functionality or anything outside critical bug fixes moving forward.
>>>> 
>>>> My initial impression is that we'd have to migrate to their cloud offering (like GPII?) or move to a different ticket system altogether.
>>>> 
>>>> Regards,
>>>> Giovanni
>>>> 
>>>> 
>>>> _______________________________________________________
>>>> 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 <https://lists.idrc.ocad.ca/mailman/listinfo/fluid-work>
>> _______________________________________________________
>> 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 <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/20201020/1bf03bb8/attachment.html>