Change wording of app description to reflect unstable state.

[Potherca]

Currently, the wording of the description in the Nextcloud app store does not make 100% clear this software is not yet stable.

This leads to understandable frustration (see pdsinterop/code-of-conduct-violations#1).

Hence, the wording of the description needs to be changed so user expectations are better managed.

[NoelDeMartin]

Hey @Potherca, I've been playing with this and I'm considering using it myself (for personal use in a self-hosted Nextcloud instance, so it's not like it needs to work perfectly).

I found this issue, and I wonder how unstable it is. Do you think it's ready for daily usage more or less, or is it in a development state? I remember hearing somewhere that this was passing the test-suite, so I thought it should be stable enough. But then I found this issue and I'm not sure anymore :/.

[Potherca]

Hi! Apologies for my slow response, I've been ill this last week.

First off, let me reassure you, the plugin is quite stable!

We have not run any stress-tests yet, so I can make any statements about performance, but it should be perfectly fine for everyday use.

Until the Solid specs themselves are stable, we won't be able to release a major v1, but beyond that, we believe the plugin is production-ready.

As for the tests, yes, we pass!

A good source to follow who is passing what is https://solidservers.org/#table, which has a nice overview.

Part of our original funding package was contributions to the Solid Test suites, and one member of PDS Interop is part of the test panel. So we are very motivated to improve both the test suites, as well as staying "in the green".

The main reason for this issue is that, at the time (a year ago), manual steps were needed to install this plugin in Nextcloud. The build/deploy process was also done manually, which introduced issues in a specific release.

Since then, things have become a lot more robust, including a recent security audit.

This issue is left open as we still need to do a final round of documentation cleanup, and the deployment process is not 100% automated (there is still one manual step left that needs automating, worked on under #113)

Anyway, I hope this has answered any questions you may have, if not, any feedback is welcome!

Also, if you run into any issues, let us know, we're here to help! 👍

On a side note, I saw your talk at FOSDEM (via live video stream). Great stuff! Very educational.

[NoelDeMartin]

Thanks @Potherca, that answers my questions. I'll keep tinkering with it then, and let you know about any findings I come across :).

And thank you for working on this project! It's very promising, and I like the idea a lot :).