-
Notifications
You must be signed in to change notification settings - Fork 393
add ESS Pro to distributions #2927
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
base: main
Are you sure you want to change the base?
Conversation
|
Hi Neil, we are of course aware of ESS Pro (and ESS Pro TI-M). You may have noticed we did not include any commercial distros at all for the initial launch due to open questions but still trying to get something that was missing a long time finally out of the door. Perhaps you could share your thoughts on this discussion? |
Co-authored-by: Kim Brose <[email protected]>
Deploying matrix-website with
|
| Latest commit: |
e25c130
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9853e5dd.matrix-website.pages.dev |
| Branch Preview URL: | https://neilj-add-ess-pro-to-distrib.matrix-website.pages.dev |
Ah I missed this, okay will comment. |
|
@HarHarLinks I'd really like to make progress on getting this one merged. #2907 (comment) has stalled, but I'm not sure how to bring that discussion to a conclusion. A pragmatic path to me would be to list commercial distros where the owner does contribute to the wider eco-system. For the short term, we exclude non-contributing distros (though do we even have an example of someone who wants to be listed?). I don't believe I can just make that decision myself, but who can? |
Adding in ESS Pro since it is a high profile distribution.
I've said elsewhere but I think we need a deterministic ordering for projects for all eco-system pages and I would support the approach Thib outlines here, but for now, adding as is.
Signed-off-by: Neil Johnson [email protected]
✔️ Checklist
<>to linkify them (learn more).[label](@/target.md)syntax./blogpage, especially for multiple posts on the same day. Prefer UTC format, e.g.2025-12-01T14:00:00Zfor Dec 1st, 2025, 2pm UTC.