OFBiz › OFBiz - User

[Documentation Team] Workflow and Process Ideas

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

16 messages Options

Sharan Foga

[Documentation Team] Workflow and Process Ideas

Hi All

Iâve started putting some ideas together about a suggested process for managing the flow of the documentation work using Jira. Essentially we want to make it as simple as possible for people to contribute.

https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+Team

There is a small diagram using the HR Guide as an example to show the folder structure we are looking to implement. I've split the process into various steps with some simple descriptions of what would need to be done.

Iâm going to be unavailable for the next few days but wanted to start this conversation. I'm hoping that people will take a look what I've started, and then also add their comments, ideas and improvements :-)

Looking forward to your feedback.

Thanks
Sharan

taher

Re: [Documentation Team] Workflow and Process Ideas

Great Work Sharan. Everything is very thorough and clear

As you know from the development ML, the initial work is committed
into trunk. Perhaps the next actions should include:
- identifying and matching mentors and mentees (if that's a word!)
- maybe creating an umbrella JIRA for the entire project

And I suppose perhaps we should start to move this discussion to dev@?
I hope everyone in the documentation team is subscribed over there?

Cheers,

On Thu, Mar 8, 2018 at 11:56 AM, Sharan Foga <[hidden email]> wrote:

> Hi All
>
> I’ve started putting some ideas together about a suggested process for managing the flow of the documentation work using Jira. Essentially we want to make it as simple as possible for people to contribute.
>
> https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+Team
>
> There is a small diagram using the HR Guide as an example to show the folder structure we are looking to implement. I've split the process into various steps with some simple descriptions of what would need to be done.
>
> I’m going to be unavailable for the next few days but wanted to start this conversation. I'm hoping that people will take a look what I've started, and then also add their comments, ideas and improvements :-)
>
> Looking forward to your feedback.
>
> Thanks
> Sharan

Timothy Boyden

RE: [Documentation Team] Workflow and Process Ideas

I am not currently on @Dev list. My thoughts on this is documentation could be a heavy list and may be better suited to its own list. The activity would be too much for @user and I am sure the devs would prefer not to have the extra chatter on their thread. Just my $0.02.

-Tim

-----Original Message-----
From: Taher Alkhateeb <[hidden email]>
Sent: Thursday, March 8, 2018 5:41 AM
To: [hidden email]
Subject: Re: [Documentation Team] Workflow and Process Ideas

Great Work Sharan. Everything is very thorough and clear

As you know from the development ML, the initial work is committed into trunk. Perhaps the next actions should include:
- identifying and matching mentors and mentees (if that's a word!)
- maybe creating an umbrella JIRA for the entire project

And I suppose perhaps we should start to move this discussion to dev@?
I hope everyone in the documentation team is subscribed over there?

Cheers,

On Thu, Mar 8, 2018 at 11:56 AM, Sharan Foga <[hidden email]> wrote:

> Hi All
>
> I’ve started putting some ideas together about a suggested process for managing the flow of the documentation work using Jira. Essentially we want to make it as simple as possible for people to contribute.
>
> https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+
> Team
>
> There is a small diagram using the HR Guide as an example to show the folder structure we are looking to implement. I've split the process into various steps with some simple descriptions of what would need to be done.
>
> I’m going to be unavailable for the next few days but wanted to start
> this conversation. I'm hoping that people will take a look what I've
> started, and then also add their comments, ideas and improvements :-)
>
> Looking forward to your feedback.
>
> Thanks
> Sharan

Timothy Boyden

RE: [Documentation Team] Workflow and Process Ideas

If another mail list cannot be done, perhaps the Skype list or a team tool like Microsoft Teams or Slack?

-Tim

-----Original Message-----
From: Timothy Boyden <[hidden email]>
Sent: Thursday, March 8, 2018 5:57 PM
To: [hidden email]
Subject: RE: [Documentation Team] Workflow and Process Ideas

I am not currently on @Dev list. My thoughts on this is documentation could be a heavy list and may be better suited to its own list. The activity would be too much for @user and I am sure the devs would prefer not to have the extra chatter on their thread. Just my $0.02.

-Tim

-----Original Message-----
From: Taher Alkhateeb <[hidden email]>
Sent: Thursday, March 8, 2018 5:41 AM
To: [hidden email]
Subject: Re: [Documentation Team] Workflow and Process Ideas

Great Work Sharan. Everything is very thorough and clear

As you know from the development ML, the initial work is committed into trunk. Perhaps the next actions should include:
- identifying and matching mentors and mentees (if that's a word!)
- maybe creating an umbrella JIRA for the entire project

And I suppose perhaps we should start to move this discussion to dev@?
I hope everyone in the documentation team is subscribed over there?

Cheers,

On Thu, Mar 8, 2018 at 11:56 AM, Sharan Foga <[hidden email]> wrote:

> Hi All
>
> I’ve started putting some ideas together about a suggested process for managing the flow of the documentation work using Jira. Essentially we want to make it as simple as possible for people to contribute.
>
> https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+
> Team
>
> There is a small diagram using the HR Guide as an example to show the folder structure we are looking to implement. I've split the process into various steps with some simple descriptions of what would need to be done.
>
> I’m going to be unavailable for the next few days but wanted to start
> this conversation. I'm hoping that people will take a look what I've
> started, and then also add their comments, ideas and improvements :-)
>
> Looking forward to your feedback.
>
> Thanks
> Sharan

Craig Parker

Re: [Documentation Team] Workflow and Process Ideas

I'd been wondering the same thing about a separate list.

On 03/08/2018 05:59 PM, Timothy Boyden wrote:

> If another mail list cannot be done, perhaps the Skype list or a team tool like Microsoft Teams or Slack?
>
> -Tim
>
> -----Original Message-----
> From: Timothy Boyden <[hidden email]>
> Sent: Thursday, March 8, 2018 5:57 PM
> To: [hidden email]
> Subject: RE: [Documentation Team] Workflow and Process Ideas
>
> I am not currently on @Dev list. My thoughts on this is documentation could be a heavy list and may be better suited to its own list. The activity would be too much for @user and I am sure the devs would prefer not to have the extra chatter on their thread. Just my $0.02.
>
> -Tim
>
> -----Original Message-----
> From: Taher Alkhateeb <[hidden email]>
> Sent: Thursday, March 8, 2018 5:41 AM
> To: [hidden email]
> Subject: Re: [Documentation Team] Workflow and Process Ideas
>
> Great Work Sharan. Everything is very thorough and clear
>
> As you know from the development ML, the initial work is committed into trunk. Perhaps the next actions should include:
> - identifying and matching mentors and mentees (if that's a word!)
> - maybe creating an umbrella JIRA for the entire project
>
> And I suppose perhaps we should start to move this discussion to dev@?
> I hope everyone in the documentation team is subscribed over there?
>
> Cheers,
>
> On Thu, Mar 8, 2018 at 11:56 AM, Sharan Foga <[hidden email]> wrote:
>> Hi All
>>
>> I’ve started putting some ideas together about a suggested process for managing the flow of the documentation work using Jira. Essentially we want to make it as simple as possible for people to contribute.
>>
>> https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+
>> Team
>>
>> There is a small diagram using the HR Guide as an example to show the folder structure we are looking to implement. I've split the process into various steps with some simple descriptions of what would need to be done.
>>
>> I’m going to be unavailable for the next few days but wanted to start
>> this conversation. I'm hoping that people will take a look what I've
>> started, and then also add their comments, ideas and improvements :-)
>>
>> Looking forward to your feedback.
>>
>> Thanks
>> Sharan

taher

Re: [Documentation Team] Workflow and Process Ideas

Perhaps we won't need as much communication as you may expect because maybe
lot of the details could be conveyed by mentors which would significantly
reduce traffic. Also, perhaps we shouldn't create a new ML before
_validating_ the need for it. If we find a consistent, high volume
communication happening then maybe that would be the preferred time to
create it, not to mention that we still have the wiki, JIRA, and maybe even
Skype for quick simple tips or so.

On Mar 9, 2018 3:24 AM, "Craig Parker" <[hidden email]> wrote:

> I'd been wondering the same thing about a separate list.
>
>
> On 03/08/2018 05:59 PM, Timothy Boyden wrote:
>
>> If another mail list cannot be done, perhaps the Skype list or a team
>> tool like Microsoft Teams or Slack?
>>
>> -Tim
>>
>> -----Original Message-----
>> From: Timothy Boyden <[hidden email]>
>> Sent: Thursday, March 8, 2018 5:57 PM
>> To: [hidden email]
>> Subject: RE: [Documentation Team] Workflow and Process Ideas
>>
>> I am not currently on @Dev list. My thoughts on this is documentation
>> could be a heavy list and may be better suited to its own list. The
>> activity would be too much for @user and I am sure the devs would prefer
>> not to have the extra chatter on their thread. Just my $0.02.
>>
>> -Tim
>>
>> -----Original Message-----
>> From: Taher Alkhateeb <[hidden email]>
>> Sent: Thursday, March 8, 2018 5:41 AM
>> To: [hidden email]
>> Subject: Re: [Documentation Team] Workflow and Process Ideas
>>
>> Great Work Sharan. Everything is very thorough and clear
>>
>> As you know from the development ML, the initial work is committed into
>> trunk. Perhaps the next actions should include:
>> - identifying and matching mentors and mentees (if that's a word!)
>> - maybe creating an umbrella JIRA for the entire project
>>
>> And I suppose perhaps we should start to move this discussion to dev@?
>> I hope everyone in the documentation team is subscribed over there?
>>
>> Cheers,
>>
>> On Thu, Mar 8, 2018 at 11:56 AM, Sharan Foga <[hidden email]> wrote:
>>
>>> Hi All
>>>
>>> I’ve started putting some ideas together about a suggested process for
>>> managing the flow of the documentation work using Jira. Essentially we want
>>> to make it as simple as possible for people to contribute.
>>>
>>> https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+
>>> Team
>>>
>>> There is a small diagram using the HR Guide as an example to show the
>>> folder structure we are looking to implement. I've split the process into
>>> various steps with some simple descriptions of what would need to be done.
>>>
>>> I’m going to be unavailable for the next few days but wanted to start
>>> this conversation. I'm hoping that people will take a look what I've
>>> started, and then also add their comments, ideas and improvements :-)
>>>
>>> Looking forward to your feedback.
>>>
>>> Thanks
>>> Sharan
>>>
>>
>

Craig Parker

Re: [Documentation Team] Workflow and Process Ideas

Well, can we preface every message with something simple like "Docs:"
for now, so folks can filter them if they want?

On 03/08/2018 07:43 PM, Taher Alkhateeb wrote:

> Perhaps we won't need as much communication as you may expect because maybe
> lot of the details could be conveyed by mentors which would significantly
> reduce traffic. Also, perhaps we shouldn't create a new ML before
> _validating_ the need for it. If we find a consistent, high volume
> communication happening then maybe that would be the preferred time to
> create it, not to mention that we still have the wiki, JIRA, and maybe even
> Skype for quick simple tips or so.
>
> On Mar 9, 2018 3:24 AM, "Craig Parker" <[hidden email]> wrote:
>
>> I'd been wondering the same thing about a separate list.
>>
>>
>> On 03/08/2018 05:59 PM, Timothy Boyden wrote:
>>
>>> If another mail list cannot be done, perhaps the Skype list or a team
>>> tool like Microsoft Teams or Slack?
>>>
>>> -Tim
>>>
>>> -----Original Message-----
>>> From: Timothy Boyden <[hidden email]>
>>> Sent: Thursday, March 8, 2018 5:57 PM
>>> To: [hidden email]
>>> Subject: RE: [Documentation Team] Workflow and Process Ideas
>>>
>>> I am not currently on @Dev list. My thoughts on this is documentation
>>> could be a heavy list and may be better suited to its own list. The
>>> activity would be too much for @user and I am sure the devs would prefer
>>> not to have the extra chatter on their thread. Just my $0.02.
>>>
>>> -Tim
>>>
>>> -----Original Message-----
>>> From: Taher Alkhateeb <[hidden email]>
>>> Sent: Thursday, March 8, 2018 5:41 AM
>>> To: [hidden email]
>>> Subject: Re: [Documentation Team] Workflow and Process Ideas
>>>
>>> Great Work Sharan. Everything is very thorough and clear
>>>
>>> As you know from the development ML, the initial work is committed into
>>> trunk. Perhaps the next actions should include:
>>> - identifying and matching mentors and mentees (if that's a word!)
>>> - maybe creating an umbrella JIRA for the entire project
>>>
>>> And I suppose perhaps we should start to move this discussion to dev@?
>>> I hope everyone in the documentation team is subscribed over there?
>>>
>>> Cheers,
>>>
>>> On Thu, Mar 8, 2018 at 11:56 AM, Sharan Foga <[hidden email]> wrote:
>>>
>>>> Hi All
>>>>
>>>> I’ve started putting some ideas together about a suggested process for
>>>> managing the flow of the documentation work using Jira. Essentially we want
>>>> to make it as simple as possible for people to contribute.
>>>>
>>>> https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Documentation+
>>>> Team
>>>>
>>>> There is a small diagram using the HR Guide as an example to show the
>>>> folder structure we are looking to implement. I've split the process into
>>>> various steps with some simple descriptions of what would need to be done.
>>>>
>>>> I’m going to be unavailable for the next few days but wanted to start
>>>> this conversation. I'm hoping that people will take a look what I've
>>>> started, and then also add their comments, ideas and improvements :-)
>>>>
>>>> Looking forward to your feedback.
>>>>
>>>> Thanks
>>>> Sharan
>>>>

Michael Brohl-3

Re: [Documentation Team] Workflow and Process Ideas

In reply to this post by Timothy Boyden

Hi Tim,

Mailing lists are the official medium to work together and document
things (if it does not happen on the list it didn't happen). I'd suggest
ro first start on dev@ and we'll see if this produces too much traffic
there.

If you want to propose things you can also create or add to wiki pages
and reference to them in the mailing list.

Regards,

Michael

Am 08.03.18 um 23:59 schrieb Timothy Boyden:

smime.p7s (5K) Download Attachment

Jacques Le Roux

Re: [Documentation Team] Workflow and Process Ideas

Administrator

In reply to this post by taher

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

taher

Re: [Documentation Team] Workflow and Process Ideas

Just to clarify what I mean folks: The ML is definitely the place for
making design and development decisions. And the purpose of mentors, wiki,
jira, skype, hipchat or whatever else is not to replace it, but to avoid
unnecessary communication in the ML. This could be things like general
beginner questions that have nothing to do with the design or development
of this documentation project.

On Mar 9, 2018 11:53 AM, "Jacques Le Roux" <[hidden email]>
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
>
>

Rajesh Mallah

Re: [Documentation Team] Workflow and Process Ideas

In reply to this post by Jacques Le Roux

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 <
[hidden email]> wrote:

Jacques Le Roux

Re: [Documentation Team] Workflow and Process Ideas

Administrator

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 <
> [hidden email]> 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
>>
>>

Rajesh Mallah

Re: [Documentation Team] Workflow and Process Ideas

no probs , shall wait ;-) and live with the ML.

On Fri, Mar 9, 2018 at 4:27 PM, Jacques Le Roux <
[hidden email]> 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 <
>> [hidden email]> 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
>>>
>>>
>>>
>

Sharan Foga

Re: [Documentation Team] Workflow and Process Ideas

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 <[hidden email]> wrote:

> no probs , shall wait ;-) and live with the ML.
>
> On Fri, Mar 9, 2018 at 4:27 PM, Jacques Le Roux <
> [hidden email]> 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 <
> >> [hidden email]> 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
> >>>
> >>>
> >>>
> >
>

Rajesh Mallah

Re: [Documentation Team] Workflow and Process Ideas

>
>
> 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 <[hidden email]> 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 <[hidden email]> wrote:
> > no probs , shall wait ;-) and live with the ML.
> >
> > On Fri, Mar 9, 2018 at 4:27 PM, Jacques Le Roux <
> > [hidden email]> 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 <
> > >> [hidden email]> 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
> > >>>
> > >>>
> > >>>
> > >
> >
>

Jacques Le Roux

Re: [Documentation Team] Workflow and Process Ideas

Administrator

Thanks Rajesh,

There is already https://the-asf.slack.com

Let's see what infra will come with...

Jacques

Le 27/07/2018 à 04:13, Rajesh Mallah a écrit :

>>
>> 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 <[hidden email]> 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 <[hidden email]> wrote:
>>> no probs , shall wait ;-) and live with the ML.
>>>
>>> On Fri, Mar 9, 2018 at 4:27 PM, Jacques Le Roux <
>>> [hidden email]> 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 <
>>>>> [hidden email]> 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
>>>>>>
>>>>>>
>>>>>>