> The only solid argument against a mailing list is "it's old," which is not an argument.
My argument list means nothing? > "Signing up for yet another forum tool to remember a password for" is not my cup of tea, either. So it goes. Nobody remembers password today, use password manager. Even in this case, make login via GitHub (OAuth). So what do you think about Discussions on GitHub (beta)? On Saturday, August 15, 2020 at 5:44:00 PM UTC+3 Larry Garfield wrote: > On Sat, Aug 15, 2020, at 9:05 AM, Philippe Cloutier wrote: > > Le 2020-08-14 à 06:31, daniel...@gmail.com a écrit : > > > > The problem isn't that discussions are not GitHub's main feature. > The problem is that [to my knowledge] GitHub does not offer discussion > forums. > > > > > > "Issues" (if enabled) may act like discussion forum. You don't need > make pull request in this case. > > > > > > Issues are a collection of issue reports. They do enable discussion, > > but only about issue reports. If a discussion topic is not an issue, > > "Issues" will not help any more than Pull requests will help discussing > > topics other than "pull requests". > > > > > > > > > Anyway, it's just cheap solution if open dedicated forum on > php-fig.org is a problem. > > > > > > I see. I must say your proposal is unclear then. It helps for proposals > > to be concrete and to use examples, but it is important to be clear > > about what is merely an example or a possibility. > > > > I would recommend you create a new clearer topic choosing a clearer > > Subject (either do not mention GitHub in the title, or only mention it > > parenthetically). And by the way, on a more general note, I think it > > would be best to have this forum alongside other PHP forums, so it may > > be more efficient to start by getting php.net to adopt "real" web > > forums. There are several web forum engines based on PHP engines, > > although free software PHP engines haven't evolved much in recent years > > to my knowledge. > > I've recently done a survey of available OSS forum software for work. My > conclusion is that they can all be grouped into one of a few categories: > Bad, Worse, Terrible, and Effectively Abandoned. "Just use a forum" is a > non-option. > > For all their issues, mailing lists are still the least-bad option for > open-threaded-discussions. There's a searchable permanent archive, it's > easy to subscribe/unsubscribe, anyone can read, join, and post, there's a > million possible clients, it's easy to filter so a folder so you can ignore > it most of the time... The only solid argument against a mailing list is > "it's old," which is not an argument. > > "Signing up for yet another forum tool to remember a password for" is not > my cup of tea, either. So it goes. > > 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. Some have set up a custom > mailing list for themselves; some have done everything via regular hangout > meetings. Some have used extensive GitHub PRs. Most have used a little of > all of the above. Working Groups are deliberately allowed to use "whatever > works." > > Moving discussions from a public mailing list to a public unthreaded HTML > form does not offer any meaningful benefits, and would only serve to make > discussion more difficult. > > This discussion comes up periodically and always ends in the same place: > There's no actual value to changing other than a couple of people don't > like using old tech, which is not sufficient for all of the other downsides > finding something else would have. > > --Larry Garfield > -- 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/edf6c285-69f3-4db5-9566-b4f50a04e27dn%40googlegroups.com.
