Listing forks to invite to the community

[selfhoster1312]

The idea here is to prevent splitting into many little forks with just a few patches applied, and to build a proper community.

Here's a list of some forks to invite over, and maybe propose to become maintainers and/or admins of the matterbridge-org community:

• https://github.com/bibanon/matterbridge/ (issue)
• https://scm.dersco.re/forks/matterbridge.git/ (mail sent)
• https://git.linux.ucla.edu/lug/matterbridge (mail sent)
• https://github.com/selfhoster1312/matterbridge/tree/upload-url-2 (that's me)
• https://github.com/tippl/matterbridge/ (mail sent)
• https://github.com/Wohlstand/matterbridge (mail sent)

Not exactly forks, but related projects we'd like to invite:

• https://scm.dersco.re/utils/matterpuppeter.git IRC puppeting bridge built on matterbridge API (mail sent)

[nosovk]

I'm using version that is based on https://github.com/tippl/matterbridge it supports new slack integrations

[poVoq]

Probably also worth notifying some people that made some recent unmerged upstream PRs?

[selfhoster1312]

Probably also worth notifying some people that made some recent unmerged upstream PRs?

Maybe before this we should get the forked repo started? Get some better docs and contribution guidelines, then we can probably invite more people?

[poVoq]

Dunno, it might make equally sense to try to get feedback from more people now and directly involve them before setting up the fork.

[selfhoster1312]

Dunno, it might make equally sense to try to get feedback from more people now and directly involve them before setting up the fork.

Sure, go ahead! I just thought pointing people to an empty "issues-only" repository where there is no docs/code to review doesn't make a lot of sense… Do you think we could get both started in parallel? If so i'll just fork the repository in this org, and start opening pull requests so people can start reviewing things.

[poVoq]

I am currently not at my PC, mobile only. Maybe towards the end of this week.

[selfhoster1312]

I am currently not at my PC, mobile only. Maybe towards the end of this week.

Do you have a hard "no" against me starting the forked repo and opening PRs in the meantime?

[poVoq]

No, please go ahead if you have time and find it worthwhile already.

[poVoq]

Not really a fork, but might be a useful patch to port: https://gitlab.com/gnoppix/matterbridge/-/commit/714a2ad7303f0d7b51b8b7f6c5f86f02a99c3524

[poVoq]

There is also https://github.com/PoshCode/matterbridge

by @Jaykul who might be interested in joining this effort here to make a community fork.

[Jaykul]

We badly need a team-based project ... and I'd be happy to re-fork from here, if only to drive traffic in the right direction.

To be clear though, I had zero go experience before I made that fork on Saturday 😉 -- but I'm happy to help with CI and builds, which is actually why I made our fork, I needed a container image to fix our Slack bridge ... and nobody else seemed to be publishing them.

I did make one change you should definitely merge ... to let it connect to slack channels on it's own, after I realized the new slack "app" was going to need to be invited into every single channel otherwise 😜 The slack code desperately needs to be cleansed of all the "legacy" stuff that doesn't even work anymore. 😒

Oh, and may I suggest ... merging the wiki/docs (back) into the repo(s)? The current situation is that when people add features to the bots, there's no simultaneous update of the documentation for how to set them up, what tokens go where, and which OAuth scopes you need, etc.

[poVoq]

Hi and welcome. Merging the docs into the repo is already done, and there is an open PR for CI improvements by @selfhoster1312 here: https://github.com/matterbridge-org/matterbridge/pulls

@selfhoster1312 wants to modernize the CI and testing infra before we start backporting the various existing patches. I agree that this is a good approach, but personally lack experience with the relevant Github systems, so can't really contribute much on that side.

If you could review those open PRs that would be much apprechiated though.

[selfhoster1312]

I did make one change you should definitely merge ... to let it connect to slack channels on it's own

Where is this code? Can you maybe open a pull request here? Besides, would you like to be registered as a maintainer for the Slack backend? Even with limited golang experience, your testing and Slack knowledge could prove useful. See #1

Oh, and may I suggest ... merging the wiki/docs (back) into the repo(s)?

That's actually already done! It's the first (and so far only) PR we merged: matterbridge-org/matterbridge#1 Now there is no separate wiki with sparse/stale information. Everything lives in the same repository and the docs are expected to be updated at the same time as the code. Does this satisfy you? I'm aware there's much room for improvement in the docs but i believe the situation is already better than before (PRs welcome).

[poVoq]

bibanon/matterbridge#25

Interesting large PR to replace the Matrix library with an actively maintained one.

[poVoq]

https://github.com/h4ks-com/mattferbridge/

Has a few fixes for IRC. @matheusfillipe would you be willing to upstream them here?