Hi, Discord does not have message history limit but has its own cons like lack of threads.
Personally I think such chat apps are not designed to have technical discussions that require voting or/and have final decision. Also registering requirement is IMHO blocker since all discussions and decisions should be publicly available as-is, without need to create any account. But on the other hand I agree that mailing list / google group isn't friendly and should be changed. I think that enabling Issues feature in https://github.com/php-fig/fig-standards (or creating https://github.com/php-fig/discussions for that purpose) could solve the problem - use Pull Requests for PSRs and other technical things that require code changes, use issues for general discussions. That way: - anyone could read all discussions without having Github account - anyone registered could join discussion (unless configured other way in the settings) - discussion history would be available - with help of some conventions (emoji reactions) there could be some voting system Alternative could be self-hosted system like Jira (free for open source → https://www.atlassian.com/software/views/open-source-license-request) that could be extended with plugins to help managing stuff. But this probably would be overkill, Github should be enough. czwartek, 12 listopada 2020 o 11:02:11 UTC+1 [email protected] napisał(a): > Hi, > This is my personal opinion, and not as secretary. > > I understand that the mailing list might be not the ideal, Slack might > bring more people to talk, but the fact that after some time/messages you > lose the history of the conversations is a no go. > It should be always possible to track the history of a decision. > > I'm not familiar with discord, does it have the same issue? > > > Asmir > > On Mon, 9 Nov 2020 at 18:19, Zachary Quintana <[email protected]> wrote: > >> I'm new to this project, so go easy please. I searched through the group >> history and I saw that back in 2016 someone proposed moving the the group >> discourse to one of those chat apps as the primary tool. I can see why that >> might not be the best idea. That said, I'd to see what anyone here thinks >> of moving from IRC to one those. It certainly would be much easier than >> trying to use IRC. Also it seems like the IRC chat is largely dead. No one >> seems to be active on that server. As an alternative would the community >> here consider opening a slack/discord/gitter chat as an alternative to IRC? >> Either way. I think you could expect to see a lot more participation if you >> were using one of those. >> >> -- >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/php-fig/5968cf0b-90bd-4803-9b34-e173738f3c59n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/php-fig/5968cf0b-90bd-4803-9b34-e173738f3c59n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/7505862d-b7a4-4e01-b7a1-ee08e64e1caen%40googlegroups.com.
