In the olden days, a FOSS (Free/Open Source Software) project typically had:
-
Juanlureplied to Jan Wildeboer 😷:krulorange: last edited by
@jwildeboer How is requesting a GitHub account "very high price"? Or put another way: is your solution to go back to *exclusively* IRC and mailing lists, or to have *both* systems to give people choice (and place the burden on maintainers)?
-
Qreplied to Jan Wildeboer 😷:krulorange: last edited by
@jwildeboer well... it is **a** workflow... which has nothing in comparison to mailing list based contribution.
GitHub/GitLab's PR workflow is an absolute disaster/nightmare for per-commit/patch review. Gerrit does that a bit better with patchsets but it gets difficult to read pretty quickly, even with topics.
GitLab/GitHub is just NOT necessarily compatible with some project's workflow.
I actually wrote a multiple pages long email on why no GH/GL for Yocto a while back, maybe I should put it in an article so it's easier to explain everything instead of being limited to a few 100s of characters at once
-
Jan Wildeboer 😷:krulorange:replied to Juanlu last edited by
@astrojuanlu When GitHub started using my code to feed it to their Copilot LLM with now way for me to opt-out, I decided the price was too high. But that's just me. I still have a GitHub account, but moved my code to Codeberg and my own Forgejo instance.
-
Jan Wildeboer 😷:krulorange:replied to Q last edited by
@0leil Please do! I will also start a blogpost on how Discord etc mess up communication in a project (IMHO) by mixing synchronous and asynchronous communication together in a way that isn't helpful but, again IMHO, damaging to the flow.
-
HankBreplied to Jan Wildeboer 😷:krulorange: last edited by
There was also source code and patches published to Usenet. I don't recall how much took place there but it was generally open and accessible. (Some newsgroups were moderated.)
-
Jan Wildeboer 😷:krulorange:replied to HankB last edited by
@HankB Before we had the web, we also had weird solutions like ftp to e-mail gateways, where you would get tarballs from an ftp server as chunked content delivered to your email inbox
-
🔗 David Sommersethreplied to Jan Wildeboer 😷:krulorange: last edited by
s/things changed dramatically/it went downhill ever since/
-
Miah Johnsonreplied to Doggie :neofox_snug: :therian: last edited by
@lunareclipse @jwildeboer IRC doesn't need history, it's not a documentation service its a place to hold discussions. You don't walk into a discussion with people and request that they give you a log of past discussions. It's ephemeral on purpose. If something important happens it can be logged and made into documentation or a issue etc.
IRC is also perfectly usable on mobile, the problem lies in frequent disconnects but let's admit that mobile users ignore irc 99% of the time anyway.
-
Jan Wildeboer 😷:krulorange:replied to 🔗 David Sommerseth last edited by
-
It's not just young people. I'm 56 and I don't care for the "submit patches only by email" rule either.
I've done it, but I don't like it.
The one project I follow that had that rule got a Github mirror, that's the only thing I use now.
They like their plaintext email; they can have it. I will happily live in *this* century.
-
Jan Wildeboer 😷:krulorange:replied to Larry Clapp last edited by
-
Larry Clappreplied to Jan Wildeboer 😷:krulorange: last edited by
I apologize, I didn't think you meant that.
I don't know if @0leil thought you did, either; they just brought it up, talking about "young people", and I offered a data point from an old fart.
-
Jan Wildeboer 😷:krulorange:replied to Jan Wildeboer 😷:krulorange: last edited by
Seeing how quite some commenters (want to?) take the wrong conclusions from my thread: I am all for the GitHub/gitlab/forgejo/codeberg based approach of managing issues, PRs, releases in "modern" ways. It made drive-by contributions so much easier! I am however not sure if discord et al are better for asynchronous communication and feel that mailing lists with public archives were a superior approach that we gave up on prematurely. HTH! 6/6
-
Miah Johnsonreplied to Jan Wildeboer 😷:krulorange: last edited by
@jwildeboer IRC wins for discussions by not requiring anything. You want to chat? Click the JavaScript client link and chat. You can install a optional client if you plan to chat often. You don't need to register or provide any personal details.
Matrix/Discord etc all fail with onboarding and high hardware requirements for a client. I can sign into IRC using any computer with networking, even obsolete hardware. NetBSD on a Apple llc, IRC on a palm pilot. Take your pick.
-
tessaraktreplied to Jan Wildeboer 😷:krulorange: last edited by
@jwildeboer What about an issue tracker?
-
Jan Wildeboer 😷:krulorange:replied to tessarakt last edited by
@tessarakt Many (smaller) projects didn't have one. It was often handled on the mailing lists. Setting up a full-blown bugzilla was quite a task. Sorceforge was (like GitHub nowadays) another solution to that.
-
Proxfox Virtual Environment 🦊replied to Miah Johnson last edited by
@miah @lunareclipse @jwildeboer yes but once you've answered the same question for the 500th time you do kinda want full chat search & history
-
Jan Wildeboer 😷:krulorange:replied to Proxfox Virtual Environment 🦊 last edited by
@tay It's called an FAQ and should be publicly available on the homepage of the project, IMHO @miah @lunareclipse
-
Miah Johnsonreplied to Proxfox Virtual Environment 🦊 last edited by
@tay @lunareclipse @jwildeboer There is this advanced technology called a "FAQ" and posting the link in the channel topic, or presenting it to the chatter who needs it bypasses this issue.
-
Proxfox Virtual Environment 🦊replied to Miah Johnson last edited by
@miah @lunareclipse @jwildeboer It 100% does NOT bypass the issue. I've placed error messages in an application where I put the instructions to resolve the issue in the message box body.
I still got hundreds of emails with the title of the message box copied and pasted in. If a lot of users aren't going to read the 2 lines of text in a modal box, they're not going out of their way to read the FAQ.
You need to give users every possible reason to not resort to messaging you, and chat history is one of them.