New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mailing shitshow #1739

Closed
wants to merge 1 commit into
base: development
from

Conversation

Projects
None yet
5 participants
@haneefmubarak
Copy link
Contributor

haneefmubarak commented Jul 19, 2013

It isn't just Librelist that is a shitshow, but rather mailing lists in general

mailing shitshow
It isn't just Librelist that is a shitshow, but rather mailing lists in general
@ethomson

This comment has been minimized.

Copy link
Member

ethomson commented Jul 19, 2013

Well if it's a shitshow maybe we should just get rid of that section entirely then, eh?

@ben

This comment has been minimized.

Copy link
Member

ben commented Jul 19, 2013

Is a mailing list necessary? I mean we have several forums already:

  • This repository for code-related stuff
  • IRC and StackOverflow for asking questions and general discussion

I guess the only thing we're missing is bigger-picture discussions, like in a forum. The maintainers have met in person several times over the last year to do this sort of thing, but we don't have a good online solution for that. Is it worth it to host an entire mailing list just for that?

@martinwoodward

This comment has been minimized.

Copy link
Member

martinwoodward commented Jul 19, 2013

Thanks @haneefmubarak this PR prompted me to give the README and CONTRIBUTING a bit of a spring clean to highlight how we actually communicate now. Hopefully makes more sense now. Closing out this PR if that's ok.

@haneefmubarak

This comment has been minimized.

Copy link
Contributor

haneefmubarak commented Jul 21, 2013

@martinwoodward Yeah that works. Always happy to help! :)

@scunz

This comment has been minimized.

Copy link
Contributor

scunz commented Jul 27, 2013

Maybe I'm a little late to this party, but this seems to me to be a good place to come up with this one: I've been involved with using/enhancing libgit2 for about 1 year now. It's a good product and it's even getting better every now and then.
However, there's one concern (probably more a gut feeling) that I could never really get rid of: It always looked to me like there is much discussion and decision-making that is backgrounded somewhere and not done in public or even publicly available.
What I mean is: Take any 200 libgit2 issues and read them. You'll be surprised how often someone "needs to talk to other folks" (Half time even without a following summary of results) or "this was decided at xyz" (Without a summary of the xyz-meeting being available).

I know that mostly 2 companies are in charge of libgit2. Because of that, I tend to agree in general that a mailing list would probably not be the best medium for better communication.
But I also know that GitHub uses their secret campfire chat rooms for communication (Which by itself isn't bad with all the integration you guys talk about). But would it be too big a demand to ask for a proxy (even one way would already be cool) between the libgit2-Campfire room and the public IRC room on freenode?

@haneefmubarak

This comment has been minimized.

Copy link
Contributor

haneefmubarak commented Jul 27, 2013

+1 to the above.

Personally though, I feel like it would be better to simply conduct meetings in an additional public IRC room on freenode setup so that only selected users may chat, while others may only listen.

@haneefmubarak haneefmubarak deleted the haneefmubarak:patch-1 branch Oct 17, 2013

@haneefmubarak haneefmubarak referenced this pull request Mar 15, 2014

Closed

Better communication? #8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment