> *I think chat is great for ad hoc discussions and meetings, but when it’s time to make any decisions, everything (including ideas discussed in chat) needs to move to a medium that can support transparency and openness. Right now, that’s mailing lists.*
Github issues / pull requests *ARE* transparent (don't require account to read), searchable, offer structurized history (while chat have rather linear and mixed), so all requirements set up by mailing list are met. All of this while providing much more readability (code syntax, formatting), they don't include all the noise from quoted previous messages or signatures (rolling eyes emote), can link issues between each other (with automatic references in issues' timeline), every user can set his own notifications policy (on project level) or subscribe to single issue/PR.. Mailing lists are so raw that in 2020 many people won't use them "just because". As for IIRC - I don't know how many people use it and how many discussions had been taken there, but honestly I doubt that there is as much discussion as would be inapropriate for Github issue. I don't say IIRC should be abandoned completely, people can talk there as much as they want but there shouldn't be taken any serious technical decisions. IIRC should be a place for friendly talk (like Symfony's Slack) and even if some serious discussion is started there, final result should be documented elsewhere. And by "elsewhere" I don't mean mailing list. środa, 16 grudnia 2020 o 17:41:27 UTC+1 and...@heigl.org napisał(a): > Am 16.12.20 um 17:38 schrieb Ben Ramsey: > > My $0.02 as one who lurks on the mailing lists: > > > > Chat programs, whether it be Slack or Discord or Rocket.Chat or > > Mattermost or whatever, are inherently bad at transparency, which is > > paramount to open source. They’re difficult to search, do not provide an > > easy means to browse through the history, and they almost always require > > an account to access the history. Mailing lists, on the other hand, > > provide search, archival browsing, and all discussions can be made > public. > > > > I think chat is great for ad hoc discussions and meetings, but when it’s > > time to make any decisions, everything (including ideas discussed in > > chat) needs to move to a medium that can support transparency and > > openness. Right now, that’s mailing lists. > > I second that! > > And IIRC this has been a discussion on this list several times and so > far the result was always to stay with the mailinglist format! > > Cheers > > Andreas > -- > ,,, > (o o) > +---------------------------------------------------------ooO-(_)-Ooo-+ > | Andreas Heigl | > | mailto:and...@heigl.org N 50°22'59.5" E 08°23'58" | > | https://andreas.heigl.org | > +---------------------------------------------------------------------+ > | https://hei.gl/appointmentwithandreas | > +---------------------------------------------------------------------+ > > -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/34473daf-758c-435a-a043-47c5bed53c11n%40googlegroups.com.
