By the way, you say it’s clear we don’t want to stay on HipChat.
When did we decide that? I don’t remember a discussion about it.
For sure, we probably won’t have a choice because there’s a good chance
Atlassian will close the service but what are the problems that make a
migration so urgent?
> Le 17 mai 2018 à 20:16, Sanne Grinovero <sa...@hibernate.org> a écrit :
> lol, I was writing about the same to the team list.
> +1 to have people register, it's better for them anyway. I checked
> it's easier to self-register.
> +1 to migrate quickly. It's clear we don't want to stay on HipChat, if
> this doesn't work out we'll see.
> Refer to my parallel email for Fedora instructions.
>> On 17 May 2018 at 19:03, Steve Ebersole <st...@hibernate.org> wrote:
>> I got an email from Atlassian this morning about the migration from HipChat
>> to Stride. Basically they have not gotten Stride feature-complete in terms
>> of HipChat which is the trigger for the mass migration. However, they are
>> reaching out to all waiting teams to see if any want to migrate anyway.
>> The list of missing features they sent me are:
>> 1. Guest access
>> 2. Some admin controls and compliance settings
>> 3. Integrations with Atlassian server products (the Jira Server app is
>> currently in beta and coming soon) and some other popular integrations. See
>> all available Stride integrations
>> 4. User management via API
>> 5. Dark mode
>> I am not really sure exactly what is missing WRT (2). (3) is nice-to-have,
>> but not blocker IMO assuming it gets added at some point.
>> I think (1) is the only one that is concerning. Though TBH for myself
>> personally, I do not think registering is a big deal.
>> Unless I hear otherwise, I plan on asking them to proceed with our
>> migration to Stride.
>> hibernate-dev mailing list
> hibernate-dev mailing list
hibernate-dev mailing list