Skip to content
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

Add link to Matrix room #162

Closed
wants to merge 1 commit into from
Closed

Conversation

Anton-Latukha
Copy link

  • You can rephrase as you please.

  • Since Matrix room is alive, list it on Community page.

  • This contact can also be added to Support page, but that is up to main developers.

* You can rephrase as you please.

* Since Matrix room is alive, list it on Community page.

* This contact can also be added to Support page, but that is up to main developers.
@grahamc
Copy link
Member

grahamc commented Sep 13, 2017

One thing I'm not clear on is why have a separate Matrix room, when the IRC channel is bridged?

@Anton-Latukha
Copy link
Author

Anton-Latukha commented Sep 13, 2017

  • That is why I started this PR.
    To inform that community info needs sync.
    And how to route users, is up to the main team.

Since IRC bridged to Matrix, Matrix not really known for now, and IRC is still used. I propose.

  • To say about Matrix first, mention what is bridged with Matrix.

  • And then list IRC, and describe how it is integrated with Matrix, and who lives in IRC.
    In near future people will migrate from it anyway.
    In half a year/year then, it probably gets empty, and IRC room can be gone then.

Also:

  • Subreddit still alive, it can be mentioned for now also.

@edolstra
Copy link
Member

I barely know what Matrix is, so I'm kind of reluctant to declare it as an "official" communication method of the NixOS developer community.

@Anton-Latukha
Copy link
Author

Anton-Latukha commented Sep 13, 2017

Matrix is worth to check-out.

It was brewing for years.
Serverless messaging framework and platform.
Now it blows up, and hype starts around it.

It started to work so good, that main investor stopped funding it, because it became such threat to their business (as I know).

What I know, that Matrix has: IRC, Slack, Telegram, Glitter, Verto bridges, and probably some unofficial also. That mean that people seamlessly in the same chat, and talk together, from IRC to Matrix and back. And they even don't know that they do that.

That is why migration in going to happen fast.

@jagajaga
Copy link
Member

@edolstra this is a great service. It's growing nowadays and it's going to be very popular. I vote to accept it.

@daylightbrightledlight
Copy link

I also vote to accept it.

@samueldr
Copy link
Member

samueldr commented Oct 10, 2018

[triage] While I'm a bit miffed that this is splitting the chat-based community a bit, but that's not important. I will argue that we need closure for this PR: do we publicize the existence of that room on the website or not?

I am neither for or against, but I think this PR should be dealt with. Not that it would be a final word forever and ever, but to reduce the backlog.

@Anton-Latukha
Copy link
Author

Anton-Latukha commented Oct 11, 2018

As always, because nobody provides topic arguments - I am going to argue with myself.

I argued with myself, changed my position, and here is what I deduced:

Why join Matrix-IRC:

Matrix rooms and IRC rooms can be the same space. Due to almost complete transparency.

Why rename "NixOS" channel to "NixOS distribution", and "Nix" channel to "Nix on Linux, macOS":

  1. NixOS distribution and Nix in Linux/macOS questions topics and operations are way different.

  2. For example - I am NixOS administrator, and more-less know installation process of Nix on other Linux distributions now - but I do not fully know or remember CLI ways to use Nix on other distros, because I use NixOS everywhere. And I am not interested to read non-NixOS chats, more-over starters chats for other Linux-distros. But all that is Nix-related.

  3. Mixing NixOS and Nix on Linux creates a collision of methods of application, and confusion for Linux users. I can now go to NixOS room and ask a basic question - an I would get two answers. In terms of how to do it on NixOS and in terms of how to do it on other Linux distributions. Wu wei solution is to make solve collision naturally, by streaming people without rules. NixOS channel is for NixOS. Nix channel is for Nix in Linux distributions, and names must show that.

  4. If NixOS would be sole to "NixOS distribution" - there would be a spacetime-quality-critical mass for quality participation there. And Nix on Linux would be more for community support of traditional DevOps and onboarding a new community Nix* members.

  5. Also, in reality, newcomers to Nix* do not understand the difference between NixOS, Nix package manager, Nix language, Nixpkgs and NixOps, so they can not choose to go to "Nix" or "NixOS" channel, they seems the same for them. But they can go to "Nix on Linux, macOS" if they use Nix there, and "NixOS distributions" if they installed NixOS.

But also remember the first argument.

With all these arguments I see the point of renaming "NixOS" room to "NixOS distribution" pretty much proven.

Why split "NixOS distribution" and "NixOS distribution-dev"

There would be more and more people in this Matrix chatroom. And more and more discussion. And it is needed to split development space with bots workflow, and discussions/questions around NixOS.

What is deduced:

  1. Matrix NixOS room joins NixOS IRC room. And becomes "NixOS distribution". It is a wu wei way to say that it is for NixOS distribution community and contribution, and people with Nix in Linux questions would naturally migrate to Nix channel.
    1.a. If there is already too many people in "NixOS distribution" split it to "NixOS distribution" (aka discussion of NixOS questions) and "NixOS distribution-dev" (aka contribution&working environment is here, contributors talk design/contributions here, GitHub bots send info here).
  2. Matrix Nix room joins Nix IRC room. And becomes "Nix on Linux, macOS". This would be a place to wu wei stream here users of "Nix on non-NixOS". Nix newcomers who try Nix, devs who use Nix on macOS, admins who use Nix on Linux and traditional DevOps who run Kubernetes clusters with Alpine+Nix containers hang-out here and share knowledge. The most enthusiastic NixOS people hang-out here to help people on traditional Linux and macOS.
  3. Core devs have a separate room/means to talk and have more official support. Obviously, this is already true.

@Anton-Latukha
Copy link
Author

I would reorganize the contribution and the main post.
And then we would see what to implement.

@Anton-Latukha
Copy link
Author

Closed due to becoming not relevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants