> > experiment with language community channels Creating sub-categories, e.g. for francophone, Spanish speaking or Russian speaking communities
> experiment user outreach tools > Do you have something in mind? > I would start from a call for topic proposals for the Jenkins Contributor Summit. Later we can move many GSoC and Hacktoberfest discussions there On Fri, May 28, 2021, 16:09 'Olblak' via Jenkins Developers < jenkinsci-dev@googlegroups.com> wrote: > After additional testing, I decided to allow user registration, on > community.jenkins.io. > I needed it to test the Github integration. > We can still revert that decision if needed > > > > On Fri, May 28, 2021, at 1:57 PM, 'Olblak' via Jenkins Developers wrote: > > Hi Oleg, > > Could you elaborate > > experiment with language community channels > > > experiment user outreach tools > Do you have something in mind? > > On Fri, May 28, 2021, at 1:00 PM, Oleg Nenashev wrote: > > I would be interested to particupate as the Events officer. I would like > to experiment with language community channels and user outreach tools. > > Thanks to everyone for driving this! > > > On Fri, May 28, 2021, 11:52 'Olblak' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> wrote: > > > I would like to highlight the discussion about the different possible > authentication with an option to vote > -> https://community.jenkins.io/t/authentication-method-used/36 > > I understand not everybody at this point will be able to vote directly > from Discourse so feel free to either request access to be part of the > evaluation process or just provide feedback here. > > At this stage, Bruce, Gavin, Tim and I have admin access and can send > invites. > Once further in the process, we'll reevaluate admin access. > > Cheers > > > On Thu, May 27, 2021, at 11:06 PM, Mark Waite wrote: > > 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 <slide.o....@gmail.com> 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 > > > <jenkinsci-dev@googlegroups.com> 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, <boa...@gmail.com> > 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. > > > >>> > > > >>> 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 me: I was moderating a Lineage clan forum for a year or so. No, no > further comments :P > > > >>> > > > >>> On Tuesday, May 25, 2021 at 11:38:58 AM UTC+2 bruce...@gmail.com > wrote: > > > >>>> > > > >>>> Hi all. > > > >>>> > > > >>>> long time lurker, but this is my time to speak up. I have > maintained many instances of Jenkins, and just as many instances of > Discourse - most recent one is defined here : > https://github.com/EGI-Federation/community.egi.eu (I have since moved > on). > > > >>>> > > > >>>> It is imho the right choice for this, but there are good ways to > use it and better ways to use it. Beyond putting my vote for what it's > worth behind this decision, I would also like to volunteer my time where > possible to help setting up and moderating, etc. > > > >>>> Happy to help in whatever way. > > > >>>> > > > >>>> Thanks, > > > >>>> Bruce > > > >>>> > > > >>>> On Tuesday, May 25, 2021 at 11:02:15 AM UTC+2 Olblak wrote: > > > >>>>> > > > >>>>> Hi Everybody, > > > >>>>> > > > >>>>> I am really glad to share that "Civilized Discourse Construction > Kit, Inc", the company behind Discourse > > > >>>>> offered to sponsor the Jenkins project with the business "tier" > > > >>>>> -> https://www.discourse.org/pricing > > > >>>>> > > > >>>>> This is a very nice opportunity to "organize" discussions > happening across the community. > > > >>>>> Different people have different expectations so feel free to > raise your voice and share your ideas. > > > >>>>> > > > >>>>> What we want to achieve is better communication with the Jenkins > community, at the moment a lot of valuable information is lost in the > various mailing list, Gitter, IRC, etc. > > > >>>>> By using Discourse it would allow to centralize questions in one > place and regroup them by categories > > > >>>>> > > > >>>>> At this stage, we are still in exploratory mode, so if you have > any experience with the tool or just want to help > > > >>>>> feel free to reach out so I can send you an invite. > > > >>>>> The discourse will be one of the topics for today's > infrastructure meeting. > > > >>>>> > > > >>>>> The service is available on "https://community.jenkins.io";. > > > >>>>> > > > >>>>> The next steps are: > > > >>>>> > > > >>>>> 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. > Opinions are more than welcome. > > > >>>>> > > > >>>>> 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. > > > >>>>> > > > >>>>> 3) Identify a group of people interested to lead this initiative. > > > >>>>> > > > >>>>> Cheers > > > >>>>> > > > >>> -- > > > >>> 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/f99b8b73-f510-473f-b900-b93fc324dfb6n%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/CACmp6kqg%2Bjoqg9FW_6ok09-tkX%2B-qLC8jCF6d93WcQwFQD77DQ%40mail.gmail.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/CAG%3D_Duuo4cSyzRYwM7KGiPFqXmmSLCW29fWRVJF8oiaHaPT8pQ%40mail.gmail.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/CACmp6kqdKH-k8Jzdzy-tEqTZJyRAdpZ2Fx5bJHGK%2BMVCWykxOw%40mail.gmail.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/0dc7131d-6b5c-4b2e-9445-cfa60689b1b6%40www.fastmail.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/68409579-2884-4258-9559-d808ac6f590a%40www.fastmail.com > . > > > > -- > Website: http://earl-of-code.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/CAPiUgVfUcw6UutMj0QjZ8HujJC%3Dj12A78uBp7d2C21qkJ-osBw%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVfUcw6UutMj0QjZ8HujJC%3Dj12A78uBp7d2C21qkJ-osBw%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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutTtqW%3DKDZBKWtOEp25xecKTO2G046TqNFksjMpRMw7aA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutTtqW%3DKDZBKWtOEp25xecKTO2G046TqNFksjMpRMw7aA%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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEKXPk393f%2BBKg1N1xyWCP87WVWW2Dn1Z%3Dg705%2B6sxwRQ%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtEKXPk393f%2BBKg1N1xyWCP87WVWW2Dn1Z%3Dg705%2B6sxwRQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/5-zkWdvGTt0/unsubscribe. > To unsubscribe from this group and all its topics, 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/dfbcefaa-da64-4b87-b26e-0c69d9480907%40www.fastmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/dfbcefaa-da64-4b87-b26e-0c69d9480907%40www.fastmail.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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBfSu%3DukRrNWPdjA3OkH8AXwfw-p1OeLVv26mjRKuQGZQ%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLBfSu%3DukRrNWPdjA3OkH8AXwfw-p1OeLVv26mjRKuQGZQ%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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/63f81302-f78c-446a-89bd-8ae5a2061287%40www.fastmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/63f81302-f78c-446a-89bd-8ae5a2061287%40www.fastmail.com?utm_medium=email&utm_source=footer> > . > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/5-zkWdvGTt0/unsubscribe. > To unsubscribe from this group and all its topics, 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/cf8f8da6-1024-4526-86ae-aef9f16a9577%40www.fastmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/cf8f8da6-1024-4526-86ae-aef9f16a9577%40www.fastmail.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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCboLJUq-sLNmZ7DxpbAJ4Nn%3DZQ6zr868rS2xYPzdv%3DmQ%40mail.gmail.com.
