- From: Lucas Huber <lh@codoo.io>
- Date: Mon, 29 Aug 2016 21:36:12 +0200
- To: Joseph Potvin <jpotvin@opman.ca>,Interledger Community Group <public-interledger@w3.org>
- Message-ID: <962B6D66-0C87-4344-8868-EE55E2FE6237@codoo.io>
Thanks for the reminder. Lucas -- Am 29. August 2016 21:30:10 MESZ, schrieb Joseph Potvin <jpotvin@opman.ca>: >RE: "Etherpad can also integrated into odoo notes module." > >Good to know. > >BTW -- I think you replied only to me and not to the list. > > >Joseph Potvin >Operations Manager | Gestionnaire des opérations >The Opman Company | La compagnie Opman >jpotvin@opman.ca >Mobile: 819-593-5983 >LinkedIn <https://www.linkedin.com/pub/joseph-potvin/2/148/423> > >On Mon, Aug 29, 2016 at 3:23 PM, Lucas Huber <lh@codoo.io> wrote: > >> If the opposite, a full featured solution is what we are looking for, >I >> recommend to have a look at Odoo. A very versatile modular foss >business >> suite. It comes with slack like messaging including mobile apps, but >also >> usable by mail. Etherpad can also integrated into odoo notes module. >> >> Lucas >> -- >> Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail >> gesendet. >> >> Am 29. August 2016 20:17:13 MESZ, schrieb Joseph Potvin ><jpotvin@opman.ca >> >: >>> >>> For a low-feature, stupid-simple (+ some clever features), >>> free/libre/open option via brower or mobile, there's the >co-authoring+chat >>> environment http://etherpad.org/ >>> >>> It's ready-hosted at many locations (e.g. >https://etherpad.wikimedia.org >>> ) ...or run one as https://etherpad.interledger.org >>> >>> It provides both the chat and co-authored minutes in one view. >>> >>> Not for the terminal interface participants. >>> >>> Joseph Potvin >>> >>> >>> On Mon, Aug 29, 2016 at 1:46 PM, Paul Frazee <pfrazee@gmail.com> >wrote: >>> >>>> Possibly Matrix.org >>>> >>>> On Mon, Aug 29, 2016 at 12:38 PM, Rafael Pereira ><rafael@rippex.net> >>>> wrote: >>>> >>>>> Someone must develop SMTP for IMs :) >>>>> >>>>> Obrigado, >>>>> Rafael >>>>> >>>>> [image: Rippex - O Gateway Ripple do Brasil] >>>>> >>>>> *Rafael Olaio - CEO * >>>>> tel +55 11 2337.2225 >>>>> cel +55 11 99522.7572 >>>>> rippex.net >>>>> Esta mensagem pode conter informação confidencial e/ou >privilegiada. Se >>>>> você não for o destinatário ou a pessoa autorizada a receber esta >mensagem, >>>>> não poderá usar, copiar ou divulgar as informações nela contidas >ou tomar >>>>> qualquer ação baseada nessas informações. Se você recebeu esta >mensagem por >>>>> engano, por favor avise imediatamente o remetente, respondendo o >e-mail e >>>>> em seguida apague-o.This message may contain confidential and/or >>>>> privileged information. If you are not the addressee or authorized >to >>>>> receive this for the addressee, you must not use, copy, disclose >or take >>>>> any action based on this message or any information here in. If >you have >>>>> received this message in error, please advise the sender >immediately by >>>>> reply e-mail and delete this message. >>>>> >>>>> 2016-08-29 14:33 GMT-03:00 Adrian Hope-Bailie ><adrian@hopebailie.com>: >>>>> >>>>>> I polled the group about using Slack a while back and the general >>>>>> consensus was that they didn't want to use it and would prefer >open tech >>>>>> like IRC. >>>>>> >>>>>> If you log into Gitter you'll be able to link it to a Slack >channel if >>>>>> that's what you'd like to do. >>>>>> >>>>>> On 29 August 2016 at 18:27, M AV <av_m@hotmail.com> wrote: >>>>>> >>>>>>> Any reason not considering Slack? >>>>>>> >>>>>>> >>>>>>> >>>>>>> *From:* Adrian Hope-Bailie [mailto:adrian@hopebailie.com] >>>>>>> *Sent:* Monday, August 29, 2016 5:57 AM >>>>>>> *To:* Daniel Bateman <7daniel77@gmail.com> >>>>>>> *Cc:* Interledger Community Group <public-interledger@w3.org> >>>>>>> *Subject:* Re: IRC and Gitter >>>>>>> >>>>>>> >>>>>>> >>>>>>> Update: Since the W3C IRC has no NickServ we can't use >sameroom.io >>>>>>> which requires this :( >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 29 August 2016 at 11:46, Adrian Hope-Bailie ><adrian@hopebailie.com> >>>>>>> wrote: >>>>>>> >>>>>>> re: 'possibly host' : We can host it ourselves (I will see if >Ripple >>>>>>> can sponsor this) or we can use a hosted service like >sameroom.io. >>>>>>> >>>>>>> re cost: >>>>>>> - Sameroom.io = $49/month (5 channels), >>>>>>> - hosted = is cost of hosting and people to manage/setup >>>>>>> >>>>>>> >>>>>>> >>>>>>> On 26 August 2016 at 16:22, Daniel Bateman <7daniel77@gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>> For option 2, what is the cost of managing another service? And >why >>>>>>> is it 'possibly host?' >>>>>>> >>>>>>> Daniel >>>>>>> >>>>>>> On Aug 26, 2016 10:04 AM, "Adrian Hope-Bailie" ><adrian@hopebailie.com> >>>>>>> wrote: >>>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> I have done some investigating and have two options for us with >>>>>>> regard to using Gitter but still offering IRC for those that >prefer that >>>>>>> channel. >>>>>>> >>>>>>> *Option 1: Switch to Gitter hosted IRC server* >>>>>>> >>>>>>> If you visit http://irc.gitter.im you'll see instructions for >>>>>>> connecting to a secure IRC server using a unique, per-user >server key. >>>>>>> >>>>>>> Once you connect you'll be logged into an IRC channel for each >Gitter >>>>>>> room and use the same Nick as your github username. >>>>>>> >>>>>>> Anything posted in either system is mirrored in the other. >>>>>>> >>>>>>> Pros: >>>>>>> >>>>>>> - Secure IRC >>>>>>> >>>>>>> - Tight integration with Gitter >>>>>>> >>>>>>> Cons: >>>>>>> >>>>>>> - Need to switch to a new IRC server >>>>>>> >>>>>>> - Lose the W3C IRC bots >>>>>>> >>>>>>> >>>>>>> >>>>>>> *Option 2: Setup a bridge between Gitter and W3C IRC* >>>>>>> >>>>>>> There are bots that can monitor both systems and mirror messages >>>>>>> between them. We can use https://sameroom.io or host a bot >ourselves. >>>>>>> >>>>>>> Pros: >>>>>>> >>>>>>> - Keep same IRC server and channel >>>>>>> >>>>>>> >>>>>>> >>>>>>> Cons: >>>>>>> >>>>>>> - Need to manage (and possibly host) yet another service >>>>>>> >>>>>>> Anyone have any thoughts on these options? >>>>>>> >>>>>>> Adrian >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>> >>>
Received on Monday, 29 August 2016 19:36:36 UTC