Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Level Access agrees to acquire UserWay #1134

Closed
wants to merge 1 commit into from

Conversation

okeul
Copy link
Contributor

@okeul okeul commented Jan 4, 2024

"When you buy an overlay company, you become an overlay company."

https://www.businesswire.com/news/home/20231230727471/en/Level-Access-Agrees-to-Acquire-UserWay

@aardrian
Copy link
Collaborator

aardrian commented Jan 4, 2024

FWIW, I also opened a PR:
#1128

But I closed it because the page lists product names, not specific vendors (though often the vendor name is the product name). I figured it was better for me to close it and spare the admin hassle of making folks debate it when, as far as I am concerned, it is mooted by the scope of the page.

@okeul
Copy link
Contributor Author

okeul commented Jan 4, 2024

Interesting point.

Another possibility, delete "Level Access" and add "(acquired by Level Access)" next to UserWay. Since, as you said, for most the product = the company, except for this one.

@aardrian
Copy link
Collaborator

aardrian commented Jan 4, 2024

I did not say "most".

The problem comes when smaller agencies white label existing overlay products. That can be management hassle and I certainly am not interested in doing so.

I think a broader community discussion would be warranted for that change (as in, is outside the decision of just the project maintainer).

@karlgroves karlgroves closed this Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants