Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: How do you talk to your GitHub community?

news.ycombinator.com

Post reply on HN
Print view View original

61–70 of 70 posts

Re: Ask HN: How do you talk to your GitHub community?

#61

Post by mabynogy »

fundamental wrote: post #60
mabynogy wrote: post #56

Earlier quoted context omitted.

> I wish there was a formula for making things more attractive to contribute to (in both the short and long term), but it's a fiddly process. I'm trying to elaborate something for that. On way I see is to reduce the entry level as much as possible. I deduce that a project aiming a lot of contributors should be heterogeneous (contributors can choose their favorite language)and shouldn't have a single build system (int…

That might work or it could backfire. With more build systems and more languages, then you can easily end up in the category that someone needs to know all of them to make meaningful changes. If you have people staying in their own part of the codebase it's easy to imagine significant bitrot occurring over time.

I imagine software isolated in vms.

Many people could do the same thing or overlap with someone's else project. It would allow projects to compete.

Re: Ask HN: How do you talk to your GitHub community?

#63

Post by fundamental »

mabynogy wrote: post #61
fundamental wrote: post #60

Earlier quoted context omitted.

That might work or it could backfire. With more build systems and more languages, then you can easily end up in the category that someone needs to know all of them to make meaningful changes. If you have people staying in their own part of the codebase it's easy to imagine significant bitrot occurring over time.

I imagine software isolated in vms. Many people could do the same thing or overlap with someone's else project. It would allow projects to compete.

Interesting. That's a radically different view on what a project should strive for than my own. My own FLOSS work focuses on getting work closer to the system's metal in order to have a responsive low-latency/realtime configuration (realtime being in the realtime signal processing sense).

In this area in particular people doing the same things results in reasonable breadth of work, but insufficient depth. So plenty of options, but all of them not good enough to compete with larger development teams.

Re: Ask HN: How do you talk to your GitHub community?

#64

Post by mabynogy »

fundamental wrote: post #63
mabynogy wrote: post #61

Earlier quoted context omitted.

I imagine software isolated in vms. Many people could do the same thing or overlap with someone's else project. It would allow projects to compete.

Interesting. That's a radically different view on what a project should strive for than my own. My own FLOSS work focuses on getting work closer to the system's metal in order to have a responsive low-latency/realtime configuration (realtime being in the realtime signal processing sense). In this area in particular people doing the same things results in reasonable breadth of work, but insufficient depth. So plenty o…

I've seen your website. It's really fascinating.

Re: Ask HN: How do you talk to your GitHub community?

#66

Post by KajMagnus »

ThatHNGuy wrote: post #25
TonnyGaric wrote: post #4

What about Slack?

The free plan allows you only to keep the latest 10K messages. And it tends to be messy

And (IMO) it's sooo annoying that everything is hidden behind a login screen. I usually don't signup, just to see what might be behind.

Here're open source Slack alternatives for public communities, no login screens: https://spectrum.chat and https://www.talkyard.io (I'm developing it).

(Rocket Chat & Mattermost & Zulip are other alternatives, all require login to see what's there? )

Re: Ask HN: How do you talk to your GitHub community?

#67

Post by blocked_again »

KajMagnus wrote: post #66
ThatHNGuy wrote: post #25

Earlier quoted context omitted.

The free plan allows you only to keep the latest 10K messages. And it tends to be messy

And (IMO) it's sooo annoying that everything is hidden behind a login screen. I usually don't signup, just to see what might be behind. Here're open source Slack alternatives for public communities, no login screens: https://spectrum.chat and https://www.talkyard.io (I'm developing it). (Rocket Chat & Mattermost & Zulip are other alternatives, all require login to see what's there? )

Many organization and companies don't want outsiders to see what is happening due to privacy and security issues. Anyway, there is a PR opened for Zulip which allows people to see the content of public streams without logging in. It's up to the administrators to decide which streams would be public to users which are not logged in.

https://github.com/zulip/zulip/pull/8135

Re: Ask HN: How do you talk to your GitHub community?

#68

Post by KajMagnus »

blocked_again wrote: post #67
KajMagnus wrote: post #66

Earlier quoted context omitted.

And (IMO) it's sooo annoying that everything is hidden behind a login screen. I usually don't signup, just to see what might be behind. Here're open source Slack alternatives for public communities, no login screens: https://spectrum.chat and https://www.talkyard.io (I'm developing it). (Rocket Chat & Mattermost & Zulip are other alternatives, all require login to see what's there? )

Many organization and companies don't want outsiders to see what is happening due to privacy and security issues. Anyway, there is a PR opened for Zulip which allows people to see the content of public streams without logging in. It's up to the administrators to decide which streams would be public to users which are not logged in. https://github.com/zulip/zulip/pull/8135

Interesting to know, thanks for mentioning :- ) B.t.w. I like Zulip's threads.

A thought: What if Zulip, during installation, let the admin choose if things should be public or hidden-behind-login, by default? E.g. useful for open source projects

Re: Ask HN: How do you talk to your GitHub community?

#69

Post by [deleted] »

KajMagnus wrote: post #68
blocked_again wrote: post #67

Earlier quoted context omitted.

Many organization and companies don't want outsiders to see what is happening due to privacy and security issues. Anyway, there is a PR opened for Zulip which allows people to see the content of public streams without logging in. It's up to the administrators to decide which streams would be public to users which are not logged in. https://github.com/zulip/zulip/pull/8135

Interesting to know, thanks for mentioning :- ) B.t.w. I like Zulip's threads. A thought: What if Zulip, during installation, let the admin choose if things should be public or hidden-behind-login, by default? E.g. useful for open source projects

[deleted]

Re: Ask HN: How do you talk to your GitHub community?

#70

Post by tabbott »

KajMagnus wrote: post #68
blocked_again wrote: post #67

Earlier quoted context omitted.

Many organization and companies don't want outsiders to see what is happening due to privacy and security issues. Anyway, there is a PR opened for Zulip which allows people to see the content of public streams without logging in. It's up to the administrators to decide which streams would be public to users which are not logged in. https://github.com/zulip/zulip/pull/8135

Interesting to know, thanks for mentioning :- ) B.t.w. I like Zulip's threads. A thought: What if Zulip, during installation, let the admin choose if things should be public or hidden-behind-login, by default? E.g. useful for open source projects

We're actually working on something like this in Zulip; it's advertised as "coming soon" at http://zulipchat.com/for/open-source
Post reply on HN