From: Elijah Newren <firstname.lastname@example.org> To: "Coghlan, Owen R CTR USARMY PEO EIS (USA)" <email@example.com> Cc: "firstname.lastname@example.org" <email@example.com>, "Pegram, George A JR CIV USARMY SEC (USA)" <firstname.lastname@example.org> Subject: Re: Possible impacts on Git due to COVID19 Date: Fri, 10 Apr 2020 10:47:27 -0700 [thread overview] Message-ID: <CABPp-BFWnfr0kc3Od4XC2ZmJ94k3p+oSmbz2k1+GyY+S-OVwig@mail.gmail.com> (raw) In-Reply-To: <FA375405E0773E4095AD3784C67AE52214DA4BC3@UMECHPA7A.easf.csd.disa.mil> On Fri, Apr 10, 2020 at 7:04 AM Coghlan, Owen R CTR USARMY PEO EIS (USA) <email@example.com> wrote: > > Good Morning, > > My name is Owen Coghlan and I'm the Cyber Security Analyst for Defensive Cyber Operations, Cyber Platforms and Systems, located at Fort Belvoir supporting the Army. Are there any possible impacts or slowdowns due to COVID19? Impacts such as supply chain, coders, and shipping, where your software product is concerned. This information would be greatly appreciated. I'm not sure what kind of "supply chain or shipping" you are envisioning would even be applicable to git. I'm also not even sure why slowdowns would matter -- you get new features slower? It's also not at all clear whether we have an overall slowdown; not to me at least. Some developers who contribute may have less time to do so (e.g. due to the sudden need to homeschool kids), but others might have more time. While some git developers may have worked in the same company and collaborated in person, overall, git development has always been done electronically and remotely and has contributors from many companies as well as hobbyists. If someone had a reason to be interested in this kind of answer beyond "My gut answer right now is I don't think so", they could try counting patch submissions to the mailing list or the number of new commits entering various branches and compare it to previous release cycles. That information is publically available for all to see, after all. But digging out this information seems like work for someone who feels that documenting the answer provides some kind of utility. If you just want a rough gut estimate, I don't perceive any slowdowns.
prev parent reply other threads:[~2020-04-10 17:47 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-10 13:54 Coghlan, Owen R CTR USARMY PEO EIS (USA) 2020-04-10 17:47 ` Elijah Newren [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://vger.kernel.org/majordomo-info.html * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CABPp-BFWnfr0kc3Od4XC2ZmJ94k3p+oSmbz2k1+GyY+S-OVwig@mail.gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Possible impacts on Git due to COVID19' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://80x24.org/mirrors/git.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).