>
>
> Slack Etc
> -------------
> As Jacques and others mentioned. We have the HipChat room which can be
> used for collaboration but any discussions or decisions need to be on the
> mailing list.
>

https://www.bloomberg.com/news/articles/2018-07-26/slack-and-atlassian-team-up-to-take-on-microsoft-in-chat-software

Slack will pay an undisclosed amount over the next three years to acquire
> Atlassian’s HipChat and Stride assets, chief executives from both companies
> said. Slack CEO Stewart Butterfield described both the payment and the
> investment by Atlassian in his company as “nominal” in financial terms but
> important strategically. He declined to elaborate on the former.
>

regds
mallah.



On Mon, Mar 12, 2018 at 2:29 PM, Sharan Foga <sha...@apache.org> wrote:

> Hi All
>
> Thanks for the feedback and comments. Based on this I will run through
> actions for the next steps:
>
> Allocating Mentors
> ---------------------------
> Yes I see this as a good next step. So will start a thread about it
>
> Moving to the Dev list
> ------------------------------
> Yes we do need to move over to the development list as the documentation
> becomes part of the development of the project. I like the idea of
> prefixing messages with [DOC] so that people can easily see it and filter I
> also think its a little early to setup a completely new mailing list, let’s
> see how we work on the Dev list. I will post a thread about this.
>
> Actually once we start using Jira – most of that traffic will flow into
> the notifications mailing list. And for people actually working on  or
> watching a particular issue.,  will get notified immediately if there are
> any comments or changes. This means that any ongoing conversation around a
> Jira moves into the Jira itself which makes sense as it will become part of
> the task and work history .
>
> Slack Etc
> -------------
> As Jacques and others mentioned. We have the HipChat room which can be
> used for collaboration but any discussions or decisions need to be on the
> mailing list.
>
> Creating Umbrella tasks in Jira
> -------------------------------------------
> I think rather than one single overarching documentation Jira task, we can
> create each guide as an umbrella task similar to what  I’ve done with the
> Human Resources Guide. I think it would be better to use our Documentation
> wiki page to track which guides are in missing or still being worked on.
>
> So let’s move along to the next step :-)
>
> Thanks
> Sharan
>
>
> On 2018/03/09 11:29:28, Rajesh Mallah <mallah.raj...@gmail.com> wrote:
> > no probs , shall wait ;-) and live with the ML.
> >
> > On Fri, Mar 9, 2018 at 4:27 PM, Jacques Le Roux <
> > jacques.le.r...@les7arts.com> wrote:
> >
> > > Hi Mallah,
> > >
> > > I already gave you my opinion:
> > >
> > > https://markmail.org/message/lgg6rro2op4bg56v
> > > https://markmail.org/message/epop5orhzin53nx6
> > >
> > > It did not change since ;)
> > >
> > > Jacques
> > >
> > >
> > >
> > > Le 09/03/2018 à 10:34, Rajesh Mallah a écrit :
> > >
> > >> Hi Jacques ,
> > >>
> > >> +1 for some kind of realtime chat channel.
> > >>
> > >>
> > >> pls re-consider a slack channel . Its free for opensource projects
> > >> and its modern.
> > >>
> > >> slack(or any realtime chatroom) != synchronous communication.
> > >> personal freedom always prevails.
> > >>
> > >> slack has tons of feature over hipchat and seeing the kind of traffic
> we
> > >> have
> > >> in this ML , imho its a good fit.
> > >>
> > >> Also the quantum of effort to compose and send an email to ML is far
> more
> > >> than a short reply over slack. We see so many new comers adopting
> ofbiz
> > >> who have questions whose answers are short and can be suitably handled
> > >> over
> > >> chat.
> > >>
> > >>
> > >> regds
> > >> mallah.
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> On Fri, Mar 9, 2018 at 2:24 PM, Jacques Le Roux <
> > >> jacques.le.r...@les7arts.com> wrote:
> > >>
> > >> Le 09/03/2018 à 01:43, Taher Alkhateeb a écrit :
> > >>>
> > >>> and maybe even
> > >>>> Skype for quick simple tips or so.
> > >>>>
> > >>>> If really necessary I'd prefer the OFBiz HipChat room which is a bit
> > >>> more
> > >>> "official".
> > >>> But, as Michael reminded, the ASF mantra for communication is "if it
> did
> > >>> not happen on the list it didn't happen at all". This for at least
> > >>> obvious
> > >>> historical and research reasons. For now the dev seems indeed the
> best
> > >>> place.
> > >>> As Craig suggested,  a preface like [DOC] would fit.
> > >>>
> > >>> Jacques
> > >>>
> > >>>
> > >>>
> > >
> >
>

Reply via email to