[Biopython] How many of you are on Slack?

[Ivan Gregoretti]

Migrating to Google groups sounds very appealing to this Biopython reader.

Thank you.

Ivan


On Mon, Jun 28, 2021 at 11:00 AM João Rodrigues
<j.p.g.l.m.rodrigues at gmail.com> wrote:
>
> My "issue" with having announcements in a blog or twitter or so (only) is that you have to make an active effort to read them as a user. I see your point with feeds (Feedly user here too) but it's an extra layer (in my opinion), and the more layers, the less involvement.
>
> An email is "passive": you subscribe and that's it, gets delivered to your inbox. It's also the lowest common denominator in terms of tech in the sense that everyone has/uses email.
>
> Migrating to a Google group should be simple too, you can (could at least) subscribe automatically all the members of the current list so that there's no action necessary on their end.
>
>
> A segunda, 28/06/2021, 10:38, Peter Cock <p.j.a.cock at googlemail.com> escreveu:
>>
>> My goal is both reduce OBF maintenance, and better connect with the
>> Biopython community - it seems this mailing list is  sub-optimal on
>> both front.
>>
>> As to consolidation/relocation, I was thinking blog (read only
>> announcements),  free-tier Slack (real-time interactions including
>> user support), and Github (dev support and discussions). But maybe
>> with the slow decline in news reader popularity (I personally have
>> used Feedly ever since Google Reader was dropped), you're right and
>> there is still a role for some kind of email based announcements list?
>>
>> (Note that some of the smaller non-public OBF mailing lists have for
>> some time forwarded to private Google Groups; your suggestion would
>> not be such a big upheaval)
>>
>> Peter
>>
>> On Mon, Jun 28, 2021 at 3:27 PM João Rodrigues
>> <j.p.g.l.m.rodrigues at gmail.com> wrote:
>> >
>> > I understand your points.
>> >
>> > If the purpose is to reduce the load on OBF to maintain and host all these things, what about creating a single mailing list on google groups (free, archived, easy to use) and use that for announcements and an initial point of contact? You could then combine google group (announcements), free-tier Slack (real-time user support), and Github (dev support) and cover pretty much all corners with remote hosted tools that archive the most important conversations.
>> >
>> > Never used Gitter or other chat platforms.
>
> _______________________________________________
> Biopython mailing list  -  Biopython at biopython.org
> https://mailman.open-bio.org/mailman/listinfo/biopython