Skip to content

Conversation

@awtj8o81ryywg793
Copy link
Contributor

Description

Add Extera Next client. Closes #3045.

✔️ Checklist

  • Keep this checklist
  • Check for common mistakes:
    • Wrap plain URLs in <> to linkify them (learn more).
    • Use the right level of headings: The page title will use a level 1 headings, so your headings should use level 2 and below.
    • Use internal links: when linking to another page on https://matrix.org, use the Zola [label](@/target.md) syntax.
  • For blog posts:
    • Verify the date and post ordering on the /blog page, especially for multiple posts on the same day. Prefer UTC format, e.g. 2025-12-01T14:00:00Z for Dec 1st, 2025, 2pm UTC.
    • Set the correct author and category. Browse existing ones at https://matrix.org/author/ and https://matrix.org/category/ to match them.
  • If you hold a specific role in relation to the content you are contributing, such as project maintainer or on behalf of a team or organisation, please let us know. See example.
  • If your PR is time-sensitive in any way, please mention the attached timeline and context in the PR description.
  • Mention any issues related to the PR. Use GitHub keywords as appropriate.
  • Your individual commits or pull request is signed off.

@awtj8o81ryywg793 awtj8o81ryywg793 requested a review from a team as a code owner December 8, 2025 03:45
@HarHarLinks HarHarLinks added the ecosystem Adding and removing ecosystem projects label Dec 8, 2025
Copy link
Collaborator

@HarHarLinks HarHarLinks left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We haven't quite formalised this yet, but we need to start tracking asset licenses more properly. Even if we don't end up using that precise tooling contrary to my expectation, I think reuse works well as a stopgap solution as proposed in #2706. Can you add this for the image in this PR?

@awtj8o81ryywg793
Copy link
Contributor Author

Quoted from a previous comment:

We haven't quite formalised this yet, but we need to start tracking asset licenses more properly. Even if we don't end up using that precise tooling contrary to my expectation, I think reuse works well as a stopgap solution as proposed in #2706. Can you add this for the image in this PR?

Sure! @officialdakari, would you be able to offer some insight here in regard to the license used for logo.svg?

@awtj8o81ryywg793
Copy link
Contributor Author

awtj8o81ryywg793 commented Dec 11, 2025

Quoted from a previous comment:

Can you add this for the image in this PR?

@HarHarLinks: Which method is preferred for adding REUSE information: within the file itself or in a separate *.license file?

I can see that a separate .license file is used for /bridges/activitypub/logo.svg, so I’ll just mirror that choice for consistency's sake.

@awtj8o81ryywg793
Copy link
Contributor Author

awtj8o81ryywg793 commented Dec 11, 2025

For the record, while the license for extera-next.svg is not currently noted publicly, after asking in #extera:extera.xyz, I have confirmed with the client's maintainer how the logo is licensed and who created it. I've added extera-next.svg.license, which contains this information. See fd4c00.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ecosystem Adding and removing ecosystem projects

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update: Add Extera Next client

2 participants