search

surge-synthesizer / surge

Synthesizer plug-in (previously released as Vember Audio Surge)
https://surge-synthesizer.github.io/
GNU General Public License v3.0
3.02k stars 386 forks source link

Set up IRC logging #120

Closed jarkkojs closed 5 years ago

jarkkojs commented 5 years ago

Many of the issues are not actually issues/tasks but merely discussions. I think it'd be good idea to set up mailing list. I found this: https://www.freelists.org/. Any other comparable service would be fine too.

jarkkojs commented 5 years ago

One example: https://github.com/kurasu/surge/issues/112

baconpaul commented 5 years ago

I have no objections! If you do this and send a PR to the README.md with appropriate instructions on how to sub and stuff we can sweep that in. And I would join the list!

esaruoho commented 5 years ago

imho this current github-tickets / PRs as conversations is good because anyone can chime in anywhere. if you're not on the mailinglist, you don't know what's going on in there. here you can reference code directly, everyone sees the reference, it can be modified on-the-go. i've found these conversations fruitful and would have a great deal of trouble following them in a mailinglist environment where most of the time there's maybe 2-3 people there as opposed to 4-6. and code-reviewing PRs is pretty important to keep conversant, rather than "if i bump into a bug, i'll post it to the mailinglist, which person x who can fix it bug, doesn't read, it never gets fixed".

i've seen people try to split communication into telegram,slack,discord,signal,whatsapp,facebook groups,phpbb2 forums and it never works - 25% of the people involved adopt it, then it dies, then it hinders communication. here everything is at your fingertips, the repo, the commits, the PRs, the forked repos and their branches, direct linking to everywhere.

granted, i've not seen a github repo this verbose before, but i don't find it confusing, it's just different.

jarkkojs commented 5 years ago

The key problem is that issues get closed. Emails get archived.

jarkkojs commented 5 years ago

I guess I could work out the logging bot to the IRC channel and close this issue :) I'm used to contribute to the open source projects where Github is not involved. Everything, including patches, are sent to the mailing list. I'm into that kind of platform than Github but I see your point about split. Don't like Github workflow at all but I can live with it.

jarkkojs commented 5 years ago

Soon to be closed as soon as @esaruoho parts out the channel :) Then I set up ChanServ there and we get logging.

esaruoho commented 5 years ago

@jsakkine i just left the channel

jarkkojs commented 5 years ago

OK, so now I have ChanServ there and I get ops from it so the channel can be rejoined again. I will enable the logging a bit later today.

jarkkojs commented 5 years ago

https://freenode.logbot.info/surgesynth/ there it is.

baconpaul commented 5 years ago

Mind tossing in a pr to update the readme sometime?

jarkkojs commented 5 years ago

Done :)

baconpaul commented 5 years ago

Thanks!!