You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@diversity.apache.org by Daniel Gruno <hu...@apache.org> on 2021/07/07 10:45:34 UTC
Re: [Lazy consensus] request a VM for CLC for Apache projects
On 07/06/2021 19.48, Rich Bowen wrote:
>
>
> On 6/6/21 8:04 AM, Daniel Gruno wrote:
>> (switching to the new list)
>>
>> The VM is up and running at https://clc.diversity.apache.org/ and has
>> ASF Oauth implemented, so any committer can make use of this service.
>>
>> I have added a few projects to try things out, seems to work.
>>
>> I suppose we should communicate this to all projects, so they may make
>> use of it?
>>
>
>
> That would be awesome.
>
> I wonder, however, if we could take some time to craft an introductory
> message, so that this is received as intended. Having endured more than
> one round of hostility towards this kind of tooling (Why are you forcing
> us to make these changes?! Are you the word police now?! This is
> Orwellian!!!) I find that a gentle introduction, with carefully chosen
> words setting expectations, and explaining the default words that are
> scanned for, would go a lot way towards heading off some of the vitriol.
>
> And, yes, I'm volunteering to draft and/or edit such a message.
>
Gentle ping then ;D
I tried elsewhere to import all of ASF's git repos, and - website repos
aside - it looks like that's a 90 minute job to scan through, so we
could potentially just have all repositories ready for when we announce,
OR we can have it be opt-in. I'm not sure what the best approach is?
>
>
>> On 06/06/2021 12.12, Daniel Gruno wrote:
>>> Going to request a VM today :)
>>>
>>> On 01/06/2021 15.26, Daniel Gruno wrote:
>>>> As stated before, I'm asking for lazy consensus on requesting a VM
>>>> for setting up CLC for Apache projects. We'll probably have this
>>>> work via OAuth.
>>>>
>>>> No one is required to +1 this, but feel free. or -1 if you have a
>>>> reason.
>>>>
>>>> For completeness, the requested specs are:
>>>>
>>>> 3 or 4 cores
>>>> 8GB memory
>>>> 150GB disk space
>>>> Ubuntu 20.04 with python3, httpd and mod_md for a TLS cert.
>>>>
>>>>
>>>> With regards,
>>>> Daniel.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: diversity-unsubscribe@apache.org
>>>> For additional commands, e-mail: diversity-help@apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: diversity-unsubscribe@apache.org
>>> For additional commands, e-mail: diversity-help@apache.org
>>>
>>
>
Re: [Lazy consensus] request a VM for CLC for Apache projects
Posted by Rich Bowen <rb...@rcbowen.com>.
On 7/7/21 6:45 AM, Daniel Gruno wrote:
> On 07/06/2021 19.48, Rich Bowen wrote:
>>
>>
>> On 6/6/21 8:04 AM, Daniel Gruno wrote:
>>> (switching to the new list)
>>>
>>> The VM is up and running at https://clc.diversity.apache.org/ and has
>>> ASF Oauth implemented, so any committer can make use of this service.
>>>
>>> I have added a few projects to try things out, seems to work.
>>>
>>> I suppose we should communicate this to all projects, so they may
>>> make use of it?
>>>
>>
>>
>> That would be awesome.
>>
>> I wonder, however, if we could take some time to craft an introductory
>> message, so that this is received as intended. Having endured more
>> than one round of hostility towards this kind of tooling (Why are you
>> forcing us to make these changes?! Are you the word police now?! This
>> is Orwellian!!!) I find that a gentle introduction, with carefully
>> chosen words setting expectations, and explaining the default words
>> that are scanned for, would go a lot way towards heading off some of
>> the vitriol.
>>
>> And, yes, I'm volunteering to draft and/or edit such a message.
>>
>
> Gentle ping then ;D
>
> I tried elsewhere to import all of ASF's git repos, and - website repos
> aside - it looks like that's a 90 minute job to scan through, so we
> could potentially just have all repositories ready for when we announce,
> OR we can have it be opt-in. I'm not sure what the best approach is?
Oh, right, I was going to write something. I'll try to get that done today.
I was out yesterday, but saw your messages that you'd imported all of
those repos.
--
Rich Bowen - rbowen@rcbowen.com
@rbowen
Fwd: [Lazy consensus] request a VM for CLC for Apache projects
Posted by Craig Russell <ap...@gmail.com>.
Hi,
I'm now convinced that we will save time in the long run if we just change the name of our main branch from "master" to "main" sooner than later.
Any discussion? Volunteers?
Craig
> On 08/07/2021 18.25, Rich Bowen wrote:
>> On 7/7/21 6:45 AM, Daniel Gruno wrote:
>>> On 07/06/2021 19.48, Rich Bowen wrote:
>>>>
>>>>
>>>> On 6/6/21 8:04 AM, Daniel Gruno wrote:
>>>>> (switching to the new list)
>>>>>
>>>>> The VM is up and running at https://clc.diversity.apache.org/ <https://clc.diversity.apache.org/> and has ASF Oauth implemented, so any committer can make use of this service.
>>>>>
>>>>> I have added a few projects to try things out, seems to work.
>>>>>
>>>>> I suppose we should communicate this to all projects, so they may make use of it?
>> I drafted something here: https://hackmd.io/Scig_0a0R4K0_sADiQCJdA <https://hackmd.io/Scig_0a0R4K0_sADiQCJdA>
>
> Looks great, +1 to sending it out to projects :)
>
> Related, all ASF repositories have been cloned to our VM and scanned once. Projects can log in via ASF OAuth and make adjustments to scan criteria as needed. The scanner runs once every 24 hours.
> On 7/9/21 10:44 PM, Craig Russell wrote:
>> Before this gets out of hand, I have to object to flagging "master" as a git branch name without any other context like "slave".
>
> Pragmatically speaking, you have a choice here. It seems pretty clear to me, having been at the center of this discussion for almost a year now, that the industry *is* going to settle on removing this usage of the word master. So you (we) can choose to flag it now, or we can wait a few years and be out of step with the rest of the conversation.
>
> Kind of like how we resisted having a code of conduct for so many years, and then just did it because it was embarrassing not to.
>
> Or we can choose to be leaders.
>
> Yes, there's an argument to be made that "master" is fine in context Z but is a problem in context Q. I have been part of this conversation dozens of times, at least. But ... why? This specific case is easier to remediate than almost any of the other ones - you change a branch name, and you spend an hour updating your tooling. It is by far the easiest win in this entire effort. Unlike, say, altering function names that are based on libraries that are based on IETF standards.
>
> --
> Rich Bowen - rbowen@rcbowen.com <ma...@rcbowen.com>
> @rbowen
>
> Begin forwarded message:
>
> From: Rich Bowen <rb...@rcbowen.com>
> Subject: Re: [Lazy consensus] request a VM for CLC for Apache projects
> Date: July 12, 2021 at 11:30:31 AM PDT
> To: Craig Russell <ap...@gmail.com>
> Cc: dev@diversity.apache.org
>
>
>
> On 7/12/21 2:18 PM, Craig Russell wrote:
>> Hi Rich,
>> You have convinced me. We can either ignore this while the rest of the industry moves on or deal with it now. Either way, I doubt that the arc of thinking will come back to "this usage is just fine".
>> Still, I'd like to say that no one here is going to force PMCs to act now. It is entirely up to each project if and when they change.
>
> Absolutely. Not only is it not the Apache way, we couldn't compel them to do this even if we wanted to. Indeed, the projects I have already talked to (5 or 6, with my work hat on) have been roughly split between, "yes, we need to address this," and "This isn't a priority for us."
>
>> The nice thing about the tool is that it allows projects to focus on those items that are important to them.
>
> Yeah, the ability to configure which keywords they want to look at is really important for the way that our projects self-govern.
>
> --
> Rich Bowen - rbowen@rcbowen.com
> @rbowen
Craig L Russell
clr@apache.org
Re: [Lazy consensus] request a VM for CLC for Apache projects
Posted by Daniel Gruno <hu...@apache.org>.
On 29/07/2021 21.19, Matt Sicker wrote:
> Hey, do we still want to send out any form of announcement for this?
Yeah, I think we're just stalled a bit due to availability :)
>
> On Mon, Jul 12, 2021 at 1:30 PM Rich Bowen <rb...@rcbowen.com> wrote:
>>
>>
>>
>> On 7/12/21 2:18 PM, Craig Russell wrote:
>>> Hi Rich,
>>>
>>> You have convinced me. We can either ignore this while the rest of the industry moves on or deal with it now. Either way, I doubt that the arc of thinking will come back to "this usage is just fine".
>>>
>>> Still, I'd like to say that no one here is going to force PMCs to act now. It is entirely up to each project if and when they change.
>>
>> Absolutely. Not only is it not the Apache way, we couldn't compel them
>> to do this even if we wanted to. Indeed, the projects I have already
>> talked to (5 or 6, with my work hat on) have been roughly split between,
>> "yes, we need to address this," and "This isn't a priority for us."
>>
>>> The nice thing about the tool is that it allows projects to focus on those items that are important to them.
>>
>> Yeah, the ability to configure which keywords they want to look at is
>> really important for the way that our projects self-govern.
>>
>> --
>> Rich Bowen - rbowen@rcbowen.com
>> @rbowen
Re: [Lazy consensus] request a VM for CLC for Apache projects
Posted by Matt Sicker <bo...@gmail.com>.
Hey, do we still want to send out any form of announcement for this?
On Mon, Jul 12, 2021 at 1:30 PM Rich Bowen <rb...@rcbowen.com> wrote:
>
>
>
> On 7/12/21 2:18 PM, Craig Russell wrote:
> > Hi Rich,
> >
> > You have convinced me. We can either ignore this while the rest of the industry moves on or deal with it now. Either way, I doubt that the arc of thinking will come back to "this usage is just fine".
> >
> > Still, I'd like to say that no one here is going to force PMCs to act now. It is entirely up to each project if and when they change.
>
> Absolutely. Not only is it not the Apache way, we couldn't compel them
> to do this even if we wanted to. Indeed, the projects I have already
> talked to (5 or 6, with my work hat on) have been roughly split between,
> "yes, we need to address this," and "This isn't a priority for us."
>
> > The nice thing about the tool is that it allows projects to focus on those items that are important to them.
>
> Yeah, the ability to configure which keywords they want to look at is
> really important for the way that our projects self-govern.
>
> --
> Rich Bowen - rbowen@rcbowen.com
> @rbowen
Re: [Lazy consensus] request a VM for CLC for Apache projects
Posted by Rich Bowen <rb...@rcbowen.com>.
On 7/12/21 2:18 PM, Craig Russell wrote:
> Hi Rich,
>
> You have convinced me. We can either ignore this while the rest of the industry moves on or deal with it now. Either way, I doubt that the arc of thinking will come back to "this usage is just fine".
>
> Still, I'd like to say that no one here is going to force PMCs to act now. It is entirely up to each project if and when they change.
Absolutely. Not only is it not the Apache way, we couldn't compel them
to do this even if we wanted to. Indeed, the projects I have already
talked to (5 or 6, with my work hat on) have been roughly split between,
"yes, we need to address this," and "This isn't a priority for us."
> The nice thing about the tool is that it allows projects to focus on those items that are important to them.
Yeah, the ability to configure which keywords they want to look at is
really important for the way that our projects self-govern.
--
Rich Bowen - rbowen@rcbowen.com
@rbowen
Re: [Lazy consensus] request a VM for CLC for Apache projects
Posted by Craig Russell <ap...@gmail.com>.
Hi Rich,
You have convinced me. We can either ignore this while the rest of the industry moves on or deal with it now. Either way, I doubt that the arc of thinking will come back to "this usage is just fine".
Still, I'd like to say that no one here is going to force PMCs to act now. It is entirely up to each project if and when they change.
The nice thing about the tool is that it allows projects to focus on those items that are important to them.
Thanks for your perspective,
Craig
> On Jul 12, 2021, at 5:32 AM, Rich Bowen <rb...@rcbowen.com> wrote:
>
>
>
> On 7/9/21 10:44 PM, Craig Russell wrote:
>> Before this gets out of hand, I have to object to flagging "master" as a git branch name without any other context like "slave".
>
> Pragmatically speaking, you have a choice here. It seems pretty clear to me, having been at the center of this discussion for almost a year now, that the industry *is* going to settle on removing this usage of the word master. So you (we) can choose to flag it now, or we can wait a few years and be out of step with the rest of the conversation.
>
> Kind of like how we resisted having a code of conduct for so many years, and then just did it because it was embarrassing not to.
>
> Or we can choose to be leaders.
>
> Yes, there's an argument to be made that "master" is fine in context Z but is a problem in context Q. I have been part of this conversation dozens of times, at least. But ... why? This specific case is easier to remediate than almost any of the other ones - you change a branch name, and you spend an hour updating your tooling. It is by far the easiest win in this entire effort. Unlike, say, altering function names that are based on libraries that are based on IETF standards.
>
> --
> Rich Bowen - rbowen@rcbowen.com
> @rbowen
Craig L Russell
clr@apache.org
Re: [Lazy consensus] request a VM for CLC for Apache projects
Posted by Rich Bowen <rb...@rcbowen.com>.
On 7/9/21 10:44 PM, Craig Russell wrote:
> Before this gets out of hand, I have to object to flagging "master" as a git branch name without any other context like "slave".
Pragmatically speaking, you have a choice here. It seems pretty clear to
me, having been at the center of this discussion for almost a year now,
that the industry *is* going to settle on removing this usage of the
word master. So you (we) can choose to flag it now, or we can wait a few
years and be out of step with the rest of the conversation.
Kind of like how we resisted having a code of conduct for so many years,
and then just did it because it was embarrassing not to.
Or we can choose to be leaders.
Yes, there's an argument to be made that "master" is fine in context Z
but is a problem in context Q. I have been part of this conversation
dozens of times, at least. But ... why? This specific case is easier to
remediate than almost any of the other ones - you change a branch name,
and you spend an hour updating your tooling. It is by far the easiest
win in this entire effort. Unlike, say, altering function names that are
based on libraries that are based on IETF standards.
--
Rich Bowen - rbowen@rcbowen.com
@rbowen
Re: CLC scanner adjustments - (WAS: Re: [Lazy consensus] request a VM
for CLC for Apache projects)
Posted by Matt Sicker <bo...@gmail.com>.
I think the modern term for that would be “active/active” (as opposed to
active/passive cluster failover). A master/master architecture is opposed
to a master/slave one, and the recommended updates for that depend on the
actual details of the underlying algorithm (a lot of people use the M/S
naming scheme regardless if it fits properly; not all distributed systems
work like that). It’s why I’ve seen the term replaced with: main, trunk,
controller, primary, leader, manager, etc., depending on the actual context.
On Sat, Jul 10, 2021 at 13:19 Craig Russell <ap...@gmail.com> wrote:
> Hi Daniel,
>
> Thanks for the details. I found the setting that allows the project to
> exclude "master" from the flagged word list where we want it to be.
>
> The DB JDO project use this to describe the relationship between github
> and gitbox:
> The ASF operates a dual master system for repositories that use Git as
> their primary version
>
> Do you know if this phrasing is now best practice in Apache?
>
> Thanks,
> Craig
>
> > On Jul 10, 2021, at 12:05 AM, Daniel Gruno <hu...@apache.org> wrote:
> >
> > On 10/07/2021 04.44, Craig Russell wrote:
> >> Before this gets out of hand, I have to object to flagging "master" as
> a git branch name without any other context like "slave".
> >
> > There are different opinions on how rigorously to track the word
> 'master' in the various communities, I think it best to leave it up to
> projects how they wish to handle this.
> >
> > The scanner comes with a default behavior that is the same for each
> repository and slightly overzealous, but can be tailored for each repo at
> any time. What we're seeing right now is that default behavior. I have
> found personally that it's best to start with a wide net and then narrow it
> down manually by adjusting the parameters.
> >
> > If a project decides they either don't want to track that word in a
> branch/url context, or don't want to track it altogether, they are free to
> make those adjustments. They can also omit certain files (or file types)
> from the scans.
> >
> > For instance, if a project wishes to exclude the word 'master' if it
> appears inside a URL, they could add something like \bhttps?://.*master.*\b
> to the exclude context list. Or you can remove the word from the context
> list entirely if you are certain you don't have any issues with the word.
> >
> > With regards,
> > Daniel.
> >
> >> Craig
> >>> On Jul 9, 2021, at 5:05 AM, Daniel Gruno <hu...@apache.org> wrote:
> >>>
> >>> On 08/07/2021 18.25, Rich Bowen wrote:
> >>>> On 7/7/21 6:45 AM, Daniel Gruno wrote:
> >>>>> On 07/06/2021 19.48, Rich Bowen wrote:
> >>>>>>
> >>>>>>
> >>>>>> On 6/6/21 8:04 AM, Daniel Gruno wrote:
> >>>>>>> (switching to the new list)
> >>>>>>>
> >>>>>>> The VM is up and running at https://clc.diversity.apache.org/ and
> has ASF Oauth implemented, so any committer can make use of this service.
> >>>>>>>
> >>>>>>> I have added a few projects to try things out, seems to work.
> >>>>>>>
> >>>>>>> I suppose we should communicate this to all projects, so they may
> make use of it?
> >>>> I drafted something here: https://hackmd.io/Scig_0a0R4K0_sADiQCJdA
> >>>
> >>> Looks great, +1 to sending it out to projects :)
> >>>
> >>> Related, all ASF repositories have been cloned to our VM and scanned
> once. Projects can log in via ASF OAuth and make adjustments to scan
> criteria as needed. The scanner runs once every 24 hours.
> >> Craig L Russell
> >> clr@apache.org
> >
>
> Craig L Russell
> clr@apache.org
>
>
Re: CLC scanner adjustments - (WAS: Re: [Lazy consensus] request a VM
for CLC for Apache projects)
Posted by Craig Russell <ap...@gmail.com>.
Hi Daniel,
Thanks for the details. I found the setting that allows the project to exclude "master" from the flagged word list where we want it to be.
The DB JDO project use this to describe the relationship between github and gitbox:
The ASF operates a dual master system for repositories that use Git as their primary version
Do you know if this phrasing is now best practice in Apache?
Thanks,
Craig
> On Jul 10, 2021, at 12:05 AM, Daniel Gruno <hu...@apache.org> wrote:
>
> On 10/07/2021 04.44, Craig Russell wrote:
>> Before this gets out of hand, I have to object to flagging "master" as a git branch name without any other context like "slave".
>
> There are different opinions on how rigorously to track the word 'master' in the various communities, I think it best to leave it up to projects how they wish to handle this.
>
> The scanner comes with a default behavior that is the same for each repository and slightly overzealous, but can be tailored for each repo at any time. What we're seeing right now is that default behavior. I have found personally that it's best to start with a wide net and then narrow it down manually by adjusting the parameters.
>
> If a project decides they either don't want to track that word in a branch/url context, or don't want to track it altogether, they are free to make those adjustments. They can also omit certain files (or file types) from the scans.
>
> For instance, if a project wishes to exclude the word 'master' if it appears inside a URL, they could add something like \bhttps?://.*master.*\b to the exclude context list. Or you can remove the word from the context list entirely if you are certain you don't have any issues with the word.
>
> With regards,
> Daniel.
>
>> Craig
>>> On Jul 9, 2021, at 5:05 AM, Daniel Gruno <hu...@apache.org> wrote:
>>>
>>> On 08/07/2021 18.25, Rich Bowen wrote:
>>>> On 7/7/21 6:45 AM, Daniel Gruno wrote:
>>>>> On 07/06/2021 19.48, Rich Bowen wrote:
>>>>>>
>>>>>>
>>>>>> On 6/6/21 8:04 AM, Daniel Gruno wrote:
>>>>>>> (switching to the new list)
>>>>>>>
>>>>>>> The VM is up and running at https://clc.diversity.apache.org/ and has ASF Oauth implemented, so any committer can make use of this service.
>>>>>>>
>>>>>>> I have added a few projects to try things out, seems to work.
>>>>>>>
>>>>>>> I suppose we should communicate this to all projects, so they may make use of it?
>>>> I drafted something here: https://hackmd.io/Scig_0a0R4K0_sADiQCJdA
>>>
>>> Looks great, +1 to sending it out to projects :)
>>>
>>> Related, all ASF repositories have been cloned to our VM and scanned once. Projects can log in via ASF OAuth and make adjustments to scan criteria as needed. The scanner runs once every 24 hours.
>> Craig L Russell
>> clr@apache.org
>
Craig L Russell
clr@apache.org
CLC scanner adjustments - (WAS: Re: [Lazy consensus] request a VM for
CLC for Apache projects)
Posted by Daniel Gruno <hu...@apache.org>.
On 10/07/2021 04.44, Craig Russell wrote:
> Before this gets out of hand, I have to object to flagging "master" as a git branch name without any other context like "slave".
There are different opinions on how rigorously to track the word
'master' in the various communities, I think it best to leave it up to
projects how they wish to handle this.
The scanner comes with a default behavior that is the same for each
repository and slightly overzealous, but can be tailored for each repo
at any time. What we're seeing right now is that default behavior. I
have found personally that it's best to start with a wide net and then
narrow it down manually by adjusting the parameters.
If a project decides they either don't want to track that word in a
branch/url context, or don't want to track it altogether, they are free
to make those adjustments. They can also omit certain files (or file
types) from the scans.
For instance, if a project wishes to exclude the word 'master' if it
appears inside a URL, they could add something like
\bhttps?://.*master.*\b to the exclude context list. Or you can remove
the word from the context list entirely if you are certain you don't
have any issues with the word.
With regards,
Daniel.
>
> Craig
>
>> On Jul 9, 2021, at 5:05 AM, Daniel Gruno <hu...@apache.org> wrote:
>>
>> On 08/07/2021 18.25, Rich Bowen wrote:
>>> On 7/7/21 6:45 AM, Daniel Gruno wrote:
>>>> On 07/06/2021 19.48, Rich Bowen wrote:
>>>>>
>>>>>
>>>>> On 6/6/21 8:04 AM, Daniel Gruno wrote:
>>>>>> (switching to the new list)
>>>>>>
>>>>>> The VM is up and running at https://clc.diversity.apache.org/ and has ASF Oauth implemented, so any committer can make use of this service.
>>>>>>
>>>>>> I have added a few projects to try things out, seems to work.
>>>>>>
>>>>>> I suppose we should communicate this to all projects, so they may make use of it?
>>> I drafted something here: https://hackmd.io/Scig_0a0R4K0_sADiQCJdA
>>
>> Looks great, +1 to sending it out to projects :)
>>
>> Related, all ASF repositories have been cloned to our VM and scanned once. Projects can log in via ASF OAuth and make adjustments to scan criteria as needed. The scanner runs once every 24 hours.
>
> Craig L Russell
> clr@apache.org
>
>
Re: [Lazy consensus] request a VM for CLC for Apache projects
Posted by Craig Russell <ap...@gmail.com>.
Before this gets out of hand, I have to object to flagging "master" as a git branch name without any other context like "slave".
Craig
> On Jul 9, 2021, at 5:05 AM, Daniel Gruno <hu...@apache.org> wrote:
>
> On 08/07/2021 18.25, Rich Bowen wrote:
>> On 7/7/21 6:45 AM, Daniel Gruno wrote:
>>> On 07/06/2021 19.48, Rich Bowen wrote:
>>>>
>>>>
>>>> On 6/6/21 8:04 AM, Daniel Gruno wrote:
>>>>> (switching to the new list)
>>>>>
>>>>> The VM is up and running at https://clc.diversity.apache.org/ and has ASF Oauth implemented, so any committer can make use of this service.
>>>>>
>>>>> I have added a few projects to try things out, seems to work.
>>>>>
>>>>> I suppose we should communicate this to all projects, so they may make use of it?
>> I drafted something here: https://hackmd.io/Scig_0a0R4K0_sADiQCJdA
>
> Looks great, +1 to sending it out to projects :)
>
> Related, all ASF repositories have been cloned to our VM and scanned once. Projects can log in via ASF OAuth and make adjustments to scan criteria as needed. The scanner runs once every 24 hours.
Craig L Russell
clr@apache.org
Re: [Lazy consensus] request a VM for CLC for Apache projects
Posted by Matt Sicker <bo...@gmail.com>.
Looks pretty good to me, too.
On Fri, Jul 9, 2021 at 7:05 AM Daniel Gruno <hu...@apache.org> wrote:
>
> On 08/07/2021 18.25, Rich Bowen wrote:
> >
> >
> > On 7/7/21 6:45 AM, Daniel Gruno wrote:
> >> On 07/06/2021 19.48, Rich Bowen wrote:
> >>>
> >>>
> >>> On 6/6/21 8:04 AM, Daniel Gruno wrote:
> >>>> (switching to the new list)
> >>>>
> >>>> The VM is up and running at https://clc.diversity.apache.org/ and
> >>>> has ASF Oauth implemented, so any committer can make use of this
> >>>> service.
> >>>>
> >>>> I have added a few projects to try things out, seems to work.
> >>>>
> >>>> I suppose we should communicate this to all projects, so they may
> >>>> make use of it?
> >
> > I drafted something here: https://hackmd.io/Scig_0a0R4K0_sADiQCJdA
> >
>
> Looks great, +1 to sending it out to projects :)
>
> Related, all ASF repositories have been cloned to our VM and scanned
> once. Projects can log in via ASF OAuth and make adjustments to scan
> criteria as needed. The scanner runs once every 24 hours.
Re: [Lazy consensus] request a VM for CLC for Apache projects
Posted by Daniel Gruno <hu...@apache.org>.
On 08/07/2021 18.25, Rich Bowen wrote:
>
>
> On 7/7/21 6:45 AM, Daniel Gruno wrote:
>> On 07/06/2021 19.48, Rich Bowen wrote:
>>>
>>>
>>> On 6/6/21 8:04 AM, Daniel Gruno wrote:
>>>> (switching to the new list)
>>>>
>>>> The VM is up and running at https://clc.diversity.apache.org/ and
>>>> has ASF Oauth implemented, so any committer can make use of this
>>>> service.
>>>>
>>>> I have added a few projects to try things out, seems to work.
>>>>
>>>> I suppose we should communicate this to all projects, so they may
>>>> make use of it?
>
> I drafted something here: https://hackmd.io/Scig_0a0R4K0_sADiQCJdA
>
Looks great, +1 to sending it out to projects :)
Related, all ASF repositories have been cloned to our VM and scanned
once. Projects can log in via ASF OAuth and make adjustments to scan
criteria as needed. The scanner runs once every 24 hours.
Re: [Lazy consensus] request a VM for CLC for Apache projects
Posted by Rich Bowen <rb...@rcbowen.com>.
On 7/7/21 6:45 AM, Daniel Gruno wrote:
> On 07/06/2021 19.48, Rich Bowen wrote:
>>
>>
>> On 6/6/21 8:04 AM, Daniel Gruno wrote:
>>> (switching to the new list)
>>>
>>> The VM is up and running at https://clc.diversity.apache.org/ and has
>>> ASF Oauth implemented, so any committer can make use of this service.
>>>
>>> I have added a few projects to try things out, seems to work.
>>>
>>> I suppose we should communicate this to all projects, so they may
>>> make use of it?
I drafted something here: https://hackmd.io/Scig_0a0R4K0_sADiQCJdA
--
Rich Bowen - rbowen@rcbowen.com
@rbowen