Would you like to contribute to a project, but the type of forge is a burden for you?
Tell us where you are, and where you want to contribute to.
Would you like to contribute to a project, but the type of forge is a burden for you?
Tell us where you are, and where you want to contribute to.
@ck
I personally considered some either Git push option so that pushing back to an upstream repo where you don't have permissions automatically creates a pull request (and ideally not even a fork).
I sometimes also wonder why people expect long texts in PRs when commit messages say it all.
~ otto
@jgoerzen
@jgoerzen
I agree, with the exception of the e-mail part.
Email has transitioned from a decentralized "good enough" to a federated mess to a literal cluster fuckery. I really want to have as little to do with it as I can.
@codeberg I may be the weird one that wants git send-email again. There is so much human context switching and unnecessary clicking in the make a fork, clone the fork, hack, push, click the submit PR button, watch for that, delete your fork, etc. cycle. Like, I've already got this cloned, I want to just write a patch and hit a button to send it up. There are so many dead forks on #Github that were made by somebody that just wanted to send in a patch.
@codeberg @ck Putting explanations in PR instead of commit is one of my pet peeves. One of them is an integral part of the repository permanently. The other is fleeting, tied to a service provider, and not well-integrated into tooling. You're exactly on point there.
@jgoerzen @codeberg @ck IME a code comment is often even better. Many times when I'm in a code review discussion and the code doesn't end up changing, the outcome of the discussion is a code comment.
@jgoerzen @codeberg @ck A pet peeve of mine in code reviews is when reviewers ask a question that is clearly answered by the commit message.
@ck @codeberg @jgoerzen yes, this would be great.
Spam and impersonation would be problems to consider - but since commits can already be signed there's lots of opportunity to distinguish commits by 'known' entities from less verifiable sources.
@raboof
> since commits can already be signed [...]
Aaand and wie have come full circle to the email again π
The hurdle of entry needs to be low enough for not-so-tech-savy people to become engaged in it. Any web-of-trust thingy that was supposed to work without a central authority was always anything but.
If we really want this to be an alternatives to send-email, we need it to be as simple as sending email first.
@codeberg
Ideally this would work without the need to create an account at a specific forge.
One of the clear benefits of send-email is that you don't have any need to create a local identity first in order to contribute.
@ck
git-send-email is not a low barrier. Many people don't even know how to configure an email client, because they are used to all those proprietary webmailers from "free of charge, full of tracking" service providers.
Many of them require OAuth, so configuring password-based SMTP access is complicated.
Only because tech-savy people find email easy, this does not mean that anyone knows how to "simply" send an email. without their usual tooling.
Chirp! is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.
All Chirp! content and data are available under the Creative Commons Attribution 3.0 license.