Re: Discourse as the default communication channel?

[Mark Waite]

I'd like to be part of the test.

On Thu, May 27, 2021 at 2:28 PM 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> The tech it uses can give you pretty live updates, but its designed as a
> forum.
>
> I've sent you a DM on IRC with an invite link for now.
>
>
>
> On Thu, May 27, 2021 at 1:08 PM Slide  wrote:
>
>> I would like access please. Just a question, as I am very unfamiliar with
>> Discourse. Is it a real time communication medium, a la IRC, or something
>> more akin to a forum?
>>
>> On Thu, May 27, 2021 at 11:57 AM 'Olblak' via Jenkins Developers <
>> jenkinsci-dev@googlegroups.com> wrote:
>>
>>> For whoever is interested to participate to the Discourse project,
>>> we started discussing over there as a way to test it and get more
>>> familiar with the tool.
>>> -> https://community.jenkins.io/t/discussion-about-categories/27/12
>>>
>>> Feel free to request an access as I didn't have the time yet to really
>>> investigate the consequences of the different authentication methods.
>>>
>>> On Tue, May 25, 2021, at 8:46 PM, 'Olblak' via Jenkins Developers wrote:
>>> > Hi Bruce,
>>> >
>>> > Thank you for stepping up, you already provided a lot of information
>>> > here.
>>> > And let's not assume we all know everything about discourse as we
>>> > definitely don't.
>>> > As you are interested to help with this project, I'll send you an
>>> > invite to "community.jenkins.io".
>>> >
>>> > As long as we don't have an agreement on the authentication mechanism,
>>> > I'll work on invite-only.
>>> >
>>> > Regarding identifying what we expected from Discourse, Bruce made a
>>> > good statement that discourse is what we want it to be, so here what I
>>> > would like it to solve.
>>> > I would like to easily identify and participate in discussion about
>>> > topics that interested me across different sub-project. So as an
>>> > initial step, Oleg suggestion seems right to me.
>>> >
>>> > On my side, I'll investigate the different authentication options.
>>> > Today during the infrastructure Oleg made a good remark,  we would
>>> like
>>> > to ideally move away from maintaining our Ldap service and we would
>>> > like to offer more alternatives than just using a Github account so
>>> > maybe using Linux foundation accounts would be better.
>>> >
>>> >
>>> > On Tue, May 25, 2021, at 7:16 PM, Matt Sicker wrote:
>>> > > Ha, so I was. Oops!
>>> > >
>>> > > On Tue, 25 May 2021 at 10:32, 'Gavin Mogan' via Jenkins Developers
>>> > >  wrote:
>>> > > >
>>> > > > Matt. It's often a confusion point. Discourse is more like a
>>> form/mailing list type thing. Discord is realtime communication. Sounds
>>> like your describing discord.
>>> > > >
>>> > > > On Tue., May 25, 2021, 6:52 a.m. Matt Sicker, 
>>> wrote:
>>> > > >>
>>> > > >> I’ve never used Discourse outside of video games, but it seems
>>> easier to set up public communities on than Slack or other things we’ve
>>> tried here so far. While in theory I’d prefer something open like Matrix, I
>>> do agree that we should try to minimize the number of services to maintain
>>> ourselves.
>>> > > >>
>>> > > >> On Tue, May 25, 2021 at 07:45 Oleg Nenashev <
>>> o.v.nenas...@gmail.com> wrote:
>>> > > >>>
>>> > > >>> Hi all,
>>> > > >>>
>>> > > >>> Thanks to Olivier for starting this discussion and for
>>> confirming sponsorship for Discourse. This is definitely something we could
>>> use to address the current sprawl of Jenkins communication channels. Many
>>> channels like User Mailing list, some SIG mailing lists and many Gitter
>>> channels could be replaced by discourse. So I am +1 for starting evaluation.
>>> > > >>>
>>> > > >>>
>>> > > >>> > 2) Configure the right level of Categories, as a first
>>> iteration I would like to focus on Jenkins users but we could extend it to
>>> Jenkins contributors as well.
>>> > > >>>
>>> > > >>> As Bruce said above, setting up a proper structure and
>>> moderation process is essential to the success of Discourse. Before we make
>>> it official, we should try it out and see how to better structure the
>>> communication channels. IMHO any interested contributor with Discourse
>>> expertise is welcome to participate in this effort. And thanks for stepping
>>> up Bruce!
>>> > > >>>
>>> > > >>> My notes:
>>> > > >>>
>>> > > >>> I would recommend creating categories for SIGs, sub-projects and
>>> outreach programs right away.
>>> > > >>> It would be great to create generic categories like "Jenkins
>>> Pipeline" or "Jenkins on Kubernetes". Plugins structure should be secondary
>>> there
>>> > > >>> Some plugins and components may need sub-categories. Likely
>>> these would be tool integration plugins (e.g. "Git plugins")
>>> > > >>> TBD: Creating a Governance category? It is feasible, but I am
>>> not sure how dit aligns with the current open governance approach through
>>> this mailing list and meetings
>>> > > >>>
>>> > > >>> I am happy to be a guinea pig for some of the categories if
>>> needed.
>>> > > >>>

Re: Discourse as the default communication channel?

['Gavin Mogan' via Jenkins Developers]

The tech it uses can give you pretty live updates, but its designed as a
forum.

I've sent you a DM on IRC with an invite link for now.



On Thu, May 27, 2021 at 1:08 PM Slide  wrote:

> I would like access please. Just a question, as I am very unfamiliar with
> Discourse. Is it a real time communication medium, a la IRC, or something
> more akin to a forum?
>
> On Thu, May 27, 2021 at 11:57 AM 'Olblak' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> For whoever is interested to participate to the Discourse project,
>> we started discussing over there as a way to test it and get more
>> familiar with the tool.
>> -> https://community.jenkins.io/t/discussion-about-categories/27/12
>>
>> Feel free to request an access as I didn't have the time yet to really
>> investigate the consequences of the different authentication methods.
>>
>> On Tue, May 25, 2021, at 8:46 PM, 'Olblak' via Jenkins Developers wrote:
>> > Hi Bruce,
>> >
>> > Thank you for stepping up, you already provided a lot of information
>> > here.
>> > And let's not assume we all know everything about discourse as we
>> > definitely don't.
>> > As you are interested to help with this project, I'll send you an
>> > invite to "community.jenkins.io".
>> >
>> > As long as we don't have an agreement on the authentication mechanism,
>> > I'll work on invite-only.
>> >
>> > Regarding identifying what we expected from Discourse, Bruce made a
>> > good statement that discourse is what we want it to be, so here what I
>> > would like it to solve.
>> > I would like to easily identify and participate in discussion about
>> > topics that interested me across different sub-project. So as an
>> > initial step, Oleg suggestion seems right to me.
>> >
>> > On my side, I'll investigate the different authentication options.
>> > Today during the infrastructure Oleg made a good remark,  we would like
>> > to ideally move away from maintaining our Ldap service and we would
>> > like to offer more alternatives than just using a Github account so
>> > maybe using Linux foundation accounts would be better.
>> >
>> >
>> > On Tue, May 25, 2021, at 7:16 PM, Matt Sicker wrote:
>> > > Ha, so I was. Oops!
>> > >
>> > > On Tue, 25 May 2021 at 10:32, 'Gavin Mogan' via Jenkins Developers
>> > >  wrote:
>> > > >
>> > > > Matt. It's often a confusion point. Discourse is more like a
>> form/mailing list type thing. Discord is realtime communication. Sounds
>> like your describing discord.
>> > > >
>> > > > On Tue., May 25, 2021, 6:52 a.m. Matt Sicker, 
>> wrote:
>> > > >>
>> > > >> I’ve never used Discourse outside of video games, but it seems
>> easier to set up public communities on than Slack or other things we’ve
>> tried here so far. While in theory I’d prefer something open like Matrix, I
>> do agree that we should try to minimize the number of services to maintain
>> ourselves.
>> > > >>
>> > > >> On Tue, May 25, 2021 at 07:45 Oleg Nenashev <
>> o.v.nenas...@gmail.com> wrote:
>> > > >>>
>> > > >>> Hi all,
>> > > >>>
>> > > >>> Thanks to Olivier for starting this discussion and for confirming
>> sponsorship for Discourse. This is definitely something we could use to
>> address the current sprawl of Jenkins communication channels. Many channels
>> like User Mailing list, some SIG mailing lists and many Gitter channels
>> could be replaced by discourse. So I am +1 for starting evaluation.
>> > > >>>
>> > > >>>
>> > > >>> > 2) Configure the right level of Categories, as a first
>> iteration I would like to focus on Jenkins users but we could extend it to
>> Jenkins contributors as well.
>> > > >>>
>> > > >>> As Bruce said above, setting up a proper structure and moderation
>> process is essential to the success of Discourse. Before we make it
>> official, we should try it out and see how to better structure the
>> communication channels. IMHO any interested contributor with Discourse
>> expertise is welcome to participate in this effort. And thanks for stepping
>> up Bruce!
>> > > >>>
>> > > >>> My notes:
>> > > >>>
>> > > >>> I would recommend creating categories for SIGs, sub-projects and
>> outreach programs right away.
>> > > >>> It would be great to create generic categories like "Jenkins
>> Pipeline" or "Jenkins on Kubernetes". Plugins structure should be secondary
>> there
>> > > >>> Some plugins and components may need sub-categories. Likely these
>> would be tool integration plugins (e.g. "Git plugins")
>> > > >>> TBD: Creating a Governance category? It is feasible, but I am not
>> sure how dit aligns with the current open governance approach through this
>> mailing list and meetings
>> > > >>>
>> > > >>> I am happy to be a guinea pig for some of the categories if
>> needed.
>> > > >>>
>> > > >>>
>> > > >>> > 1) Delegating authentication to a third service, Github,
>> keycloak, LDAP, etc...  My preferred approach would be to rely on Github
>> SSO to authenticate with the tool. But we could still use our Jenkins
>> account.
>> > > >>>
>> > > >>> 

Re: Discourse as the default communication channel?

[Slide]

I would like access please. Just a question, as I am very unfamiliar with
Discourse. Is it a real time communication medium, a la IRC, or something
more akin to a forum?

On Thu, May 27, 2021 at 11:57 AM 'Olblak' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> For whoever is interested to participate to the Discourse project,
> we started discussing over there as a way to test it and get more familiar
> with the tool.
> -> https://community.jenkins.io/t/discussion-about-categories/27/12
>
> Feel free to request an access as I didn't have the time yet to really
> investigate the consequences of the different authentication methods.
>
> On Tue, May 25, 2021, at 8:46 PM, 'Olblak' via Jenkins Developers wrote:
> > Hi Bruce,
> >
> > Thank you for stepping up, you already provided a lot of information
> > here.
> > And let's not assume we all know everything about discourse as we
> > definitely don't.
> > As you are interested to help with this project, I'll send you an
> > invite to "community.jenkins.io".
> >
> > As long as we don't have an agreement on the authentication mechanism,
> > I'll work on invite-only.
> >
> > Regarding identifying what we expected from Discourse, Bruce made a
> > good statement that discourse is what we want it to be, so here what I
> > would like it to solve.
> > I would like to easily identify and participate in discussion about
> > topics that interested me across different sub-project. So as an
> > initial step, Oleg suggestion seems right to me.
> >
> > On my side, I'll investigate the different authentication options.
> > Today during the infrastructure Oleg made a good remark,  we would like
> > to ideally move away from maintaining our Ldap service and we would
> > like to offer more alternatives than just using a Github account so
> > maybe using Linux foundation accounts would be better.
> >
> >
> > On Tue, May 25, 2021, at 7:16 PM, Matt Sicker wrote:
> > > Ha, so I was. Oops!
> > >
> > > On Tue, 25 May 2021 at 10:32, 'Gavin Mogan' via Jenkins Developers
> > >  wrote:
> > > >
> > > > Matt. It's often a confusion point. Discourse is more like a
> form/mailing list type thing. Discord is realtime communication. Sounds
> like your describing discord.
> > > >
> > > > On Tue., May 25, 2021, 6:52 a.m. Matt Sicker, 
> wrote:
> > > >>
> > > >> I’ve never used Discourse outside of video games, but it seems
> easier to set up public communities on than Slack or other things we’ve
> tried here so far. While in theory I’d prefer something open like Matrix, I
> do agree that we should try to minimize the number of services to maintain
> ourselves.
> > > >>
> > > >> On Tue, May 25, 2021 at 07:45 Oleg Nenashev 
> wrote:
> > > >>>
> > > >>> Hi all,
> > > >>>
> > > >>> Thanks to Olivier for starting this discussion and for confirming
> sponsorship for Discourse. This is definitely something we could use to
> address the current sprawl of Jenkins communication channels. Many channels
> like User Mailing list, some SIG mailing lists and many Gitter channels
> could be replaced by discourse. So I am +1 for starting evaluation.
> > > >>>
> > > >>>
> > > >>> > 2) Configure the right level of Categories, as a first iteration
> I would like to focus on Jenkins users but we could extend it to Jenkins
> contributors as well.
> > > >>>
> > > >>> As Bruce said above, setting up a proper structure and moderation
> process is essential to the success of Discourse. Before we make it
> official, we should try it out and see how to better structure the
> communication channels. IMHO any interested contributor with Discourse
> expertise is welcome to participate in this effort. And thanks for stepping
> up Bruce!
> > > >>>
> > > >>> My notes:
> > > >>>
> > > >>> I would recommend creating categories for SIGs, sub-projects and
> outreach programs right away.
> > > >>> It would be great to create generic categories like "Jenkins
> Pipeline" or "Jenkins on Kubernetes". Plugins structure should be secondary
> there
> > > >>> Some plugins and components may need sub-categories. Likely these
> would be tool integration plugins (e.g. "Git plugins")
> > > >>> TBD: Creating a Governance category? It is feasible, but I am not
> sure how dit aligns with the current open governance approach through this
> mailing list and meetings
> > > >>>
> > > >>> I am happy to be a guinea pig for some of the categories if needed.
> > > >>>
> > > >>>
> > > >>> > 1) Delegating authentication to a third service, Github,
> keycloak, LDAP, etc...  My preferred approach would be to rely on Github
> SSO to authenticate with the tool. But we could still use our Jenkins
> account.
> > > >>>
> > > >>> I am -1 for using the Jenkins account. Last year we agreed that we
> want to move away from running our own user identity, and I believe it was
> a right decision. One of the interesting options would be using the Linux
> Foundation SSO so that the forum is aligned with the Linux Foundation
> identities. If technically 

Re: Discourse as the default communication channel?

['Olblak' via Jenkins Developers]

For whoever is interested to participate to the Discourse project, 
we started discussing over there as a way to test it and get more familiar with 
the tool.
-> https://community.jenkins.io/t/discussion-about-categories/27/12

Feel free to request an access as I didn't have the time yet to really 
investigate the consequences of the different authentication methods.

On Tue, May 25, 2021, at 8:46 PM, 'Olblak' via Jenkins Developers wrote:
> Hi Bruce, 
> 
> Thank you for stepping up, you already provided a lot of information 
> here.
> And let's not assume we all know everything about discourse as we 
> definitely don't.
> As you are interested to help with this project, I'll send you an 
> invite to "community.jenkins.io".
> 
> As long as we don't have an agreement on the authentication mechanism, 
> I'll work on invite-only.
> 
> Regarding identifying what we expected from Discourse, Bruce made a 
> good statement that discourse is what we want it to be, so here what I 
> would like it to solve.
> I would like to easily identify and participate in discussion about 
> topics that interested me across different sub-project. So as an 
> initial step, Oleg suggestion seems right to me.
>  
> On my side, I'll investigate the different authentication options. 
> Today during the infrastructure Oleg made a good remark,  we would like 
> to ideally move away from maintaining our Ldap service and we would 
> like to offer more alternatives than just using a Github account so 
> maybe using Linux foundation accounts would be better.
> 
> 
> On Tue, May 25, 2021, at 7:16 PM, Matt Sicker wrote:
> > Ha, so I was. Oops!
> > 
> > On Tue, 25 May 2021 at 10:32, 'Gavin Mogan' via Jenkins Developers
> >  wrote:
> > >
> > > Matt. It's often a confusion point. Discourse is more like a form/mailing 
> > > list type thing. Discord is realtime communication. Sounds like your 
> > > describing discord.
> > >
> > > On Tue., May 25, 2021, 6:52 a.m. Matt Sicker,  wrote:
> > >>
> > >> I’ve never used Discourse outside of video games, but it seems easier to 
> > >> set up public communities on than Slack or other things we’ve tried here 
> > >> so far. While in theory I’d prefer something open like Matrix, I do 
> > >> agree that we should try to minimize the number of services to maintain 
> > >> ourselves.
> > >>
> > >> On Tue, May 25, 2021 at 07:45 Oleg Nenashev  
> > >> wrote:
> > >>>
> > >>> Hi all,
> > >>>
> > >>> Thanks to Olivier for starting this discussion and for confirming 
> > >>> sponsorship for Discourse. This is definitely something we could use to 
> > >>> address the current sprawl of Jenkins communication channels. Many 
> > >>> channels like User Mailing list, some SIG mailing lists and many Gitter 
> > >>> channels could be replaced by discourse. So I am +1 for starting 
> > >>> evaluation.
> > >>>
> > >>>
> > >>> > 2) Configure the right level of Categories, as a first iteration I 
> > >>> > would like to focus on Jenkins users but we could extend it to 
> > >>> > Jenkins contributors as well.
> > >>>
> > >>> As Bruce said above, setting up a proper structure and moderation 
> > >>> process is essential to the success of Discourse. Before we make it 
> > >>> official, we should try it out and see how to better structure the 
> > >>> communication channels. IMHO any interested contributor with Discourse 
> > >>> expertise is welcome to participate in this effort. And thanks for 
> > >>> stepping up Bruce!
> > >>>
> > >>> My notes:
> > >>>
> > >>> I would recommend creating categories for SIGs, sub-projects and 
> > >>> outreach programs right away.
> > >>> It would be great to create generic categories like "Jenkins Pipeline" 
> > >>> or "Jenkins on Kubernetes". Plugins structure should be secondary there
> > >>> Some plugins and components may need sub-categories. Likely these would 
> > >>> be tool integration plugins (e.g. "Git plugins")
> > >>> TBD: Creating a Governance category? It is feasible, but I am not sure 
> > >>> how dit aligns with the current open governance approach through this 
> > >>> mailing list and meetings
> > >>>
> > >>> I am happy to be a guinea pig for some of the categories if needed.
> > >>>
> > >>>
> > >>> > 1) Delegating authentication to a third service, Github, keycloak, 
> > >>> > LDAP, etc...  My preferred approach would be to rely on Github SSO to 
> > >>> > authenticate with the tool. But we could still use our Jenkins 
> > >>> > account.
> > >>>
> > >>> I am -1 for using the Jenkins account. Last year we agreed that we want 
> > >>> to move away from running our own user identity, and I believe it was a 
> > >>> right decision. One of the interesting options would be using the Linux 
> > >>> Foundation SSO so that the forum is aligned with the Linux Foundation 
> > >>> identities. If technically feasible, this would be my preference.
> > >>>
> > >>> Best regards,
> > >>> Oleg Nenashev
> > >>>
> > >>> P.S: My personal experience with forums is very limited. Fun fact about 
> 

Re: Updating Plugin framework to support Java11?

[Ullrich Hafner]

You should not switch your plugin to Java 11 unless Jenkins core switches to 
Java 11. Otherwise your plugin will not work in Jenkins instances that run with 
Java 8. So do not expect a solution until that step has been announced. 

> Am 27.05.2021 um 20:01 schrieb Bryan Stopp :
> 
> 
> Was looking at updating my plugin to only build using Java11 and output 
> Java11 bytecode.
> 
> But when I went to use 11 as the value of java.level in my pom, it broke due 
> to the plugins not understanding Java target of "1.11" (because its supposed 
> to be just "11").
> 
> Is there a plan to update/release a plugin parent pom that is predominantly 
> configured to support only Java11?
> 
> Thanks,
> 
> -Bryan
> 
> -- 
> 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 jenkinsci-dev+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/55720f8e-4944-49e1-ae8a-bc00d34fc50cn%40googlegroups.com
>  
> .

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6A550719-8D92-4C3A-B183-CF95AE337FAC%40gmail.com.

Updating Plugin framework to support Java11?

[Bryan Stopp]

Was looking at updating my plugin to only build using Java11 and output 
Java11 bytecode.

But when I went to use 11 as the value of *java.level* in my pom, it broke 
due to the plugins not understanding Java target of "1.11" (because its 
supposed to be just "11").

Is there a plan to update/release a plugin parent pom that is predominantly 
configured to support only Java11?

Thanks,

-Bryan

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/55720f8e-4944-49e1-ae8a-bc00d34fc50cn%40googlegroups.com.