Hello everyone,
<https://pr.pico.sh/> is an open source server for letting contributors make a pull request using SSH. I think it would be a great addition to Sourcehut, because the mail workflow is confusing, especially for beginners coming from GitHub. What do you think?
On July 14, 2024 2:48:44 PM GMT+02:00, "Страхиња Радић" <sr@strahinja.org> wrote:
>Дана 24/07/14 02:37PM, Jakob написа:>What is confusing about it exactly?
- A contributor has to enable SMTP in the settings of most mail providers.
- A contributor needs to configure Git. (It took me quite some time, because my hosting provider configured their server in a weird way.)
Using the pr.pico.sh software, it's just piping a patch into ssh. Reviews and revisions work the same way.
Another difference is that ssh runs fine on Android, but git-send-email doesn't. Using ssh would allow me and other people to quickly do PRs, reviews & revisions on the phone or tablet, when a proper computer isn't available.
> <https://pr.pico.sh/> is an open source server for letting contributors make a pull request using SSH. I think it would be a great addition to Sourcehut, because the mail workflow is confusing, especially for beginners coming from GitHub. What do you think?
This looks like a very interesting tool, thanks for sharing!
I would also be in favor of sr.ht supporting this when time allows.
Pico is interesting but is currently in pre-alpha. I’m not sure it makes sense to integrate with it at this stage, personally. It also has vastly different semantics on how feedback is embedded in a patch in ways that are mostly incompatible with the email workflow. In practice repositories would have to choose which semantics they prefer, which could be clunky and lead to frustration.
On July 14, 2024 3:07:00 PM GMT+02:00, Andrew Thorp <andrew.thorp.dev@gmail.com> wrote:
> In practice repositories would have to choose which semantics they prefer, which could be clunky and lead to frustration.
I agree with that. This could indeed be a problem. On the other hand keep in mind, that email is an old, fragile and complex technology. Self-hosting mail and avoiding to get blocked by big providers (e.g. gmail, hotmail, gmx) isn't that easy. In contrast, creating a ssh key pair is very easy.
Дана 24/07/14 03:04PM, Jakob написа:
> - A contributor has to enable SMTP in the settings of most mail > providers.
Email "providers" that don't support SMTP, like Tutanota, suck anyway.
Probably the most widespread free email provider, Gmail, currently
supports SMTP, and works with SMTP clients. Personally, for Gmail I'm
using msmtp[1] with its "allow insecure applications" setting and
"application password" even unrelated with Git, so I'm also using it
for Git. (I also use msmtp for my hosted email server.) The usage of
msmtp in Git is easily set up by adding this to .gitconfig:
[sendemail]
from = Your Name <youremail@host.com>
sendmailCmd = msmtp -a youremail@host.com> - A contributor needs to configure Git. (It took me quite some time, > because my hosting provider configured their server in a weird way.)
Git needs to be configured properly anyway (see above or [2])? This is
a one-time thing and thus a non-issue.
---
[1]: https://marlam.de/msmtp/
[2]: https://git-send-email.io/
On July 14, 2024 3:41:13 PM GMT+02:00, "Страхиња Радић" <sr@strahinja.org> wrote:
>Дана 24/07/14 03:04PM, Jakob написа:>> - A contributor has to enable SMTP in the settings of most mail >> providers.>>Email "providers" that don't support SMTP, like Tutanota, suck anyway.>Probably the most widespread free email provider, Gmail, currently>supports SMTP, and works with SMTP clients. Personally, for Gmail I'm>using msmtp[1] with its "allow insecure applications" setting and>"application password" even unrelated with Git, so I'm also using it>for Git. (I also use msmtp for my hosted email server.) The usage of>msmtp in Git is easily set up by adding this to .gitconfig:>> [sendemail]> from = Your Name <youremail@host.com>> sendmailCmd = msmtp -a youremail@host.com>>>> - A contributor needs to configure Git. (It took me quite some time, >> because my hosting provider configured their server in a weird way.)>>Git needs to be configured properly anyway (see above or [2])? This is>a one-time thing and thus a non-issue.>>>--->>[1]: https://marlam.de/msmtp/>[2]: https://git-send-email.io/>
On July 14, 2024 3:41:13 PM GMT+02:00, "Страхиња Радић" <sr@strahinja.org> wrote:
>Дана 24/07/14 03:04PM, Jakob написа:> This is a one-time thing and thus a non-issue.
Yes, but compare that to GitHub: Click the green button to fork, clone your repo, commit, push, click the green button to make a PR and done.
On 2024-07-14 15:41, Страхиња Радић wrote:
> Дана 24/07/14 03:04PM, Jakob написа:>> - A contributor has to enable SMTP in the settings of most mail >> providers.> > Email "providers" that don't support SMTP, like Tutanota, suck anyway.> ...
That is not an especially productive response to give to users who want
to contribute to a project, just saying.
Дана 24/07/14 04:13PM, Jakob написа:
> Yes, but compare that to GitHub: Click the green button to fork, > clone your repo, commit, push, click the green button to make a PR and > done.
I don't like clicking JavaScript buttons on web pages selling my data
to third parties or feeding my code to AI if I can avoid it. Sometimes
it is regrettably the only way to contribute to Free Software projects,
_only_ because they aren't present on a code hosting platform like
Sourcehut.
In contrast to this, I use simple command line and TUI programs to get
the job done in a straightforward, efficient and controllable way. I
use Neomutt as email client, I use Vim as my main text editor (and my
own editor sled[1] as EDITOR - eg. used by Neomutt for email
composition, as well as Git and Got for commit/tag messages), and so
on.
The thing which I love Sourcehut for, and the reason I switched to it
as my main code hosting provider, is that from the start it adopted
the *opposite* policies to those of Github (esp. after Github was
acquired by Microsoft). It so far stands firmly against AI and Bitcoin
miners, and uses email-based workflow instead of the PR web-based
system.
[1]: https://strahinja.srht.site/sled
On Sun, Jul 14, 2024 at 02:37:58PM +0200, Jakob wrote:
> Hello everyone,> > <https://pr.pico.sh/> is an open source server for letting contributors make a pull request using SSH. I think it would be a great addition to Sourcehut, because the mail workflow is confusing, especially for beginners coming from GitHub. What do you think?
nei