The community is interested in dates. Surely enough time has passed there’s a decent indication. On 25 Oct 2019, 14:09 +0100, Vadim Rutkovsky , wrote: > On Fri, Oct 25, 2019 at 2:57 PM Justin Cook wrote: > > Are there any dates associated with milestones? I can’t find any. > > No,
Are there any dates associated with milestones? I can’t find any. On 25 Oct 2019, 13:12 +0100, Christian Glombek , wrote: > > The Roadmap for OKD 4 has been accepted! > > > > On Tue, Oct 15, 2019 at 3:00 PM Christian Glombek > > wrote: > > > Dear OKD Community, > > > this is a Call for Agreement
say an email address scrubbed, then so be it. Otherwise, there’s nothing of interest. But, yet again, if they used the channel with explicit notification, their use is consent. Using GDPR as an excuse is fear mongering by people who don’t understand it. Justin Cook > > > > > > > > > > ___ dev mailing list email@example.com http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
On 22 Jul 2019, 00:07 +0100, Gleidson Nascimento , wrote: > I'm with Daniel, I believe it is easier to attract help by using Slack > instead of IRC. My experience over many years — especially with OCP3 — IRC with public logs smashes Slack. It’s not comparable. The proof is in the pudding.
by forking OKD3 and integrating upstream. I am not interested in doing that. We shouldn’t have to. Cheers, Justin Cook On 20 Jul 2019, 06:34 +0530, Daniel Comnea , wrote: > Hi Christian, > > Welcome and thanks for volunteering on kicking off this effort. > > My vote goes to #openshif
On 12 Jul 2019, 15:52 +0100, Neal Gompa , wrote: > On Fri, Jul 12, 2019 at 10:48 AM Michael Gugino wrote: > > > > I propose we keep the mailing list, and get back on Freenode for > > support instead of slack. In fact, I think we should move all > > openshift discussions that are not confidential
Freenode+++ On 12 Jul 2019, 15:48 +0100, Michael Gugino , wrote: > I propose we keep the mailing list, and get back on Freenode for > support instead of slack. In fact, I think we should move all > openshift discussions that are not confidential to freenode. > > On