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.
