Add support for NC 30

[IndrekHaav]

The app seems to work fine, this just marks it as compatible.
resolves #200

[IndrekHaav]

Looks like @datenangebot hasn't been active for a while. Pinging @nickvergessen, not sure who else can merge PRs...

[kenda]

Merged your PR but I think we would need a version bump + release to get this out. But I'm not familiar anymore how the release process worked in the last time here.

[nickvergessen]

But I'm not familiar anymore how the release process worked in the last time here.

If you have the app key, it should be something like:

• Bump version in appinfo/info.xml
• Commit and push
• Create a git tag with the version from appinfo/info.xml
• Push the tag
• Make a release out of the tag https://github.com/nextcloud/health/tags
• Remove the leading # from those lines: https://github.com/nextcloud/health/blob/main/Makefile#L67-L70
• make appstore-local
• Upload the file from build/artifacts to the release
• Go to https://apps.nextcloud.com/developer/apps/releases/new
• Post the link to the uploaded health.tar.gz together with the "signature" output from the make command above

[kenda]

If you have the app key, it should be something like:

No, I don't have the app key. The releases were always done by @datenangebot in the past afaik.

[IndrekHaav]

Does this mean the app is effectively unmaintained? Considering the only person who can make a new release appears to be inactive.

[nickvergessen]

You can request a new certificate in https://github.com/nextcloud/app-certificate-requests?tab=readme-ov-file#how-to-request-an-app-certificate

[datenangebot]

Hi, well yes, the app is without a real maintainer at the moment.
And there are known security problems in this app, that's why I don't feel good to ship new releases.
Unfortunately I can't find any time to fix that...

If I can support you to get a new sign key or if there is a handover process, let me know.

[IndrekHaav]

If I can support you to get a new sign key or if there is a handover process, let me know.

@datenangebot If you meant me, then unfortunately I have neither the time nor experience to become a NC app maintainer.

If a new version with NC 30 support is not happening, then perhaps there should be an announcement about this. As you can see from the linked issue, there are quite a few people waiting for an update.

[solonovamax]

And there are known security problems in this app, that's why I don't feel good to ship new releases.

like what? or can you not disclose them publicly?

because if they're able to be disclosed, then it would be possible for someone else to go about fixing them

[BraidenPsiuk]

If that information can't easily be disclosed, maybe this can be answered- Is it worth spending time fixing these security problems? Or is it better to spend the time developing a new app from scratch that follows more modern practices?

And if a new app is developed, is there a good strategy for "sunsetting" old apps and replacing them with new ones?

As a user of this app for a few years now I have unfortunately felt the lack of updates and care for this app, it is almost always the last to get support when upgrading to new NC versions.

[datenangebot]

And if a new app is developed, is there a good strategy for "sunsetting" old apps and replacing them with new ones?

If there is somebody who wants to renew this app by reusing the name and technicaly the namespace, please contact me.

My 50cents: Do we really need this app renewed? I think tracking data can be done by the tables application and generating diagramms and charts can be archieved with the combination of tables and analytics... An health app should be more specific to health topics, allowing specific calculations and so on, but that takes a lot of time and needs expert knowledge. I tried several times to get a team around this topic within the nextcloud company, some community guys and the GNU health organisation, but unfortunately without luck. 🤔