Very nice! Thx a lot, Carlos Sent from my iPhone
> On 22 Jan 2017, at 05:02, Carlos Santana <[email protected]> wrote: > > I started looking in setting up a webserver to setup a auto sign for the > Slack team, so anyone can join. > > But then I was, a webserver for this simple task really? > > I went ahead and created a simple serveless action, exposed with api > gateway, and a simple github page > > Boom OpenWhisk Slack Invite ! > > Tell your serveless friends to join us in Slack: > https://csantanapr.github.io/openwhisk-slackinvite > > Backend is a 20 line OpenWhisk NodeJS Action > >> On Fri, Jan 20, 2017 at 2:45 PM Carlos Santana <[email protected]> wrote: >> >> I just created a new Slack team today https://openwhisk-team.slack.com >> (openwhisk domain was already taken :-( ) >> >> I think this will help users and grow the open community >> >> I proposed the following: >> - As community we join and use this Slack Team >> - Allow anyone to join automatically (we would would need to setup a >> simple web page (hopefully serverless)_ for folks to enter their email) >> - Treat it as IRC, water cooler, integrations to help daily dev tasks, >> etc.. Meaning also send people to join and use the dev list >> - Be aware that Slack is not the place to have converstations that are >> better to have in the dev list >> - Remember this is a free tier of Slack to messages start deleting after >> while, so grab to good questions, discussion, ideas, bugs, move it to >> issues, mailing list, wiki, etc.. >> >> I added some email domains so some of you can join today >> >> We can discuss channel creations and integration once in Slack >> >> -- Carlos >> >> >> On Mon, Dec 12, 2016 at 12:12 PM Sergio Fernández <[email protected]> >> wrote: >> >> Continuing with Betrand's arguments, I would say is more a community than >> an infrastructure discussion. Therefore it should better go to >> [email protected]. >> >> On Dec 12, 2016 5:13 PM, "Matt Rutkowski" <[email protected]> wrote: >> >> I will repost my question to the "infra" email list... it seems another >> project has done this as indicated and would like to replicate... >> >> Regards, >> -Matt >> >>> On 2016-12-12 08:28 (-0600), Felix Meschberger <[email protected]> wrote: >>> Techno: Yes, I’d think infra are the guys to talk to. You might want to >> start with users(a)infra(dot)apache(dot)org and be ready to fill a JIRA >> ticket >>> >>> Community: I agree with Bertrand. This mailing list is the ulitmate >> channel. So if something does not happen here, it didn’t. And while Slack >> is not really forcibly synchronous (as opposed to Jabber and IRC), free >> Slack has a limit of the number of past messages you see. But then: Would >> there be an option to forward messages (or digests) from Slack to the >> mailing list ? >>> >>> Regards >>> Felix >>> >>> >>>> Am 12.12.2016 um 10:33 schrieb Sergio Fernández <[email protected]>: >>>> >>>> On Fri, Dec 9, 2016 at 9:17 PM, Matt Rutkowski <[email protected]> >> wrote: >>>>> >>>>> How do we go about setting something up like this for OpenWhisk with >> these >>>>> additional domain-based account requirements? >>>>> >>>> >>>> I'm not sure what are the ASF policies for such external tooling. But I >>>> guess you'd need to talk with INFRA about archival of conversations or >> so. >>>> >>>> BTW, in addition ASF already uses a HipChat bound to @apache.org >> emails >>>> addresses: http://infra.chat >>>> >>>> -- >>>> <http://infra.chat> >>>> <http://infra.chat> >>>> Sergio Fernández >>>> Partner Technology Manager >>>> Redlink GmbH >>>> m: +43 6602747925 <+43%20660%202747925> >>>> e: <http://infra.chat>[email protected] >>>> w: http://redlink.co >>> >>> >> >>
