Skip to content
This repository has been archived by the owner on Nov 26, 2020. It is now read-only.

Archive module #44

Open
ekohl opened this issue Nov 29, 2019 · 11 comments
Open

Archive module #44

ekohl opened this issue Nov 29, 2019 · 11 comments

Comments

@ekohl
Copy link
Member

ekohl commented Nov 29, 2019

Per https://www.atlassian.com/partnerships/slack/faq#faq-da2b66a1-53d3-4c4e-a405-467d961336f7 and https://en.wikipedia.org/wiki/HipChat it appears HipChat has been discontinued since February 2019. That means this module can be archived.

@alexjfisher
Copy link
Member

There was also a self-hosted version of hipchat which I suppose some people will still be using. Maybe the README update could mention that if you are using this module with a self-hosted hipchat to open an issue if you need the module unarchived??

@ekohl
Copy link
Member Author

ekohl commented Nov 29, 2019

Looks like Hipchat Server is not EOL until Jun 30, 2020 according to https://confluence.atlassian.com/support/atlassian-support-end-of-life-policy-201851003.html.

Since you can't open issues on archived modules, I'm proposing we deprecate the module instead. That means a big fat warning in README.md referring to this issue, removing it from modulesync_config and plumbing. Also close all open PRs. If anyone is interested in reviving the module, they should comment here.

@alexjfisher
Copy link
Member

I was also wondering about adding some centralised policy doc. eg. voxpupuli/voxpupuli.github.io#213

@james-powis
Copy link
Member

As the person who initially brought this module from @jamtur01 management to Vox, I no longer work for an organization that uses Hipchat... (and to be fair they all have moved from Hipchat to other alternatives...).

To be honest, this module has been a nightmare to even try and support without having access to a Hipchat installation given its closed source and steep entry to replicate on-prem / cloud-based implementations.

I am totally cool with calling it deprecated today and abandoned at the OnPrem EOL.

@jamtur01
Copy link
Contributor

Sounds good to me.

@alexjfisher
Copy link
Member

@james-powis @jamtur01 Thanks both for your input.

@ekohl
Copy link
Member Author

ekohl commented Aug 30, 2020

Looks like it's now officially EOL and we can proceed with archiving.

@igalic
Copy link
Contributor

igalic commented Sep 5, 2020

what does archiving a module do to the forge release?

@alexjfisher
Copy link
Member

I say we leave the forge copy as is (ie. don't deprecate it). It's not like we can suggest a replacement. Users themselves will know if they're still running an EOL hipchat server locally.

@ekohl
Copy link
Member Author

ekohl commented Nov 25, 2020

I'm not sure you need to hint at a replacement for deprecation. I think you can just say "don't use this anymore", which is perfectly valid.

@ekohl
Copy link
Member Author

ekohl commented Nov 25, 2020

Following https://voxpupuli.org/docs/deprecated_and_archived_modules/. I've pushed e58db4c to refer to this issue. Going to archive the module now. Thanks everyone!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants