Add certificate request for nc_connector_backend

[DeBaschdi]

This pull request adds the certificate signing request for the Nextcloud app nc_connector_backend

Checklist

• Please include a link to your app repository
  https://github.com/nc-connector/Server_Backend

[jospoortvliet]

Hello,
the name has been changed before :D . I was actually still in agreement with @AndyScherzinger (At the time, the issue was the naming of the mail clients.) that I could use NC Connector.

Or is it only about the AppID?

I have the NC Connector for Thunderbird as a mail add-on, as well as the NC Connector for Outlook.

This is supposed to be my server backend for it.
Would "nc_connector_backend" be sufficiently differentiated?

hum, let me blame andy then. I think the name nextcloud connector, or nextcloud connector back-end, is super duper generic. Connector to what? MariaDB? Microsoft Office? Paypal?

Of course, in the Thunderbird appstore it makes sense the name is nc_connector, but by that logic in the Nextcloud app store it should be called tb_connector - see what I mean?

I just rather not have an app in our appstore occupy such a super generic name... So for the back-end, if it was tb_connector or tb-nc_connector, it would be clear what the connector is about at least from the name. To some degree at least - "Thunderbird_Nextcloud_connector_by_DeBaschdi" would be a little... long 😄

I'm sorry for the extra work - but I hope you understand and can agree with the logic behind my request!

[DeBaschdi]

@jospoortvliet
Thanks, I understand.

I understand the problem now: In the context of the Nextcloud App Store, "nc_connector_backend" is still too general, as it doesn't clearly indicate what the connector is for.

I can rename the app ID to something more specific.

Would "nc_mail_connector_backend" be acceptable?

That would cover existing Outlook, Thunderbird, and upcomming future applications.

[DeBaschdi]

Next Try --> #967