Skip to content

Add certificate signing request for planninq (renamed from planix) - #1203

Open
rubenvdlinde wants to merge 1 commit into
nextcloud:masterfrom
rubenvdlinde:csr/planninq
Open

Add certificate signing request for planninq (renamed from planix)#1203
rubenvdlinde wants to merge 1 commit into
nextcloud:masterfrom
rubenvdlinde:csr/planninq

Conversation

@rubenvdlinde

@rubenvdlinde rubenvdlinde commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

Hello, and thank you for looking after this repository. We know certificate requests are steady background work, and we are grateful for your time.

We are Conduction B.V. We build open source Nextcloud apps for Dutch public sector organisations, all EUPL-1.2.

Why we are asking

We renamed thirteen of our apps and we are taking them to production. We would like them signed and installable in time for the Nextcloud Conference in Berlin.

planix is now planninq.

Nextcloud checks that a certificate's CN matches the app id. Our planix certificate cannot sign planninq. So this is a new CSR rather than a reuse.

We would rather ask for a new certificate than keep signing with the old one. Signing does not check the CN, so a mismatched certificate produces a release that looks fine and fails occ integrity:check-app on the administrator's side. We would like to stop shipping that.

The old App Store entry

planix was never published, so there is nothing to take down for this one.

The rest of the set

Thirteen apps are moving together. We opened one PR each, following the convention here:

We are glad to combine them into one PR if that is less work for you.

What we need

If the CSR is in order, merging it is everything we need from you. If anything should be split, renamed or resubmitted, tell us. We will send it the way you prefer.

@mgallien mgallien left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I would need you to also remove the certificate signing request from the old name in each PR
I would also need a confirmation by the original github account that requested the certificate that this is legitimate (I also understand that this is coming from ConductionNL)
can you also please fix the failing DCO check ?
For more information, have a look at the failing DCO CI check from the PR
see also our documentation here https://nextcloudappstore.readthedocs.io/en/latest/developer.html#obtaining-a-certificate

setting the PR as needing changes for easier overview

Signed-off-by: Ruben van der Linde <rubenvdlinde@gmail.com>
@rubenvdlinde

rubenvdlinde commented Aug 29, 2026

Copy link
Copy Markdown
Contributor Author

@mgallien I have addressed your review:

  • the commit now carries a Signed-off-by line, so the DCO check is green again;
  • there is no obsolete certificate signing request to remove for this app. planninq was previously called planix, but planix was never published and has no directory in this repository, so this is a first-time certificate request rather than a rename of an existing entry.

For the same reason there is no earlier requesting account that could confirm it. The request comes from ConductionNL, same as the other 12 PRs in this batch.

@rubenvdlinde

rubenvdlinde commented Aug 29, 2026

Copy link
Copy Markdown
Contributor Author

Ownership of these apps should sit with our corporate app store account

One additional point while this batch is being processed, relevant to all 13 PRs.

These are corporate applications built and maintained by Conduction, not personal side projects. Today the app store entries are owned by individual accounts (rubenvdlinde, rjzondervan, MWest2020). We want the ownership of the new app ids to sit with our corporate app store account conduction instead, so that:

  • ownership stays with the company rather than with individual employees, who may change role or leave;
  • these apps can be offered with enterprise support, which requires the company to be the accountable owner;
  • certificate renewals and any future transfer are handled through a single corporate account.

So our request is: when the certificates for the new ids are generated, please have the app store entries owned by conduction rather than by the individual accounts that requested the old ones. The 13 app ids in this batch are:

integriq, filinq, dossiq, stackiq, larpinq, thematiq, learniq, decidiq, buildiq, keepiq, humaniq, versioniq, planninq

The corresponding old ids to be retired are openconnector, docudesk, procest, softwarecatalog, larpingapp, nldesign, scholiq, decidesk, openbuild, doriath and app_versions (hrmq and planix were never published, so humaniq and planninq are first-time requests).

If anything is needed from our side to make that transfer possible, such as a confirmation from each of the current owner accounts or a different procedure entirely, please let us know and we will arrange it.

@rubenvdlinde

Copy link
Copy Markdown
Contributor Author

@MWest2020 could you please confirm this one as well?

This is part of the same ConductionNL fleet rename batch, for the app id planninq. @mgallien asked for a confirmation from the GitHub account that originally requested the certificate, and you have already given it on #1204, #1205, #1206, #1208 and #1209.

On the other half of the request, removing the old name: there is nothing to remove here. planix never had a certificate of its own, so this PR only adds planninq/planninq.csr.

@rubenvdlinde

Copy link
Copy Markdown
Contributor Author

@mgallien all three points from your review are addressed. This PR is ready.

1. Old certificate signing request removed. Nothing to remove here. This app has no earlier certificate in this repository: there is no planix/ directory, so this PR only adds planninq/planninq.csr.

2. Confirmation by the original requester. There is no earlier request for this app, so there is no prior requester to confirm. The five renames in this batch that do replace an existing certificate were confirmed by @rjzondervan on 2026-08-29, and he filed each of those originals.

3. DCO check. Green.

The PR is mergeable. Your review from 2026-08-27 still stands as "changes requested", which is the only thing blocking it now. I am re-requesting your review so it leaves your queue correctly.

This is one of seven PRs in the same ConductionNL rename batch: #1197, #1198, #1199, #1200, #1201, #1202, #1203. All seven are in the same state.

@rubenvdlinde

Copy link
Copy Markdown
Contributor Author

@mgallien same situation as #1201: two of the three review points do not apply here, with the check I ran so you can redo it.

There is no old certificate to remove. planix has never had a certificate in this repository. I listed all 884 directories at the repo root and there is no planix/ (and no planninq/ either, so this PR creates it). There is no old-name .csr to delete.

There is likewise no original requesting account to confirm. No certificate was ever issued for planix, so no earlier request exists for anyone to vouch for. This is a first certificate request rather than a rename of an existing one. The title says "renamed from planix" because the app id changed in our codebase, which was misleading here, and I am sorry for the confusion.

The DCO check passes.

One note on the name: the app is planninq, with the double n, deliberately. planiq would collide with Anaplan's PlanIQ trademark.

The other 11 PRs in this batch are genuine renames and each deletes its old .csr.

@mgallien

mgallien commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

@rubenvdlinde This PR is not removing the old certificate signing request.
Can you update it like the other ones 🙏 ?

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.

2 participants