Open Source

30385 readers

551 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Posts must be relevant to the open source ideology
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago

MODERATORS

[email protected]

Any "tutorial" for using IRC and mailing list? (lemmy.ml)

submitted 6 months ago by [email protected] to c/[email protected]

21 comments fedilink hide all child comments

I'm talking about GNU here.

I just can't seem to figure out on how to use either of them to communicate. IRCs don't save older messages, but instead logs them. And I guess for the same reason, it is impossible to discuss anything in depth.

Mailing list is really hard to read, as it is nowhere similar to forum or tree-style comments. I can't figure out what mailing list to message to.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 2 points 6 months ago (1 children)

Ask if they are open to move to something else /s

[–] [email protected] 2 points 6 months ago (3 children)

I have to be honest, and no offense to GNU folks, but I am really not enjoying this barrier to entry. This cognitive overload is something I'm not comfortable with.

[–] [email protected] -1 points 6 months ago* (last edited 6 months ago) (1 children)

Cognitive overload? From IRC and mailing lists? It makes me doubt whether you'd be able to contribute anything, anyway.

[–] [email protected] 1 points 6 months ago (1 children)

WOW YOU ARE SUCH A NICE PERSON

[–] [email protected] 2 points 6 months ago (1 children)

He's not wrong though. If IRC and mailing lists fall into the too-hard basket, id hate to think of where GNU-style C code falls. Bottom of the too-hard cliff?

[–] [email protected] 2 points 6 months ago

Yes they are wrong. A contribution may consist of "merely" a bug report. Even just asking questions may indicate that the UX or documentation is lacking.

[–] [email protected] 2 points 6 months ago (1 children)

Fun fact the guy behind awk sent in a patch via email cuz he thought git was too complicated or not worth the hassle.

[–] [email protected] 4 points 6 months ago

git was designed to accept patches over email. How else would you do it? man git-send-email

[–] [email protected] 3 points 6 months ago

Understandable. Unfortunately the people in power of those services have to change. There's no other way.