Re: Business Process and Use Case Library for Ecommerce ERP

[Pranay Pandey]

Thanks Rishi!

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Tue, Nov 15, 2016 at 6:20 PM, Rishi Solanki 
wrote:

> Agreed, +1 for proposed hierachy.
>
> Thanks Pranay!
>
> Rishi Solanki
> Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
>
> On Tue, Nov 15, 2016 at 6:08 PM, Pranay Pandey <
> pranay.pan...@hotwaxsystems.com> wrote:
>
> > Thanks Rishi for the note, there is a reason why I wanted to name those
> > component document suffixed with Branch or Release number. For better
> > indexing of documents, a unique name will help.
> >
> > Best regards,
> >
> > Pranay Pandey
> > HotWax Systems
> > http://www.hotwaxsystems.com/
> >
> > On Tue, Nov 15, 2016 at 4:40 PM, Rishi Solanki 
> > wrote:
> >
> > > Just one suggestion in hierachy, I'm good with the proposed hierachy as
> > > well.
> > >
> > > - OFBiz 14.12
> > > -- Ecommerce
> > > -- Order Manager
> > > ...
> > > ...
> > > ...
> > > - OFBiz 16.12
> > > -- Ecommerce
> > > -- Order Manager
> > >
> > > Thanks for initiative. :-)
> > >
> > >
> > > Rishi Solanki
> > > Manager, Enterprise Software Development
> > > HotWax Systems Pvt. Ltd.
> > > Direct: +91-9893287847
> > > http://www.hotwaxsystems.com
> > >
> > > On Tue, Nov 15, 2016 at 12:31 PM, Pranay Pandey <
> > > pranay.pan...@hotwaxsystems.com> wrote:
> > >
> > > > Interestingly, there will be heavy updates to these documents and
> hence
> > > > will be updated rigorously. Going with links to history I think won't
> > > work
> > > > in this case. We'll need to create separate pages with tagging the
> name
> > > of
> > > > the branch or release int he document name itself e.g.
> > > >
> > > > - OFBiz 14.12
> > > > -- Ecommerce 14.12
> > > > -- Order Manager 14.12
> > > > ...
> > > > ...
> > > > ...
> > > > - OFBiz 16.12
> > > > -- Ecommerce 16.12
> > > > -- Order Manager 16.12
> > > >
> > > >
> > > > Best regards,
> > > >
> > > > Pranay Pandey
> > > > HotWax Systems
> > > > http://www.hotwaxsystems.com/
> > > >
> > > > On Sun, Nov 13, 2016 at 3:31 PM, Jacques Le Roux <
> > > > jacques.le.r...@les7arts.com> wrote:
> > > >
> > > > > Hi Pranay,
> > > > >
> > > > > I like the idea, maybe you can use the same way I did it when I
> > updated
> > > > > the documentation for the Gradle move.
> > > > >
> > > > > I simply referenced with a link a previous version in history, eg:
> > "Pre
> > > > > Gradle version" notice at https://cwiki.apache.org/confl
> > > > > uence/display/OFBIZ/Addressing+Custom+Requirements+In+OFBiz
> > > > >
> > > > > Jacques
> > > > >
> > > > >
> > > > >
> > > > > Le 09/11/2016 à 13:55, Pranay Pandey a écrit :
> > > > >
> > > > >> Thanks Taher for this note. Yes it is about document
> re-organisation
> > > and
> > > > >> will help users to locate right set of document whenever needed.
> > > > >>
> > > > >> I am getting your point on priorities, but at the same time think
> > that
> > > > >> fine
> > > > >> tuned user stories will older branch will help us building good
> set
> > of
> > > > QA
> > > > >> artefacts for OFBiz upcoming release as well.
> > > > >>
> > > > >> I have also worked with one of my team member(Swapnil M Mane) to
> > come
> > > up
> > > > >> with a renewed OFBiz tutorial for beginners. Very soon we'll add
> it
> > to
> > > > >> OFBiz Confluence. Then we can discuss to upgrade it as needed for
> > > making
> > > > >> it
> > > > >> more easy to understand   and useful.
> > > > >>
> > > > >> Best regards,
> > > > >>
> > > > >> Pranay Pandey
> > > > >> HotWax Systems
> > > > >> http://www.hotwaxsystems.com/
> > > > >>
> > > > >> On Tue, Nov 8, 2016 at 4:53 PM, Taher Alkhateeb <
> > > > >> slidingfilame...@gmail.com>
> > > > >> wrote:
> > > > >>
> > > > >> Hi Pranay,
> > > > >>>
> > > > >>> It is a good idea of course to keep multiple versions of
> > > documentation
> > > > >>> for
> > > > >>> multiple releases.
> > > > >>>
> > > > >>> Talking in terms of priority, however, I think perhaps we need to
> > > spend
> > > > >>> most of our energy into first organizing and cleaning up our
> > > > >>> documentation.
> > > > >>> We need an API section, a user manual, a developer manual, and a
> > set
> > > of
> > > > >>> tutorials. All of these need to be categorized and point to each
> > > other
> > > > in
> > > > >>> hyperlinks. Right now, the documentation is heavily scattered in
> > > > >>> different
> > > > >>> and confusing sections. There is no "one location" for getting a
> > > piece
> > > > of
> > > > >>> information. So for example, the business processes could be
> maybe
> > > part
> > > > >>> of
> > > > >>> the "User Manual" right? We don't have such a categorization at
> the
> > > > >>> moment
> > > > >>> which dilutes value.
> > > > >>>
> > > > >>> Also if you think about it, good organization of this information
> > > would
> > > > >>> make it easier to create release-specific 

Re: OFBiz Premier League – Reviewers Choice Award

[Sharan Foga]

Hi Scott

No problem - with Apachecon and our OFBiz track this week, it is 
probably a good idea to extend it so let's make it the 22nd November 
instead.


Thanks
Sharan

On 15/11/16 23:00, Scott Gray wrote:

Hi Sharan,

If you could extend the deadline a few days it would be appreciated, I
haven't yet been able to read through all of the submissions.

Thanks
Scott

On 13 November 2016 at 09:22, Bilgin Ibryam  wrote:


Any effort to help make OFBiz better is worth an applause. Well done
HWM and Sharan.

Bilgin


On 11 November 2016 at 21:30, Jacques Le Roux
 wrote:

Oops sorry my dashboard was not shared, it is now, same link
https://issues.apache.org/jira/secure/Dashboard.jspa?

selectPageId=12310800

Jacques



Le 11/11/2016 à 19:30, Jacques Le Roux a écrit :

Hi Divesh, Sharan, Pierre,

First I think it's better to not cross post this thread, and it seems

it's

best placed here, in dev ML. Because, if we expect a realistic result,
reviewing the work done by the HotWax team and giving an opinion about

it is

clearly technical!

This said, it was already an overwhelming task to review the work done

by

the HotWax team (thanks you all!) and I don't think much people will

have

the time to seriously decide which team did the best work. Sorry but

I'll

not. Maybe inside HotWax it's easier to decide, so maybe Jacopo, Anil,

Scott

and maybe some others I miss (sorry for you guys, you are so many) will
because they did not participate and I guess it was on purpose?

About Pierre's answer, I must say I was also surprised that Sharan and

not

someone from HotWax asked for feedback. Because her questions were

already

quite organised.

This is minor regarding the question, but maybe Sharan you are

officially

working with HotWax now?

Anyway thanks to all who worked on these issues, improving OBFiz is

always

a good aim and your effort was quite impressive! We have still 300 new
issues waiting now ;)
https://issues.apache.org/jira/secure/Dashboard.jspa?

selectPageId=12310800

Jacques


Le 11/11/2016 à 09:32, Divesh Dutta a écrit :

Pierre,

Instead of taunting, you should understand the bigger cause for what
Sharan
is doing it. Overall OPL effort and involving others community members

in

it is for bigger cause and sake of OFBiz and its community.


Thanks
--
Divesh Dutta.

On Thu, Nov 10, 2016 at 2:50 PM, Pierre Smits 
wrote:


Hi Sharan,

Congratulations regarding your new assignment as HotWax spokesperson

to

the
OFBiz project.

Best regards

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Wed, Nov 9, 2016 at 11:39 PM, Sharan Foga 
wrote:


Hi Everyone

(I'm posting this on both user and dev lists).

The Hotwax Systems teams desperately need your help! Why? Because

their

OFBiz Premier League (OPL) competition ended this month. Details can

be

found at http://opl.ofbiz.us/)

Six teams were competing for points to improve OFBiz by contributing
ideas, code, documentation, developments and bug fixes. On 5th

November

2016 - the 6 month time period ended and now feedback from all the
OFBiz
Community is needed to choose the team that will receive the

'Reviewers

Choice Award'. (Note: The Reviewers are the OFBiz Community :-) )

The 6 teams were :

   *

 Team-1 - MV Controller

   *

 Team-2 - OFBiz Fanatics

   *

 Team-3 - OFgrammers

   *

 Team-4 - OS Biz Contributor

   *

 Team-5 - OS Code Breakers

   *

 Team-6 - SO Architects

Each team has prepared a report with details of the contributions

made

over the last 6 months. These reports can be found at the following
link:

https://drive.google.com/drive/folders/0BxupAk96lggNTm0zT3A2alNRY1k

Please take a look at the reports and then assign your rating score

for

each team. (I've taken a quick preview of the reports already and

it's

going to be a tough decision!). All the scores will be totalled and

the

winning team will be the one with the most points. The scores and
winner
will be announced on the OFBiz mailing lists.

*IMPORTANT NOTE*: All the Hotwax team members who are involved with

any

of

the OPL teams _*will not*_ participate in the rating or scoring of

any

of
the teams.


_*Rate The Teams*_

To rate the teams I've setup a short survey (see link) with the name

of

each team and a sliding scale that you can rate them and their work
from

1

(Poor) to 10 (Excellent).

https://www.surveymonkey.com/r/RXW7KVC

Anyone from the OFBiz Community can participate in the rating the OPL
teams. The survey will be open for the next 7 days and will close on

17^th

November 2016. The scores will be totalled and hopefully we'll find

out

which team has won the award.

Good luck to all the teams and thanks for all the OFBiz contributions

that

have been made.

Thanks
Sharan








--
Bilgin Ibryam
Camel Committer at ASF & 

Re: OFBiz Premier League – Reviewers Choice Award

[Sharan Foga]

Hi Jacques

I'm helping out at Apachecon in Seville so havent had much time to 
follow the mailing lists. I've included some responses below:


I cross posted this for several reasons.

 *

   This is an informational message and not a discussion thread

 *

   All the changes done by these teams benefit our users so it made
   sense to me to let our users take a look at what has been done and
   be able to vote for or rate teams that have implemented the features
   they like

 *

   Developer based questions are sometimes raised on our user list
   instead of our dev list, meaning that some of our technical
   community prefer using our user list rather than the dev one, so the
   message would reach them too

I disagree that giving an opinion or rating to the teams is clearly 
technical. Each of the teams have prepared a report summarising what 
they have done. Everyone is free to rate the teams based on their own 
criteria. If you want to rate them based on their coding techniques then 
you are free to do that and if someone else wants to rate them based on 
the features they have implemented then in my view that is also 
perfectly acceptable. This is an award where the OFBiz community choose, 
so why limit that to only developers when the work being done affects 
our user base too.


Remember that this OFBiz Premier League initiative was open to anyone 
from the OFBiz community – so anyone could have formed a team and become 
involved. It just so happened that no-one else did.


Also as I'd put together all the community surveys and had access to the 
tool, I was asked if I could create one to rate the teams, so it also 
made sense to for me send out the communications as well as the survey 
links. (So in response to your question No – I am not working for Hotwax)


I think that we shouldn't lose sight of the fact that everyone in the 
teams did these contributions in their own free time as individuals who 
wanted to contribute to OFBiz and not as paid Hotwax employees. If this 
was a paid effort instead of a voluntary effort, then I would probably 
have a different view but this is something that was done voluntarily 
for the community by other members of the community and to me that is 
all that counts.


Thanks
Sharan



On 11/11/16 19:30, Jacques Le Roux wrote:

Hi Divesh, Sharan, Pierre,

First I think it's better to not cross post this thread, and it seems 
it's best placed here, in dev ML. Because, if we expect a realistic 
result, reviewing the work done by the HotWax team and giving an 
opinion about it is clearly technical!


This said, it was already an overwhelming task to review the work done 
by the HotWax team (thanks you all!) and I don't think much people 
will have the time to seriously decide which team did the best work. 
Sorry but I'll not. Maybe inside HotWax it's easier to decide, so 
maybe Jacopo, Anil, Scott and maybe some others I miss (sorry for you 
guys, you are so many) will because they did not participate and I 
guess it was on purpose?


About Pierre's answer, I must say I was also surprised that Sharan and 
not someone from HotWax asked for feedback. Because her questions were 
already quite organised.


This is minor regarding the question, but maybe Sharan you are 
officially working with HotWax now?


Anyway thanks to all who worked on these issues, improving OBFiz is 
always a good aim and your effort was quite impressive! We have still 
300 new issues waiting now ;)
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12310800 



Jacques


Le 11/11/2016 à 09:32, Divesh Dutta a écrit :

Pierre,

Instead of taunting, you should understand the bigger cause for what 
Sharan
is doing it. Overall OPL effort and involving others community 
members in

it is for bigger cause and sake of OFBiz and its community.


Thanks
--
Divesh Dutta.

On Thu, Nov 10, 2016 at 2:50 PM, Pierre Smits 
wrote:


Hi Sharan,

Congratulations regarding your new assignment as HotWax spokesperson 
to the

OFBiz project.

Best regards

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

OFBiz Extensions Marketplace
http://oem.ofbizci.net/oci-2/

On Wed, Nov 9, 2016 at 11:39 PM, Sharan Foga 
wrote:


Hi Everyone

(I'm posting this on both user and dev lists).

The Hotwax Systems teams desperately need your help! Why? Because 
their
OFBiz Premier League (OPL) competition ended this month. Details 
can be

found at http://opl.ofbiz.us/)

Six teams were competing for points to improve OFBiz by contributing
ideas, code, documentation, developments and bug fixes. On 5th 
November
2016 - the 6 month time period ended and now feedback from all the 
OFBiz
Community is needed to choose the team that will receive the 
'Reviewers

Choice Award'. (Note: The Reviewers are the OFBiz Community :-) )

The 6 teams were :

  *

Team-1 - MV Controller

  *

Team-2 - OFBiz Fanatics

  *

Team-3 - OFgrammers

  *

Re: OFBiz Premier League – Reviewers Choice Award

[Scott Gray]

Hi Sharan,

If you could extend the deadline a few days it would be appreciated, I
haven't yet been able to read through all of the submissions.

Thanks
Scott

On 13 November 2016 at 09:22, Bilgin Ibryam  wrote:

> Any effort to help make OFBiz better is worth an applause. Well done
> HWM and Sharan.
>
> Bilgin
>
>
> On 11 November 2016 at 21:30, Jacques Le Roux
>  wrote:
> > Oops sorry my dashboard was not shared, it is now, same link
> > https://issues.apache.org/jira/secure/Dashboard.jspa?
> selectPageId=12310800
> >
> > Jacques
> >
> >
> >
> > Le 11/11/2016 à 19:30, Jacques Le Roux a écrit :
> >>
> >> Hi Divesh, Sharan, Pierre,
> >>
> >> First I think it's better to not cross post this thread, and it seems
> it's
> >> best placed here, in dev ML. Because, if we expect a realistic result,
> >> reviewing the work done by the HotWax team and giving an opinion about
> it is
> >> clearly technical!
> >>
> >> This said, it was already an overwhelming task to review the work done
> by
> >> the HotWax team (thanks you all!) and I don't think much people will
> have
> >> the time to seriously decide which team did the best work. Sorry but
> I'll
> >> not. Maybe inside HotWax it's easier to decide, so maybe Jacopo, Anil,
> Scott
> >> and maybe some others I miss (sorry for you guys, you are so many) will
> >> because they did not participate and I guess it was on purpose?
> >>
> >> About Pierre's answer, I must say I was also surprised that Sharan and
> not
> >> someone from HotWax asked for feedback. Because her questions were
> already
> >> quite organised.
> >>
> >> This is minor regarding the question, but maybe Sharan you are
> officially
> >> working with HotWax now?
> >>
> >> Anyway thanks to all who worked on these issues, improving OBFiz is
> always
> >> a good aim and your effort was quite impressive! We have still 300 new
> >> issues waiting now ;)
> >> https://issues.apache.org/jira/secure/Dashboard.jspa?
> selectPageId=12310800
> >>
> >> Jacques
> >>
> >>
> >> Le 11/11/2016 à 09:32, Divesh Dutta a écrit :
> >>>
> >>> Pierre,
> >>>
> >>> Instead of taunting, you should understand the bigger cause for what
> >>> Sharan
> >>> is doing it. Overall OPL effort and involving others community members
> in
> >>> it is for bigger cause and sake of OFBiz and its community.
> >>>
> >>>
> >>> Thanks
> >>> --
> >>> Divesh Dutta.
> >>>
> >>> On Thu, Nov 10, 2016 at 2:50 PM, Pierre Smits 
> >>> wrote:
> >>>
>  Hi Sharan,
> 
>  Congratulations regarding your new assignment as HotWax spokesperson
> to
>  the
>  OFBiz project.
> 
>  Best regards
> 
>  Pierre Smits
> 
>  ORRTIZ.COM 
>  OFBiz based solutions & services
> 
>  OFBiz Extensions Marketplace
>  http://oem.ofbizci.net/oci-2/
> 
>  On Wed, Nov 9, 2016 at 11:39 PM, Sharan Foga 
>  wrote:
> 
> > Hi Everyone
> >
> > (I'm posting this on both user and dev lists).
> >
> > The Hotwax Systems teams desperately need your help! Why? Because
> their
> > OFBiz Premier League (OPL) competition ended this month. Details can
> be
> > found at http://opl.ofbiz.us/)
> >
> > Six teams were competing for points to improve OFBiz by contributing
> > ideas, code, documentation, developments and bug fixes. On 5th
> November
> > 2016 - the 6 month time period ended and now feedback from all the
> > OFBiz
> > Community is needed to choose the team that will receive the
> 'Reviewers
> > Choice Award'. (Note: The Reviewers are the OFBiz Community :-) )
> >
> > The 6 teams were :
> >
> >   *
> >
> > Team-1 - MV Controller
> >
> >   *
> >
> > Team-2 - OFBiz Fanatics
> >
> >   *
> >
> > Team-3 - OFgrammers
> >
> >   *
> >
> > Team-4 - OS Biz Contributor
> >
> >   *
> >
> > Team-5 - OS Code Breakers
> >
> >   *
> >
> > Team-6 - SO Architects
> >
> > Each team has prepared a report with details of the contributions
> made
> > over the last 6 months. These reports can be found at the following
> > link:
> >
> > https://drive.google.com/drive/folders/0BxupAk96lggNTm0zT3A2alNRY1k
> >
> > Please take a look at the reports and then assign your rating score
> for
> > each team. (I've taken a quick preview of the reports already and
> it's
> > going to be a tough decision!). All the scores will be totalled and
> the
> > winning team will be the one with the most points. The scores and
> > winner
> > will be announced on the OFBiz mailing lists.
> >
> > *IMPORTANT NOTE*: All the Hotwax team members who are involved with
> any
> 
>  of
> >
> > the OPL teams _*will not*_ participate in the rating or scoring of
> any
> > of
> > the teams.
> >

Re: Integration tests take a very long time

[Scott Gray]

FYI latest trunk takes almost exactly 5 minutes on my machine.

Regards
Scott

On 16 November 2016 at 06:34, Taher Alkhateeb 
wrote:

> Hi Folks,
>
> As you may recall, we introduced unit-tests to OFBiz in addition to the
> existing integration tests to try and balance the long development cycle
> that we currently suffer from.
>
> The total number of tests on the latest version of Trunk on my machine is
> 1929, and the total time it takes to complete all tests using the command
> ./gradlew cleanAll loadDefault testIntegration is almost 20 minutes!
> Something is wrong, and in my opinion it is that we have way too many
> integration tests and very few unit tests. Integration tests are resource
> hungry and a strain on the system and heavily slow down the development
> cycle.
>
> So I urge everyone interested in writing tests to prefer unit tests over
> integration tests where possible, or even better, to try rewrite some of
> the integration tests as unit tests, or to increase the efficiency of the
> algorithms for testing. Our development cycle is becoming very slow because
> of the mountain of integration tests that reside in the framework.
>
> If you are interested, Jacopo already wrote a few tests with mocking using
> Mockito. You can use these tests as a reference to help you in writing
> efficient and fast unit tests.
>
> Cheers,
>
> Taher Alkhateeb
>

Integration tests take a very long time

[Taher Alkhateeb]

Hi Folks,

As you may recall, we introduced unit-tests to OFBiz in addition to the
existing integration tests to try and balance the long development cycle
that we currently suffer from.

The total number of tests on the latest version of Trunk on my machine is
1929, and the total time it takes to complete all tests using the command
./gradlew cleanAll loadDefault testIntegration is almost 20 minutes!
Something is wrong, and in my opinion it is that we have way too many
integration tests and very few unit tests. Integration tests are resource
hungry and a strain on the system and heavily slow down the development
cycle.

So I urge everyone interested in writing tests to prefer unit tests over
integration tests where possible, or even better, to try rewrite some of
the integration tests as unit tests, or to increase the efficiency of the
algorithms for testing. Our development cycle is becoming very slow because
of the mountain of integration tests that reside in the framework.

If you are interested, Jacopo already wrote a few tests with mocking using
Mockito. You can use these tests as a reference to help you in writing
efficient and fast unit tests.

Cheers,

Taher Alkhateeb

Re: Business Process and Use Case Library for Ecommerce ERP

[Rishi Solanki]

Agreed, +1 for proposed hierachy.

Thanks Pranay!

Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

On Tue, Nov 15, 2016 at 6:08 PM, Pranay Pandey <
pranay.pan...@hotwaxsystems.com> wrote:

> Thanks Rishi for the note, there is a reason why I wanted to name those
> component document suffixed with Branch or Release number. For better
> indexing of documents, a unique name will help.
>
> Best regards,
>
> Pranay Pandey
> HotWax Systems
> http://www.hotwaxsystems.com/
>
> On Tue, Nov 15, 2016 at 4:40 PM, Rishi Solanki 
> wrote:
>
> > Just one suggestion in hierachy, I'm good with the proposed hierachy as
> > well.
> >
> > - OFBiz 14.12
> > -- Ecommerce
> > -- Order Manager
> > ...
> > ...
> > ...
> > - OFBiz 16.12
> > -- Ecommerce
> > -- Order Manager
> >
> > Thanks for initiative. :-)
> >
> >
> > Rishi Solanki
> > Manager, Enterprise Software Development
> > HotWax Systems Pvt. Ltd.
> > Direct: +91-9893287847
> > http://www.hotwaxsystems.com
> >
> > On Tue, Nov 15, 2016 at 12:31 PM, Pranay Pandey <
> > pranay.pan...@hotwaxsystems.com> wrote:
> >
> > > Interestingly, there will be heavy updates to these documents and hence
> > > will be updated rigorously. Going with links to history I think won't
> > work
> > > in this case. We'll need to create separate pages with tagging the name
> > of
> > > the branch or release int he document name itself e.g.
> > >
> > > - OFBiz 14.12
> > > -- Ecommerce 14.12
> > > -- Order Manager 14.12
> > > ...
> > > ...
> > > ...
> > > - OFBiz 16.12
> > > -- Ecommerce 16.12
> > > -- Order Manager 16.12
> > >
> > >
> > > Best regards,
> > >
> > > Pranay Pandey
> > > HotWax Systems
> > > http://www.hotwaxsystems.com/
> > >
> > > On Sun, Nov 13, 2016 at 3:31 PM, Jacques Le Roux <
> > > jacques.le.r...@les7arts.com> wrote:
> > >
> > > > Hi Pranay,
> > > >
> > > > I like the idea, maybe you can use the same way I did it when I
> updated
> > > > the documentation for the Gradle move.
> > > >
> > > > I simply referenced with a link a previous version in history, eg:
> "Pre
> > > > Gradle version" notice at https://cwiki.apache.org/confl
> > > > uence/display/OFBIZ/Addressing+Custom+Requirements+In+OFBiz
> > > >
> > > > Jacques
> > > >
> > > >
> > > >
> > > > Le 09/11/2016 à 13:55, Pranay Pandey a écrit :
> > > >
> > > >> Thanks Taher for this note. Yes it is about document re-organisation
> > and
> > > >> will help users to locate right set of document whenever needed.
> > > >>
> > > >> I am getting your point on priorities, but at the same time think
> that
> > > >> fine
> > > >> tuned user stories will older branch will help us building good set
> of
> > > QA
> > > >> artefacts for OFBiz upcoming release as well.
> > > >>
> > > >> I have also worked with one of my team member(Swapnil M Mane) to
> come
> > up
> > > >> with a renewed OFBiz tutorial for beginners. Very soon we'll add it
> to
> > > >> OFBiz Confluence. Then we can discuss to upgrade it as needed for
> > making
> > > >> it
> > > >> more easy to understand   and useful.
> > > >>
> > > >> Best regards,
> > > >>
> > > >> Pranay Pandey
> > > >> HotWax Systems
> > > >> http://www.hotwaxsystems.com/
> > > >>
> > > >> On Tue, Nov 8, 2016 at 4:53 PM, Taher Alkhateeb <
> > > >> slidingfilame...@gmail.com>
> > > >> wrote:
> > > >>
> > > >> Hi Pranay,
> > > >>>
> > > >>> It is a good idea of course to keep multiple versions of
> > documentation
> > > >>> for
> > > >>> multiple releases.
> > > >>>
> > > >>> Talking in terms of priority, however, I think perhaps we need to
> > spend
> > > >>> most of our energy into first organizing and cleaning up our
> > > >>> documentation.
> > > >>> We need an API section, a user manual, a developer manual, and a
> set
> > of
> > > >>> tutorials. All of these need to be categorized and point to each
> > other
> > > in
> > > >>> hyperlinks. Right now, the documentation is heavily scattered in
> > > >>> different
> > > >>> and confusing sections. There is no "one location" for getting a
> > piece
> > > of
> > > >>> information. So for example, the business processes could be maybe
> > part
> > > >>> of
> > > >>> the "User Manual" right? We don't have such a categorization at the
> > > >>> moment
> > > >>> which dilutes value.
> > > >>>
> > > >>> Also if you think about it, good organization of this information
> > would
> > > >>> make it easier to create release-specific documentation because
> > you're
> > > >>> building on the same organized skeleton. So in short I agree with
> > your
> > > >>> approach but trying to convince you to perhaps try to focus your
> > energy
> > > >>> on
> > > >>> organizing our documentation if you have the time for it.
> > > >>>
> > > >>> Thank you as always for your initiative.
> > > >>>
> > > >>> Cheers,
> > > >>>
> > > >>> Taher Alkhateeb
> > > >>>
> > > >>> On Tue, Nov 8, 2016 at 2:08 PM, Pranay Pandey <
> > > >>> 

Re: Business Process and Use Case Library for Ecommerce ERP

[Pranay Pandey]

Thanks Jacques.

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Tue, Nov 15, 2016 at 4:44 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Makes totally sense, thanks Pranay
>
> Jacques
>
>
> Le 15/11/2016 à 08:01, Pranay Pandey a écrit :
>
>> Interestingly, there will be heavy updates to these documents and hence
>> will be updated rigorously. Going with links to history I think won't work
>> in this case. We'll need to create separate pages with tagging the name of
>> the branch or release int he document name itself e.g.
>>
>> - OFBiz 14.12
>> -- Ecommerce 14.12
>> -- Order Manager 14.12
>> ...
>> ...
>> ...
>> - OFBiz 16.12
>> -- Ecommerce 16.12
>> -- Order Manager 16.12
>>
>>
>> Best regards,
>>
>> Pranay Pandey
>> HotWax Systems
>> http://www.hotwaxsystems.com/
>>
>> On Sun, Nov 13, 2016 at 3:31 PM, Jacques Le Roux <
>> jacques.le.r...@les7arts.com> wrote:
>>
>> Hi Pranay,
>>>
>>> I like the idea, maybe you can use the same way I did it when I updated
>>> the documentation for the Gradle move.
>>>
>>> I simply referenced with a link a previous version in history, eg: "Pre
>>> Gradle version" notice at https://cwiki.apache.org/confl
>>> uence/display/OFBIZ/Addressing+Custom+Requirements+In+OFBiz
>>>
>>> Jacques
>>>
>>>
>>>
>>> Le 09/11/2016 à 13:55, Pranay Pandey a écrit :
>>>
>>> Thanks Taher for this note. Yes it is about document re-organisation and
 will help users to locate right set of document whenever needed.

 I am getting your point on priorities, but at the same time think that
 fine
 tuned user stories will older branch will help us building good set of
 QA
 artefacts for OFBiz upcoming release as well.

 I have also worked with one of my team member(Swapnil M Mane) to come up
 with a renewed OFBiz tutorial for beginners. Very soon we'll add it to
 OFBiz Confluence. Then we can discuss to upgrade it as needed for making
 it
 more easy to understand   and useful.

 Best regards,

 Pranay Pandey
 HotWax Systems
 http://www.hotwaxsystems.com/

 On Tue, Nov 8, 2016 at 4:53 PM, Taher Alkhateeb <
 slidingfilame...@gmail.com>
 wrote:

 Hi Pranay,

> It is a good idea of course to keep multiple versions of documentation
> for
> multiple releases.
>
> Talking in terms of priority, however, I think perhaps we need to spend
> most of our energy into first organizing and cleaning up our
> documentation.
> We need an API section, a user manual, a developer manual, and a set of
> tutorials. All of these need to be categorized and point to each other
> in
> hyperlinks. Right now, the documentation is heavily scattered in
> different
> and confusing sections. There is no "one location" for getting a piece
> of
> information. So for example, the business processes could be maybe part
> of
> the "User Manual" right? We don't have such a categorization at the
> moment
> which dilutes value.
>
> Also if you think about it, good organization of this information would
> make it easier to create release-specific documentation because you're
> building on the same organized skeleton. So in short I agree with your
> approach but trying to convince you to perhaps try to focus your energy
> on
> organizing our documentation if you have the time for it.
>
> Thank you as always for your initiative.
>
> Cheers,
>
> Taher Alkhateeb
>
> On Tue, Nov 8, 2016 at 2:08 PM, Pranay Pandey <
> pranay.pan...@hotwaxsystems.com> wrote:
>
> Hello Everyone,
>
>> I am thinking to make a change in document hierarchy for Business
>> Process
>> and Use Case Library for Ecommerce ERP
>> . I think we can rename
>> it
>> for branch or release.
>> E.g. we can prepare first set of documents for branch Release 14.12.
>> So
>>
>> the
>
> document hierarchy will look like:
>>
>> - Business Process and Use Case Library for Ecommerce ERP
>> -- Release 14.12
>> -- Release 16.12
>> -- and so on
>>
>> So the idea is to dedicatedly build documents for specific branch or
>> releases. This way a set of the documents will be declared to be used
>>
>> for a
>
> specific release being used. As we start preparing for the new release,
>>
>> we
>
> can copy from old release and append the additions to it. We can then
>>
>> also
>
> add test cases(with a mark of success or failure for each for all the
>> components) along with User Stories and Use Cases which will add more
>>
>> value
>
> to it.
>>
>> With its current name and structure it indicates, it's for trunk and
>>
>> having
>
> it managed on release basis will bring in more 

Re: Business Process and Use Case Library for Ecommerce ERP

[Pranay Pandey]

Thanks Rishi for the note, there is a reason why I wanted to name those
component document suffixed with Branch or Release number. For better
indexing of documents, a unique name will help.

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Tue, Nov 15, 2016 at 4:40 PM, Rishi Solanki 
wrote:

> Just one suggestion in hierachy, I'm good with the proposed hierachy as
> well.
>
> - OFBiz 14.12
> -- Ecommerce
> -- Order Manager
> ...
> ...
> ...
> - OFBiz 16.12
> -- Ecommerce
> -- Order Manager
>
> Thanks for initiative. :-)
>
>
> Rishi Solanki
> Manager, Enterprise Software Development
> HotWax Systems Pvt. Ltd.
> Direct: +91-9893287847
> http://www.hotwaxsystems.com
>
> On Tue, Nov 15, 2016 at 12:31 PM, Pranay Pandey <
> pranay.pan...@hotwaxsystems.com> wrote:
>
> > Interestingly, there will be heavy updates to these documents and hence
> > will be updated rigorously. Going with links to history I think won't
> work
> > in this case. We'll need to create separate pages with tagging the name
> of
> > the branch or release int he document name itself e.g.
> >
> > - OFBiz 14.12
> > -- Ecommerce 14.12
> > -- Order Manager 14.12
> > ...
> > ...
> > ...
> > - OFBiz 16.12
> > -- Ecommerce 16.12
> > -- Order Manager 16.12
> >
> >
> > Best regards,
> >
> > Pranay Pandey
> > HotWax Systems
> > http://www.hotwaxsystems.com/
> >
> > On Sun, Nov 13, 2016 at 3:31 PM, Jacques Le Roux <
> > jacques.le.r...@les7arts.com> wrote:
> >
> > > Hi Pranay,
> > >
> > > I like the idea, maybe you can use the same way I did it when I updated
> > > the documentation for the Gradle move.
> > >
> > > I simply referenced with a link a previous version in history, eg: "Pre
> > > Gradle version" notice at https://cwiki.apache.org/confl
> > > uence/display/OFBIZ/Addressing+Custom+Requirements+In+OFBiz
> > >
> > > Jacques
> > >
> > >
> > >
> > > Le 09/11/2016 à 13:55, Pranay Pandey a écrit :
> > >
> > >> Thanks Taher for this note. Yes it is about document re-organisation
> and
> > >> will help users to locate right set of document whenever needed.
> > >>
> > >> I am getting your point on priorities, but at the same time think that
> > >> fine
> > >> tuned user stories will older branch will help us building good set of
> > QA
> > >> artefacts for OFBiz upcoming release as well.
> > >>
> > >> I have also worked with one of my team member(Swapnil M Mane) to come
> up
> > >> with a renewed OFBiz tutorial for beginners. Very soon we'll add it to
> > >> OFBiz Confluence. Then we can discuss to upgrade it as needed for
> making
> > >> it
> > >> more easy to understand   and useful.
> > >>
> > >> Best regards,
> > >>
> > >> Pranay Pandey
> > >> HotWax Systems
> > >> http://www.hotwaxsystems.com/
> > >>
> > >> On Tue, Nov 8, 2016 at 4:53 PM, Taher Alkhateeb <
> > >> slidingfilame...@gmail.com>
> > >> wrote:
> > >>
> > >> Hi Pranay,
> > >>>
> > >>> It is a good idea of course to keep multiple versions of
> documentation
> > >>> for
> > >>> multiple releases.
> > >>>
> > >>> Talking in terms of priority, however, I think perhaps we need to
> spend
> > >>> most of our energy into first organizing and cleaning up our
> > >>> documentation.
> > >>> We need an API section, a user manual, a developer manual, and a set
> of
> > >>> tutorials. All of these need to be categorized and point to each
> other
> > in
> > >>> hyperlinks. Right now, the documentation is heavily scattered in
> > >>> different
> > >>> and confusing sections. There is no "one location" for getting a
> piece
> > of
> > >>> information. So for example, the business processes could be maybe
> part
> > >>> of
> > >>> the "User Manual" right? We don't have such a categorization at the
> > >>> moment
> > >>> which dilutes value.
> > >>>
> > >>> Also if you think about it, good organization of this information
> would
> > >>> make it easier to create release-specific documentation because
> you're
> > >>> building on the same organized skeleton. So in short I agree with
> your
> > >>> approach but trying to convince you to perhaps try to focus your
> energy
> > >>> on
> > >>> organizing our documentation if you have the time for it.
> > >>>
> > >>> Thank you as always for your initiative.
> > >>>
> > >>> Cheers,
> > >>>
> > >>> Taher Alkhateeb
> > >>>
> > >>> On Tue, Nov 8, 2016 at 2:08 PM, Pranay Pandey <
> > >>> pranay.pan...@hotwaxsystems.com> wrote:
> > >>>
> > >>> Hello Everyone,
> > 
> >  I am thinking to make a change in document hierarchy for Business
> >  Process
> >  and Use Case Library for Ecommerce ERP
> >  . I think we can
> rename
> >  it
> >  for branch or release.
> >  E.g. we can prepare first set of documents for branch Release 14.12.
> > So
> > 
> > >>> the
> > >>>
> >  document hierarchy will look like:
> > 
> >  - Business Process and Use Case Library for Ecommerce ERP
> >  -- Release 14.12
> >  

Re: Business Process and Use Case Library for Ecommerce ERP

[Jacques Le Roux]

Makes totally sense, thanks Pranay

Jacques

Le 15/11/2016 à 08:01, Pranay Pandey a écrit :

Interestingly, there will be heavy updates to these documents and hence
will be updated rigorously. Going with links to history I think won't work
in this case. We'll need to create separate pages with tagging the name of
the branch or release int he document name itself e.g.

- OFBiz 14.12
-- Ecommerce 14.12
-- Order Manager 14.12
...
...
...
- OFBiz 16.12
-- Ecommerce 16.12
-- Order Manager 16.12


Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Sun, Nov 13, 2016 at 3:31 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Hi Pranay,

I like the idea, maybe you can use the same way I did it when I updated
the documentation for the Gradle move.

I simply referenced with a link a previous version in history, eg: "Pre
Gradle version" notice at https://cwiki.apache.org/confl
uence/display/OFBIZ/Addressing+Custom+Requirements+In+OFBiz

Jacques



Le 09/11/2016 à 13:55, Pranay Pandey a écrit :


Thanks Taher for this note. Yes it is about document re-organisation and
will help users to locate right set of document whenever needed.

I am getting your point on priorities, but at the same time think that
fine
tuned user stories will older branch will help us building good set of QA
artefacts for OFBiz upcoming release as well.

I have also worked with one of my team member(Swapnil M Mane) to come up
with a renewed OFBiz tutorial for beginners. Very soon we'll add it to
OFBiz Confluence. Then we can discuss to upgrade it as needed for making
it
more easy to understand   and useful.

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

On Tue, Nov 8, 2016 at 4:53 PM, Taher Alkhateeb <
slidingfilame...@gmail.com>
wrote:

Hi Pranay,

It is a good idea of course to keep multiple versions of documentation
for
multiple releases.

Talking in terms of priority, however, I think perhaps we need to spend
most of our energy into first organizing and cleaning up our
documentation.
We need an API section, a user manual, a developer manual, and a set of
tutorials. All of these need to be categorized and point to each other in
hyperlinks. Right now, the documentation is heavily scattered in
different
and confusing sections. There is no "one location" for getting a piece of
information. So for example, the business processes could be maybe part
of
the "User Manual" right? We don't have such a categorization at the
moment
which dilutes value.

Also if you think about it, good organization of this information would
make it easier to create release-specific documentation because you're
building on the same organized skeleton. So in short I agree with your
approach but trying to convince you to perhaps try to focus your energy
on
organizing our documentation if you have the time for it.

Thank you as always for your initiative.

Cheers,

Taher Alkhateeb

On Tue, Nov 8, 2016 at 2:08 PM, Pranay Pandey <
pranay.pan...@hotwaxsystems.com> wrote:

Hello Everyone,

I am thinking to make a change in document hierarchy for Business
Process
and Use Case Library for Ecommerce ERP
. I think we can rename
it
for branch or release.
E.g. we can prepare first set of documents for branch Release 14.12. So


the


document hierarchy will look like:

- Business Process and Use Case Library for Ecommerce ERP
-- Release 14.12
-- Release 16.12
-- and so on

So the idea is to dedicatedly build documents for specific branch or
releases. This way a set of the documents will be declared to be used


for a


specific release being used. As we start preparing for the new release,


we


can copy from old release and append the additions to it. We can then


also


add test cases(with a mark of success or failure for each for all the
components) along with User Stories and Use Cases which will add more


value


to it.

With its current name and structure it indicates, it's for trunk and


having


it managed on release basis will bring in more attention to it.

Please let me know your thoughts on it. If no objections are seen I
would
like to make this change in a day or two.

Best regards,

Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/

Re: Business Process and Use Case Library for Ecommerce ERP

[Rishi Solanki]

Just one suggestion in hierachy, I'm good with the proposed hierachy as
well.

- OFBiz 14.12
-- Ecommerce
-- Order Manager
...
...
...
- OFBiz 16.12
-- Ecommerce
-- Order Manager

Thanks for initiative. :-)


Rishi Solanki
Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com

On Tue, Nov 15, 2016 at 12:31 PM, Pranay Pandey <
pranay.pan...@hotwaxsystems.com> wrote:

> Interestingly, there will be heavy updates to these documents and hence
> will be updated rigorously. Going with links to history I think won't work
> in this case. We'll need to create separate pages with tagging the name of
> the branch or release int he document name itself e.g.
>
> - OFBiz 14.12
> -- Ecommerce 14.12
> -- Order Manager 14.12
> ...
> ...
> ...
> - OFBiz 16.12
> -- Ecommerce 16.12
> -- Order Manager 16.12
>
>
> Best regards,
>
> Pranay Pandey
> HotWax Systems
> http://www.hotwaxsystems.com/
>
> On Sun, Nov 13, 2016 at 3:31 PM, Jacques Le Roux <
> jacques.le.r...@les7arts.com> wrote:
>
> > Hi Pranay,
> >
> > I like the idea, maybe you can use the same way I did it when I updated
> > the documentation for the Gradle move.
> >
> > I simply referenced with a link a previous version in history, eg: "Pre
> > Gradle version" notice at https://cwiki.apache.org/confl
> > uence/display/OFBIZ/Addressing+Custom+Requirements+In+OFBiz
> >
> > Jacques
> >
> >
> >
> > Le 09/11/2016 à 13:55, Pranay Pandey a écrit :
> >
> >> Thanks Taher for this note. Yes it is about document re-organisation and
> >> will help users to locate right set of document whenever needed.
> >>
> >> I am getting your point on priorities, but at the same time think that
> >> fine
> >> tuned user stories will older branch will help us building good set of
> QA
> >> artefacts for OFBiz upcoming release as well.
> >>
> >> I have also worked with one of my team member(Swapnil M Mane) to come up
> >> with a renewed OFBiz tutorial for beginners. Very soon we'll add it to
> >> OFBiz Confluence. Then we can discuss to upgrade it as needed for making
> >> it
> >> more easy to understand   and useful.
> >>
> >> Best regards,
> >>
> >> Pranay Pandey
> >> HotWax Systems
> >> http://www.hotwaxsystems.com/
> >>
> >> On Tue, Nov 8, 2016 at 4:53 PM, Taher Alkhateeb <
> >> slidingfilame...@gmail.com>
> >> wrote:
> >>
> >> Hi Pranay,
> >>>
> >>> It is a good idea of course to keep multiple versions of documentation
> >>> for
> >>> multiple releases.
> >>>
> >>> Talking in terms of priority, however, I think perhaps we need to spend
> >>> most of our energy into first organizing and cleaning up our
> >>> documentation.
> >>> We need an API section, a user manual, a developer manual, and a set of
> >>> tutorials. All of these need to be categorized and point to each other
> in
> >>> hyperlinks. Right now, the documentation is heavily scattered in
> >>> different
> >>> and confusing sections. There is no "one location" for getting a piece
> of
> >>> information. So for example, the business processes could be maybe part
> >>> of
> >>> the "User Manual" right? We don't have such a categorization at the
> >>> moment
> >>> which dilutes value.
> >>>
> >>> Also if you think about it, good organization of this information would
> >>> make it easier to create release-specific documentation because you're
> >>> building on the same organized skeleton. So in short I agree with your
> >>> approach but trying to convince you to perhaps try to focus your energy
> >>> on
> >>> organizing our documentation if you have the time for it.
> >>>
> >>> Thank you as always for your initiative.
> >>>
> >>> Cheers,
> >>>
> >>> Taher Alkhateeb
> >>>
> >>> On Tue, Nov 8, 2016 at 2:08 PM, Pranay Pandey <
> >>> pranay.pan...@hotwaxsystems.com> wrote:
> >>>
> >>> Hello Everyone,
> 
>  I am thinking to make a change in document hierarchy for Business
>  Process
>  and Use Case Library for Ecommerce ERP
>  . I think we can rename
>  it
>  for branch or release.
>  E.g. we can prepare first set of documents for branch Release 14.12.
> So
> 
> >>> the
> >>>
>  document hierarchy will look like:
> 
>  - Business Process and Use Case Library for Ecommerce ERP
>  -- Release 14.12
>  -- Release 16.12
>  -- and so on
> 
>  So the idea is to dedicatedly build documents for specific branch or
>  releases. This way a set of the documents will be declared to be used
> 
> >>> for a
> >>>
>  specific release being used. As we start preparing for the new
> release,
> 
> >>> we
> >>>
>  can copy from old release and append the additions to it. We can then
> 
> >>> also
> >>>
>  add test cases(with a mark of success or failure for each for all the
>  components) along with User Stories and Use Cases which will add more
> 
> >>> value
> >>>
>  to it.
> 
>  With its current name and