<div dir="ltr">All good points, it's important that we do not diverge from the community. Today I created an #openstack-functions channel on IRC and have submitted the necessary patches to the openstack-infra project-config and irc-meetings repositories. Due to this, I may have to move the first meeting from this Tuesday to another day or week as we wait for approval.. I'll keep this thread posted as soon as I know more.<div><br></div><div>Regards,</div><div>Derek</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Mar 2, 2017 at 11:54 AM Paul Belanger <<a href="mailto:pabelanger@redhat.com">pabelanger@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Thu, Mar 02, 2017 at 05:41:24PM +0000, Derek Schultz wrote:<br class="gmail_msg">
> Hi Emilien,<br class="gmail_msg">
><br class="gmail_msg">
> Thanks for the feedback! I'm aware that IRC is the standard for OpenStack<br class="gmail_msg">
> folks, but at this current stage it's just easier to hold the discussion in<br class="gmail_msg">
> Slack as Picasso ties into the IronFunctions open source project and<br class="gmail_msg">
> important context would be lost if we were to maintain different chat<br class="gmail_msg">
> platforms. That said, I think we can move Picasso from Slack to IRC in the<br class="gmail_msg">
> future (once we prepare for the big tent).<br class="gmail_msg">
><br class="gmail_msg">
I agree with Emilien here, by using a proprietary platform you are potentially<br class="gmail_msg">
alienation existing openstack developers from contributing to your project.<br class="gmail_msg">
Yes IRC would be needed for big tent, but why start consuming IRC out of the<br class="gmail_msg">
gate?<br class="gmail_msg">
<br class="gmail_msg">
Are are already hosting code on <a href="http://git.openstack.org" rel="noreferrer" class="gmail_msg" target="_blank">git.openstack.org</a>, seems like the next step<br class="gmail_msg">
would be to move to IRC.<br class="gmail_msg">
<br class="gmail_msg">
> Regards,<br class="gmail_msg">
> Derek Schultz<br class="gmail_msg">
><br class="gmail_msg">
> On Wed, Mar 1, 2017 at 7:49 AM Emilien Macchi <<a href="mailto:emilien@redhat.com" class="gmail_msg" target="_blank">emilien@redhat.com</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
> > On Tue, Feb 28, 2017 at 12:30 PM, Derek Schultz <<a href="mailto:schultz.derek@gmail.com" class="gmail_msg" target="_blank">schultz.derek@gmail.com</a>><br class="gmail_msg">
> > wrote:<br class="gmail_msg">
> > > Hello all,<br class="gmail_msg">
> > ><br class="gmail_msg">
> > > The Picasso team will be running our first meeting next Tuesday. All<br class="gmail_msg">
> > those<br class="gmail_msg">
> > > interested in the project are welcome!<br class="gmail_msg">
> > ><br class="gmail_msg">
> > > For those of you not familiar with Picasso, it provides a platform for<br class="gmail_msg">
> > > Functions as a Service (FaaS) on OpenStack [1].<br class="gmail_msg">
> > ><br class="gmail_msg">
> > > Tuesday, March 7th, 2017 Meeting Agenda:<br class="gmail_msg">
> > > Starting at UTC 18:00<br class="gmail_msg">
> > ><br class="gmail_msg">
> > > 1. From Python to Go. (What Picasso needs from IronFunctions to implement<br class="gmail_msg">
> > > multi-tenancy)<br class="gmail_msg">
> > > 2. Blueprints [2]<br class="gmail_msg">
> > > 3. Figure out best time slot for future meetings.<br class="gmail_msg">
> > > 4. Roadmap discussion.<br class="gmail_msg">
> > ><br class="gmail_msg">
> > > How to join:<br class="gmail_msg">
> > > <a href="http://slack.iron.io" rel="noreferrer" class="gmail_msg" target="_blank">http://slack.iron.io</a> in the #openstack channel<br class="gmail_msg">
> ><br class="gmail_msg">
> > I would recommend using IRC for consistency with other projects.<br class="gmail_msg">
> > Nothing forces you to do so, unless you plan to apply to the Big Tent.<br class="gmail_msg">
> > My personal recommendation would be to use IRC so you can get more<br class="gmail_msg">
> > visibility, since most of OpenStack folks are on IRC (and not always<br class="gmail_msg">
> > on Slack).<br class="gmail_msg">
> ><br class="gmail_msg">
> > Good luck for your first meeting!<br class="gmail_msg">
> ><br class="gmail_msg">
> > > Etherpad: <a href="https://etherpad.openstack.org/p/picasso-first-meeting" rel="noreferrer" class="gmail_msg" target="_blank">https://etherpad.openstack.org/p/picasso-first-meeting</a><br class="gmail_msg">
> > ><br class="gmail_msg">
> > > [1] <a href="https://wiki.openstack.org/wiki/Picasso" rel="noreferrer" class="gmail_msg" target="_blank">https://wiki.openstack.org/wiki/Picasso</a><br class="gmail_msg">
> > > [2] <a href="https://blueprints.launchpad.net/picasso" rel="noreferrer" class="gmail_msg" target="_blank">https://blueprints.launchpad.net/picasso</a><br class="gmail_msg">
> > ><br class="gmail_msg">
> > ><br class="gmail_msg">
> > ><br class="gmail_msg">
> > ><br class="gmail_msg">
> > __________________________________________________________________________<br class="gmail_msg">
> > > OpenStack Development Mailing List (not for usage questions)<br class="gmail_msg">
> > > Unsubscribe:<br class="gmail_msg">
> > <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" class="gmail_msg" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="gmail_msg">
> > > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="gmail_msg">
> > ><br class="gmail_msg">
> ><br class="gmail_msg">
> ><br class="gmail_msg">
> ><br class="gmail_msg">
> > --<br class="gmail_msg">
> > Emilien Macchi<br class="gmail_msg">
> ><br class="gmail_msg">
> > __________________________________________________________________________<br class="gmail_msg">
> > OpenStack Development Mailing List (not for usage questions)<br class="gmail_msg">
> > Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" class="gmail_msg" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="gmail_msg">
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="gmail_msg">
> ><br class="gmail_msg">
<br class="gmail_msg">
> __________________________________________________________________________<br class="gmail_msg">
> OpenStack Development Mailing List (not for usage questions)<br class="gmail_msg">
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" class="gmail_msg" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="gmail_msg">
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
__________________________________________________________________________<br class="gmail_msg">
OpenStack Development Mailing List (not for usage questions)<br class="gmail_msg">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" class="gmail_msg" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="gmail_msg">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="gmail_msg">
</blockquote></div>