A new free-software forge: sr.ht

Posted Jan 9, 2019 0:28 UTC (Wed) by mageta (subscriber, #89696)
In reply to: A new free-software forge: sr.ht by awilfox
Parent article: A new free-software forge: sr.ht

You should at least try to get some form of coherent argument, instead of just calling it names.

A new free-software forge: sr.ht

Posted Jan 9, 2019 8:29 UTC (Wed) by Archimedes (subscriber, #125143) [Link] (3 responses)

My (personal) main argument in the comparison of email vs web based system would be:
I can choose my email client, I am allowed to configure that client as I wish, I can enhance that client (depending on it) in plenty of ways which help me to work as I would like to, and the great thing is that all what I like on my setup does not influence anybody else.

On Web based systems in all (or maybe most) the user has no real way to change the "websie client" as he would like to use it. Also the workflow, shorcuts, ui, whatever is given by solely the web client. For me that feels like the mainframe times, root == god, user == nothing+epsilon ...

A new free-software forge: sr.ht

Posted Jan 9, 2019 21:10 UTC (Wed) by roc (subscriber, #30627) [Link] (1 responses)

Actually there's quite a lot one can do to customize Github and Gitlab. Both of them have APIs that let you write applications that read/write data and customize workflow. On the UI side, browser extensions let you customize look and feel.

A new free-software forge: sr.ht

Posted Jan 10, 2019 17:57 UTC (Thu) by ddevault (subscriber, #99589) [Link]

An important difference is that email is governed by standards and enjoys a lush ecosystem of open source implementations.

A new free-software forge: sr.ht

Posted Jan 10, 2019 23:11 UTC (Thu) by neilbrown (subscriber, #359) [Link]

> My (personal) main argument in the comparison of email vs web based system would be:

Mine would be "federation". By this, I particularly mean a global name-space for contributors, together with (at least) minimal interaction possibilities between all platforms.

If I want to add "Reported-by:" to a patch that I generate, based on a report that I received on some weird platform (case-in-point: github issues), the name attached to the problem report should be a universal name that I can use in the Reported-by tag.

If I want to include someone in a conversation - I should be able to request that within the platform and they should be able to receive my request, review the history, and make a comment without having to sign-in or anything - just follow a link to read, and then reply to the original message to contribute.