kik on Nostr: npub1vuj6r…pmr6e (I'm contributing to that feature, reacting to the discussion on ...
npub1vuj6rlfvarx0ajldz9rehzgt40ve09dj0603m20syx2h5xpqgd7qrpmr6e (npub1vuj…mr6e)
(I'm contributing to that feature, reacting to the discussion on HN here as I don't have an account there)
I really don't understand why people keep opposing this with email workflow. We can have both. 🤷
The only software I use nearly as much as vim is mutt, I would totally dig being able to contribute with email. But I also know this makes me an outlier. AP based merge requests is not for people like me (who will find their way anyway), it's for people not comfortable with git and patching. That is, beginner developers or even ~gasp~ non developers. We (the FOSS projects maintainers) want everyone to be able to contribute, if they want to. And we need choices - ideally transparently interoperable ones. No need to oppose the various options to impose our preferences on others.
#activitypub #gitlab #forgefed
(I'm contributing to that feature, reacting to the discussion on HN here as I don't have an account there)
I really don't understand why people keep opposing this with email workflow. We can have both. 🤷
The only software I use nearly as much as vim is mutt, I would totally dig being able to contribute with email. But I also know this makes me an outlier. AP based merge requests is not for people like me (who will find their way anyway), it's for people not comfortable with git and patching. That is, beginner developers or even ~gasp~ non developers. We (the FOSS projects maintainers) want everyone to be able to contribute, if they want to. And we need choices - ideally transparently interoperable ones. No need to oppose the various options to impose our preferences on others.
#activitypub #gitlab #forgefed