+1

On Wednesday, November 11, 2020 at 1:52:11 PM UTC-7 [email protected] 
wrote:

> +1 from me as well
>
> Am 11.11.2020 um 21:41 schrieb Mark Waite <[email protected]>:
>
> +1 from me.
>
> On Wed, Nov 11, 2020 at 1:38 PM Oleg Nenashev <[email protected]> wrote:
>
>> Hi all, any additional feedback about the hosting request?
>>
>> Thanks in advance,
>> Oleg
>>
>> On Wednesday, November 11, 2020 at 8:18:43 AM UTC+1 Oleg Nenashev wrote:
>>
>>> It is me who asked for a developer mailing list thread. There is no 
>>> problem with the hosting itself, I can create repos when there is a 
>>> consensus. I asked for a more public process (not so many contributors 
>>> watch HOSTING), because it is a follow-up to the Jenkins Kubernetes 
>>> Operator: Open Governance Proposal 
>>> <https://groups.google.com/g/jenkinsci-dev/c/OA5nb_SAgh0/m/q8SSKE1UAwAJ> 
>>> that 
>>> got stuck due to the lack of public response from Virtus Lab. As discussed 
>>> at the governance board meetings in August and October, hosting a new 
>>> operator is an alternative to getting the upstream 
>>> https://github.com/jenkinsci/kubernetes-operator unblocked. So this 
>>> request basically applies an alternate plan.
>>>  
>>> I am +1 for hosting a new operator, because I see no clear way for 
>>> unblocking https://github.com/jenkinsci/kubernetes-operator. We got 
>>> some private response from Virtus Lab to the Jenkins Board on Oct 16, but I 
>>> have no permission to share it. Although this response is somewhat 
>>> promising, it does not immediately unblocks contributions to the 
>>> repository. There is no public response from Virtus Lab as they intended to 
>>> do, and there is little activity in the repository. Although there is a 
>>> declared intent to introduce changes in November, I am not sure it is . 
>>> Having an alternate repository is how we could unblock contributors while 
>>> we keep communicating with Virtus Lab and trying to unlock the upstream.
>>>
>>> No strong opinion about naming
>>>
>>> Best regards,
>>> Oleg
>>>
>>> On Tuesday, November 10, 2020 at 6:44:15 PM UTC+1 [email protected] 
>>> wrote:
>>>
>>>> You need to open a hosting jira ticket.
>>>>
>>>> https://www.jenkins.io/doc/developer/publishing/requesting-hosting/
>>>>
>>>> And that'll create everything for you (repo, team, etc)
>>>>
>>>>
>>>> On Tue., Nov. 10, 2020, 9:33 a.m. Akram Ben Aissi, <[email protected]> 
>>>> wrote:
>>>>
>>>>> Hi Jenkins Devs,
>>>>>
>>>>> I am delighted to announce the creation of a new Jenkins Operator for 
>>>>> kubernetes under the name "Simple Jenkins Operator".
>>>>>  
>>>>> A kubernetes operator is kubernetes native component that is able to 
>>>>> install, manage and operate applications running in kubernetes.
>>>>>
>>>>> Hence, the Simple Jenkins Operator will provide a simple and 
>>>>> straightforward experience to allow installation, management, upgrade and 
>>>>> backup of Jenkins when it is running in kubernetes.
>>>>>
>>>>> This projects comes into an alternative to the first Jenkins Operator 
>>>>> namely jenkinsci/kubernetes-operator and aims to provide a simpler user 
>>>>> experience by using more kubernetes native component.
>>>>>
>>>>> Our first version will be 0.7.0 and will be compatible with 
>>>>> operator-sdk 1.0.1 .
>>>>> Please, jenkins board member, could you please create a repository 
>>>>> named (jenkinsci/simple-jenkins-operator) so we can push our existing 
>>>>> code 
>>>>> base there.
>>>>>
>>>>> Of course, contributions are welcome, and we really want an open 
>>>>> govervnance for the very start, so any individual or enterprise 
>>>>> contributor 
>>>>> is welcome.
>>>>>
>>>>> greetings
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>>
>>>>> AKRAM BEN AISSI
>>>>>
>>>>> PRINCIPAL SOFTWARE ENGINEER
>>>>>
>>>>>  <https://red.ht/sig>
>>>>>
>>>>> M: +33.6.31.57.08.60 <//+33631570860>       T: @akrambenaissi 
>>>>> <http://twitter.com/akrambenaissi>
>>>>>
>>>>> E: [email protected]    #: Akram      
>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google 
>>>>> Groups "Jenkins Developers" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>> an email to [email protected].
>>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFkVfmPwBguuhsjAsbAOYKRtn287Zf%2BKjT4oFwd6NTQ-wTb%3DBA%40mail.gmail.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAFkVfmPwBguuhsjAsbAOYKRtn287Zf%2BKjT4oFwd6NTQ-wTb%3DBA%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected].
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/3b769e3f-e17f-41c3-838c-9ffed782e1b4n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/3b769e3f-e17f-41c3-838c-9ffed782e1b4n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtE9iwsJ2hfrj2Q0oO6ULJo1oL%2BrrOHO%3DeLUBJc_RQp4ig%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtE9iwsJ2hfrj2Q0oO6ULJo1oL%2BrrOHO%3DeLUBJc_RQp4ig%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/cbf5ca2a-d09e-4e13-8044-1539bb2098e9n%40googlegroups.com.

Reply via email to