Integrate upcoming Community Solid Server release into the website

[RubenVerborgh]

This PR inserts documentation on how to install Community Solid Server v1.0.

[csarven]

Remind me.. is there a reference to where consensus was reached on this change/recommendation?

[jeff-zucker]

May I ask about the intended transition process? I think it would really help implementers if there could be a period when CSS runs on an alternate port for testing before it replaces NSS on the main port. It would also be really helpful to have a rough timeline of when the testing server would be available and when the main port is targeted for switching to CSS. I also have questions about solidcommunity.net as an IDP - will the same registration processes be available?

[RubenVerborgh]

Remind me.. is there a reference to where consensus was reached on this change/recommendation?

There is none; just trying to be helpful with getting the tutorial up to date.
Is there consensus needed for this beyond a review on this PR?

May I ask about the intended transition process?

Absolutely, we need one. And that's going to be a longer conversation.

This is just ensuring that new developers start out with the most spec-compatible Node.js implementation, to avoid creating new apps with old authentication methods, for instance.

I think it would really help implementers if there could be a period when CSS runs on an alternate port for testing before it replaces NSS on the main port.

I also have questions about solidcommunity.net as an IDP

I'm not sure if we're on the same page here; solidcommunity.net is not being replaced at this point in time.

This PR upgrades the docs for new developers to recommend CSS rather than NSS.

[jeff-zucker]

Yes, I see now that prepping the onboarding materials is separate from transition of solidcommunity.net. Is there an issue about the transition on solidcommunity.net? If not, I'll create one.

I agree that it's a good idea to have the onboarding materials recommend CSS to new developers.What I would also like to see in the onboarding materials is a section aimed at existing developers who have aimed their apps at NSS. What should we expect in terms of differences? What things might we have wrongly gotten used to in NSS that won't work the same when spec compliant.

[RubenVerborgh]

Is there an issue about the transition on solidcommunity.net?

I'm not sure if there is an issue; but I know that @justinwb is following up on that.

What I would also like to see in the onboarding materials is a section aimed at existing developers who have aimed their apps at NSS.

Okay if we track that in #607?

[csarven]

There is none; just trying to be helpful with getting the tutorial up to date.

Ack. Replacing NSS with CSS is a significant change. Ditto any implications on existing applications. (This is besides the point on moving things forward..)

Is there consensus needed for this beyond a review on this PR?

Perhaps the PR is sufficient but given its significance I think it'd be appropriate to raise this PR in the next Solid Team meeting, and make sure there are no objections, and concerns are acknowledged. It'd be good to mention the PR in solid/* chats etc.

[RubenVerborgh]

Replacing NSS with CSS is a significant change.

It will be; but that's not the scope of this PR.

This PR adds new CSS documentation and removes old NSS documentation.
We deliberately do not make any suggestions about NSS being replaced, because that is not happening.

It'd be good to mention the PR in solid/* chats etc.

Indeed; tracking at:

• https://gitter.im/solid/team?at=610aa4baf31bc0605a4537f7
• https://gitter.im/solid/chat?at=610aa5a13eec6d41d13b5ad4

raise this PR in the next Solid Team meeting

Unless this PR attracts significant feedback, will raise on 2021-08-11.

[timbl]

"This is just ensuring that new developers start out with the most spec-compatible Node.js implementation, to avoid creating new apps with old authentication methods, for instance." -- well, NSS supports new auth methods as well as the old ones. The solid-ui stack needs to be upgraded. This is in process. Does the databrowser in general work with CSS? I suggest the solidproject.org mention both NSS and CSS for a while, don't just eliminate NSS.

[RubenVerborgh]

Does the databrowser in general work with CSS?

It does not; because Databrowser is using old authentication protocols. And that's exactly what we want to avoid: new people starting out with old things.

I suggest the solidproject.org mention both NSS and CSS for a while, don't just eliminate NSS.

Point taken, I'll just change this PR to keep including NSS, and then there's nothing controversial.

[RubenVerborgh]

Rewrote the PR to add CSS and keep the NSS documentation. Should be entirely uncontroversial now; asking @csarven to confirm if we can proceed with a simple review now. Note that the diff is not very helpful; when deployed, https://solidproject.org/self-hosting/nss/ remains identical to what it is today.

I would immensely appreciate if any of @justinwb @NSeydoux @csarven @jeff-zucker @kay-kim could review so we can launch this new page in time for Solid World tomorrow. Thanks in advance!

[ewingson]

read attentively. as an contributor to https://solidproject.org/self-hosting/nss and maintainer of https://solidweb.org I think it's best to drive simultanously (NSS and CSS) for a while. perhaps onboarding for new people to CSS makes sense. as I can say for today, I will follow the switch of solidcommunity.net when it happens and do my best to admin the part I am responsible for as good as my knowledge is. thumbs up for discussion and building consensus.

[csarven]

To be clear, I only wanted to make sure there is sufficient consensus as well as community awareness on the change in these docs. Now that CSS information only adds to the existing docs, I think that's reasonable and hopefully welcomed by the others.

[csarven]

Useful to introduce CSS...

[RubenVerborgh]

Thanks @ewingson @csarven @jeff-zucker @timbl, merging the addition.

[RubenVerborgh]

Thanks @kay-kim, will take your suggestions into account before merging.