Hey Folks. Am 05.03.24 um 00:11 schrieb dan...@daniil.it:
If I have learned one thing in decades of software development and emergency management it is:The VSC part from github (hosting our code), can very easily be ported. Issues, discussions etc can not.With the ongoing enshittification of most of the Internet due to advertising and tracking, we'd be negligent not hosting and owning our own content (including our issue tracker, but that ship has sailed now).PHP actually recently moved from a self-hosted VCS to github due to a hack that compromised php's source code, moving back to a self-hosted instance seems like a downgrade.However, if that's being discussed, it can be done properly, i.e. with a self-hosted gitlab instance, which also provides issues, projects, CI, basically the full devops experience, that would be the perfect chance to also move the mailing list and php wiki to gitlab (which is how many FOSS projects work currently, I.e. wayland, xorg, mesa, pipewire, asahi use the gitlab.freedesktop.org gitlab instance, arch linux has its own gitlab instance (which is also used for RFCs)).Email has been around for half a century. Will things like Slack, Discord, and the like still be operational and allow access to our archives in another 25 years? I'm almost certain it won't be.No one is proposing to move the issue tracker to discord, slack or telegram: those are messengers, and should not be used as support forums for such a major language, mainly because they're non-indexable.Regards, Daniil Gentili
Never change a process in an emergencyProcesses are there to help in emergencies. They provide stable ways to process information. And in any case, any decission taken in an emergency situation will be influenced by the wish to fastly overcome the emergency and not by the wish to optimize the process.
Also discussions about whether a process is necessary or not or needs to be changed wastes resources that can help solve the problem.
That said: It is fine to discuss whether the mailinglists are the best thing to foster communication about the development of PHP - when the mailinglist is working fine.
When the mailinglist is broken (and it'S not that that happens every other week) the only discussion is either about the development of PHP or how one can help to fix the issue.
Some things didn't go well. Some things did go well. We (meaning those that fixed and still fix the issues at hand) might come together for a retrospective once everything works fine again and see what can be improved to help avoid such a situation the next time.
Once that is done and everything works fine I am looking forward to an RFC proposing better ways to communicate about all the aspects of developing PHP in a worldwide distributed community of volunteers.
Cheers
Andreas
--
,,,
(o o)
+---------------------------------------------------------ooO-(_)-Ooo-+
| Andreas Heigl |
| mailto:andr...@heigl.org N 50°22'59.5" E 08°23'58" |
| https://andreas.heigl.org |
+---------------------------------------------------------------------+
| https://hei.gl/appointmentwithandreas |
+---------------------------------------------------------------------+
| GPG-Key: https://hei.gl/keyandreasheiglorg |
+---------------------------------------------------------------------+
OpenPGP_signature.asc
Description: OpenPGP digital signature
