> On Nov 19, 2023, at 9:03 PM, Trond Myklebust <trondmy@xxxxxxxxxxxxxxx> wrote: > > On Mon, 2023-11-20 at 01:07 +0000, Chuck Lever III wrote: >> >> >>> On Nov 19, 2023, at 7:16 PM, Trond Myklebust >>> <trondmy@xxxxxxxxxxxxxxx> wrote: >>> >>> On Sat, 2023-11-18 at 15:45 -0500, Steve Dickson wrote: >>>> >>>> >>>> On 11/18/23 12:03 PM, Chuck Lever III wrote: >>>>> >>>>>> On Nov 18, 2023, at 11:49 AM, Trond Myklebust >>>>>> <trondmy@xxxxxxxxxxxxxxx> wrote: >>>>>> >>>>>> On Sat, 2023-11-18 at 16:41 +0000, Chuck Lever III wrote: >>>>>>> >>>>>>>> On Nov 18, 2023, at 1:42 AM, Cedric Blancher >>>>>>>> <cedric.blancher@xxxxxxxxx> wrote: >>>>>>>> >>>>>>>> On Fri, 17 Nov 2023 at 08:42, Cedric Blancher >>>>>>>> <cedric.blancher@xxxxxxxxx> wrote: >>>>>>>>> >>>>>>>>> How owns bugzilla.linux-nfs.org? >>>>>>>> >>>>>>>> Apologies for the type, it should be "who", not "how". >>>>>>>> >>>>>>>> But the problem remains, I still did not get an account >>>>>>>> creation >>>>>>>> token >>>>>>>> via email for *ANY* of my email addresses. It appears >>>>>>>> account >>>>>>>> creation >>>>>>>> is broken. >>>>>>> >>>>>>> Trond owns it. But he's already showed me the SMTP log from >>>>>>> Sunday night: a token was sent out. Have you checked your >>>>>>> spam folders? >>>>>> >>>>>> I'm closing it down. It has been run and paid for by me, but >>>>>> I >>>>>> don't >>>>>> have time or resources to keep doing so. >>>>> >>>>> Understood about lack of resources, but is there no-one who can >>>>> take over for you, at least in the short term? Yanking it out >>>>> without warning is not cool. >>>>> >>>>> Does this announcement include git.linux-nfs.org >>>>> <http://git.linux-nfs.org/> and >>>>> wiki.linux-nfs.org <http://wiki.linux-nfs.org/> as well? >>>>> >>>>> As this site is a long-time community-used resource, it would >>>>> be fair if we could come up with a transition plan if it truly >>>>> needs to go away. >>>> >>>> If you need resources and time... Please reach out... >>>> >>>> This is a community... I'm sure we can figure something out. >>>> But please turn it back on. >>>> >>> >>> So far, I've heard a lot of 'we should', and a lot of 'we could'. >>> >>> What I have yet to hear are the magic words "I volunteer to help >>> maintain these services". >> >> I volunteer to help. I can do as much or as little as you prefer. >> And I volunteer to lead an effort to either: >> >> a) find a replacement issue tracking service, or >> >> b) find a way to archive the content of the bugzilla if we agree >> there is no more need for a bugzilla.linux-nfs. >> >> Or both. >> >> There is no way for us to know how much effort it takes if you >> suffer in silence, my friend. > > The point is that email has evolved over the 18 years since I set up > the very first linux-nfs.org. I have not had time to keep up with the > requirements of adding support for DMARC, SPF, etc. which is why > Cedric's account setup email is probably in his spam folder, assuming > that the gmail server even accepted it at all. > > Furthermore, both the wikimedia and bugzilla instances are far from > running the most recent code versions and I'm sure there are plenty of > well known security holes etc to exploit. So both code bases have been > needing an upgrade for a while now. > > Finally, the VM itself is still running RHEL/CentOS 7, and I'd like to > see it migrated to a platform that is is still maintained. > > All these tasks would need help from the person (or people?) who > volunteers to maintain the bugzilla + wiki services. Some of them would > need to be 100% owned by that person, and others (like the platform > upgrade) would need a lot of coordination with me. > > IOW: I'm not advocating either way. I can understand wanting to migrate > away from the current setup to something that is maintained by someone > else. However if anyone does wants to take on the job of helping to > maintain the current setup, then they need to know that it will involve > real work. Understood, and accepted. Finding a hosted bugzilla (such as devzing.com <http://devzing.com/>) and migrating the active bugs there would help with all these issues. I haven't yet looked for hosted wiki services, but I'll bet we can handle that in a similar fashion. It is also sensible to have one place for kernel bugs, as you pointed out. It's the upstream user space issues where there is likely still a need for an issue tracker independent of the kernel.org <http://kernel.org/> one. There are links to bugzilla.linux-nfs.org <http://bugzilla.linux-nfs.org/> bugs in the kernel's commit log that we need to continue handling somehow -- a read- only bugzilla instance, if nothing else, might be easy to maintain for that purpose, but there could be other ways to deal with that. -- Chuck Lever
