Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

Awww I'm so happy they care so much about me But that's actually really awesome news. Gitter was a really good idea that was never completed. On Wed., Sep. 30, 2020, 6:49 a.m. Oleg Nenashev, wrote: > To make Gavin happy, GitLab handed over Gitter to Element. Element plans > to gradually make G

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

To make Gavin happy, GitLab handed over Gitter to Element. Element plans to gradually make Gitter "just" a client for matrix. - https://matrix.org/blog/2020/09/30/welcoming-gitter-to-matrix - https://element.io/blog/gitter-is-joining-element/ Good times. If done properly, it would definite

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

Hi Any thoughts on Zulip? They have an open source sponsorship for their cloud version: https://zulip.com/for/open-source/ There's a server you can try it out on here: https://chat.zulip.org/ Google, GitHub etc are all supported for auth to. Thanks Tim On Sat, 30 May 2020 at 18:44, Oleg Nena

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

I would be happy to do that. We have already established an onboarding process, and there was a proposal in thus thread to have regular meetings to do knowledge transfers. It got lost in the chat discussions On Sat, May 30, 2020, 18:33 Sladyn Nunes wrote: > Another aspect that could be explored

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

Another aspect that could be explored is having a sort of mentorship kind of a programme/channel . Just like the Linux kernel has a kernel mentorship program to coach new developers into contributing to the core, maybe we could have Jenkins core-mentorship coaching more new developers into contribu

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

Hi all, Just a heads-up I occasionally created a "#jenkins-release" channel on Freenode. Until we have a better decision in this thread, I suggest using this channel for runtime communications between the Jenkins release team and contributors who want to join. Final solution is still up for a

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

I also think that mattermost is a reasonable chat solution for devops teams - https://github.com/mattermost. Besides results of comparing mattermost and slack are pretty obvious - https://mattermost.com/mattermost-vs-slack/ :-) Just my 2c Thx, Vlad On Wednesday, April 8, 2020 at 5:17:38 AM UT

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

I started https://docs.google.com/spreadsheets/d/1F3Yj-X6y9SbdiQ1UX5aYEA3Z73rZMhw6WozvesvQ-QI/edit?usp=sharing yesterday to take some rough notes. My vote is still matrix! On Sun, Apr 12, 2020 at 11:49 AM Daniel Beck wrote: > > > > On 11. Apr 2020, at 19:53, Radosław Antoniuk > wrote: > > > > F

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

> On 11. Apr 2020, at 19:53, Radosław Antoniuk wrote: > > For me the availability of on-line archive of online chats, whether it be IRC > or Slack is not an argument for the tool, especially for the external > communication - for internal communication of the core contributors, it might > b

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

On Sat, Apr 11, 2020 at 2:08 AM Daniel Beck wrote: > > > On 11. Apr 2020, at 01:06, Oleg Nenashev wrote: > > > > TBH if we use Slack for runtime communications only, even losing history > is not a big deal > > Strongly disagree. Even such conversations have a tendency to contain > useful informa

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

On April 10, 2020 11:08:26 PM UTC, Marky Jackson wrote: >I am +1 on slack. Also feel gitter is a horrible experience but will >not use rocketchat, whatsapps, or Skype > >> On Apr 10, 2020, at 4:06 PM, Oleg Nenashev >wrote: >> >> If we have archiving established, I do not mind trying out Slack.

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

> On 11. Apr 2020, at 01:06, Oleg Nenashev wrote: > > TBH if we use Slack for runtime communications only, even losing history is > not a big deal Strongly disagree. Even such conversations have a tendency to contain useful information, I'm not interested in having to keep a text editor ope

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

I am +1 on slack. Also feel gitter is a horrible experience but will not use rocketchat, whatsapps, or Skype > On Apr 10, 2020, at 4:06 PM, Oleg Nenashev wrote: > > If we have archiving established, I do not mind trying out Slack. TBH if we > use Slack for runtime communications only, even los

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

If we have archiving established, I do not mind trying out Slack. TBH if we use Slack for *runtime communications only*, even losing history is not a big deal. But I do not hold my breath about t, so history is needed IMHO. My IMHO: Gitter is quite bad and not really maintained nowadays, IRC is

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

Also this for moderation on slack: https://github.com/foqal/slack-moderator/blob/master/README.md On Thu, 9 Apr 2020 at 12:51, Tim Jacomb wrote: > There’s this project for a public archive of slack: > https://github.com/dutchcoders/slackarchive > > We would need the equivalent for IRC as well I

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

There’s this project for a public archive of slack: https://github.com/dutchcoders/slackarchive We would need the equivalent for IRC as well I think. With IRC currently there’s no public log of any of the Jenkins channels. Each person needs to log it then self or pay / run a service that will do

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

Hey, I'm not critisizing! I just have my own preference and opinion :-) You know, if IRC would be so great, Slack wouldn't exist. Indeed, between Gitter and IRC probably I'd choose IRC. Between Rocket.Chat and IRC (although I never used it), for my own startup, I am choosing Slack or Rocket.Chat, b

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

> On 9. Apr 2020, at 10:55, Radosław Antoniuk wrote: > > Gitter/Slack, JIRA Infra and dev mailing list should be enough and then if > #core on Gitter then #infra also on Gitter. Didn't Gitter have problems maintaining the platform? Have those been resolved? And Slack costs money unless we'r

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

> > > I'd also love to have a channel for #infra. > > Multiple references to #jenkins-infra on > https://jenkins.io/projects/infrastructure/ > > Not intended that way, but still a great example what a major downside is > when jumping on every chat software bandwagon, it makes it unnecessarily > dif

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

> On 9. Apr 2020, at 10:31, Radek Antoniuk wrote: > > I'd also love to have a channel for #infra. Multiple references to #jenkins-infra on https://jenkins.io/projects/infrastructure/ Not intended that way, but still a great example what a major downside is when jumping on every chat softwa

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

Infra is on IRC.freenode.net #jenkins-infra I've been using matrix for a few months now, so will be writing up a proposal real soon on centralizing on matrix cause right now everything is so spread out On Thu., Apr. 9, 2020, 1:31 a.m. Radek Antoniuk, wrote: > Definitely +1 for core channel, def

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

Definitely +1 for core channel, definitely -1 for gitter and +1 for Slack or some other alternative like Rocket.Chat: I'd also love to have a channel for #infra. Something on that: https://medium.com/@gabriel_wilkes/why-tech-groups-can-get-away-with-using-slack-for-free-but-open-source-projects-a

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

I'm not a big fan of gitter myself as the client is fairly buggy and limited compared to the alternatives. I'm even ok with IRC. We could use some other chat as well like Slack as you suggested. On Wed, Apr 8, 2020 at 2:15 PM Sladyn Nunes wrote: > > I would like to share my opinion as a new cont

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

I would like to share my opinion as a new contributer to the Jenkins core that it would be very helpful if there is a Jenkins core developers dedicated channel maybe on slack or any other convenient medium similar to the Jenkins-X project , because the jenkinsci/jenkins gitter channel is mostly fi

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

do you mean #jenkins on irc or gitter http://gitter.im/jenkinsci/jenkins ? gitter jenkins is are very heavy user channel irc jenkins isn't so bad but still lots of people after pipeline help. On the kubernetes slack there's a few, -users and -dev channels Which helps separate out the noise in my

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

> On 8. Apr 2020, at 14:17, Oleg Nenashev wrote: > > creation of chats and other communication channels for Jenkins core > maintainers which could help in the case of runtime communications: > merge/changelog discussions, sync-ups between maintainers, etc. Right now we > mostly use pull req

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

+1 from me on a core-dev chat room. I do think we will have to make sure it is moderated in some fashion to prevent non-core-dev related questioning. I also think if this room is created there should be some type of banner stating that this channel expects that some basic debugging was done prio

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

I think a core-dev chat room would be useful, I don’t think it needs limiting to just be core-developers though Anything related to development on the core would be welcomed there Thanks Tim On Wed, 8 Apr 2020 at 13:17, Oleg Nenashev wrote: > Hi all, > > In the Proposal: Expanding the Jenkins

Discussion: Jenkins Core Maintainer/Developer discussion channels

Hi all, In the Proposal: Expanding the Jenkins Core maintainers team thread we briefly discussed creation of chats and other communication channels for Jenkins core maintainers which could help in the case of runtim