> I think there's a misunderstanding here about how FIG operates. The mailing list is the primary official venue for discussion, but not the only. Most of the actual work on specs happens in Working Groups, and they are free to use whatever tooling they prefer.
The problem is that we have quite good case for PSR (PHP 8 attributes). We had opinions by leaders in static analyzing (PhpStan, psalm, phan) and by author of AOP Go framework that we have something to discuss. However, none of them wants to join this mailing list, some of them had bad experience already (PhpStan). > Moving discussions from a public mailing list to a public unthreaded HTML form https://github.com/vercel/next.js/discussions — this is threaded forum and you can ask GitHub support for that. Also GitHub has team discussions: https://docs.github.com/en/github/building-a-strong-community/about-team-discussions You can make working group as a team there and give us platform for discussions. > does not offer any meaningful benefits Well, "working group" as you said, see the benefits. Instead of bureaucracy, can help us with team discussion or, even better, with org discussions like https://github.com/vercel/next.js/discussions? On Thursday, August 20, 2020 at 7:33:01 PM UTC+3 daniel...@gmail.com wrote: > Exactly! > > On Tuesday, August 18, 2020 at 1:49:08 PM UTC+3 fenn...@gmail.com wrote: > >> >> >> If i may, GitHub has a discussion module which can be enabled for >> organizations >> >> https://docs.github.com/en/github/building-a-strong-community/about-team-discussions >> >> On Wednesday, August 12, 2020 at 1:19:22 AM UTC+1 che...@gmail.com wrote: >> >>> Hi Daniel, >>> >>> Le 2020-08-11 à 11:06, daniel...@gmail.com a écrit : >>> > Hi, >>> > >>> > I noticed that many people really dislike this mailing list. There are >>> > many reasons: >>> > >>> > * PHP community wants to see your GitHub profiles, be more open; >>> > * no sane highlighting of the code (for discussions about code); >>> > * very obsolete messaging system in general: it's like plain text vs >>> > native GUI; >>> > * lack of on mailing lists: emoji system as voting mechanism for >>> > simple voting and for hot discussions where someone asks reasonable >>> > question, but it drowns and nobody sees it (on GitHub it's hard to >>> > avoid question with many 👍 signs); >>> > * GitHub offers diffs for edited comments; >>> > * moderators can tag issues there; >>> > * mailing-list gives worse feedback by PHP community; don't be bad >>> > politicians: that's good when you have better feedback. >>> > >>> > This question was raised not a once if I recall correctly: you planned >>> > to move somewhere like a modern forum. >>> > >>> > Why separate repository in the https://github.com/php-fig group can't >>> > be simple solution? >>> >>> >>> I do not know GitHub much, but I do not understand your suggestion. A >>> GitHub repository is designed to store code, not discussions (nor >>> voting, nor politics). >>> >>> >>> > [...] >>> >>> -- >>> Philippe Cloutier >>> http://www.philippecloutier.com >>> >>> -- 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/64622b42-12a3-45d7-b138-fca9fbe07a2fn%40googlegroups.com.
