added google groups links

[RBhupi]

[freemansw1]

Note that I changed the target here to be the 1.4.0 release candidate, which results in the changes to main to be merged into RC_v1.4.0 branch.

[freemansw1]

I think advertising these mailing lists is a good idea. I'm not sure that I have been using them correctly, actually. I had forgotten about the separate tobac-users list. I think we should consider getting rid of that list, actually, given how small it is (12 members vs 24 in the more general tobac list), and then create a mailing list for developers specifically.

[codecov[bot]]

Codecov Report

Base: 36.22% // Head: 36.22% // No change to project coverage :thumbsup:

Coverage data is based on head (df904a7) compared to base (720ef18). Patch has no changes to coverable lines.

Additional details and impacted files

@@            Coverage Diff             @@
##           RC_v1.4.0     #162   +/-   ##
==========================================
  Coverage      36.22%   36.22%           
==========================================
  Files             10       10           
  Lines           2120     2120           
==========================================
  Hits             768      768           
  Misses          1352     1352           

Flag	Coverage Δ
unittests	36.22% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

[RBhupi]

Yeah. I thought of adding these links after the SciPy talk. I think the lists are evolving differently than we initially thought. We also have https://groups.google.com/g/tobac-developers group.

On Tue, Jul 19, 2022 at 3:57 PM Sean Freeman @.***> wrote:

I think advertising these mailing lists is a good idea. I'm not sure that I have been using them correctly, actually. I had forgotten about the separate tobac-users list. I think we should consider getting rid of that list, actually, given how small it is (12 members vs 24 in the more general tobac list), and then create a mailing list for developers specifically.

— Reply to this email directly, view it on GitHub https://github.com/tobac-project/tobac/pull/162#issuecomment-1189542714, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASYW6GBFCXYIZNUBN7PF6LVU4JDBANCNFSM54BJCE4A . You are receiving this because you authored the thread.Message ID: @.***>

[RBhupi]

I can open the tobac group for all to join and delete or hide tobac-users group if that sounds good. Let's talk about it at the next meeting.

[JuliaKukulies]

I was not even aware that we had these three different groups to be honest, but I think your suggestion to get rid of tobac-users sounds good @freemansw1 @RBhupi.

Would it not be easier if we stick to Slack instead of communicating on different platforms? But I am not sure how well the email integration in Slack works, as it is certainly useful to be able to send an email to a specific subgroup or let users contact us via mail if they do not have a Slack account.

[freemansw1]

Would it not be easier if we stick to Slack instead of communicating on different platforms? But I am not sure how well the email integration in Slack works, as it is certainly useful to be able to send an email to a specific subgroup or let users contact us via mail if they do not have a Slack account.

I like Slack, but I think people really have to buy in to use it. I agree that we should cross-post everything there (which I haven't been great about!), but I agree we need to keep e-mail as it's a much lower barrier of entry.

[JuliaKukulies]

Ok yes, I agree to keep the mailing lists. But good point from @RBhupi that we already have the one for developers, so probably no need to create another.

[freemansw1]

After discussion in the developers' meeting today, I think the plan is to stick with the developers and main tobac mailing lists and get rid of the users one. I think we should also advertise the slack in the readme.

[freemansw1]

@RBhupi I think after discussion today, the plan is to advertise the two mailing lists, but not to put the slack link on the readme given spam concerns. We'll instead start distributing the slack link with releases, beginning with v1.4 (because I forgot today).

So, that just leaves switching around the mailing lists. Are you happy to update the PR, or do you want us to do so?

[freemansw1]

OK, I updated the mailing list links and added a brief slack discussion. Re-requesting review from @JuliaKukulies and requesting review from @snilsn.

[RBhupi]

Thanks Sean! The other group with only a few members is now deactivated.

On Mon, Oct 31, 2022 at 10:09 AM JuliaKukulies @.***> wrote:

@.**** approved this pull request.

Excellent, thanks @freemansw1 https://github.com/freemansw1 !

— Reply to this email directly, view it on GitHub https://github.com/tobac-project/tobac/pull/162#pullrequestreview-1162049236, or unsubscribe https://github.com/notifications/unsubscribe-auth/AASYW6DN7ASUHVWW5FRYUKDWF7OMBANCNFSM54BJCE4A . You are receiving this because you were mentioned.Message ID: @.***>