Re: Request to become a contributor

[Ashish Vijaywargiya]

Done, Thanks Tanmay! Here you go -
https://cwiki.apache.org/confluence/x/AIRMAg

--
Kind Regards
Ashish Vijaywargiya
HotWax Systems - est. 1997
Connect with me on LinkedIn -
https://www.linkedin.com/in/ashishvijaywargiya1

On Fri, Jul 1, 2016 at 6:51 PM, Tanmay Muley  wrote:

> Hello,
>
> Please register me as OFBiz contributor.
> My account details are as follows :
>
> Full Name : Tanmay Muley
> User Name : tanmay.muley
> Email : tanmay.mu...@hotwaxsystems.com 
>
> I have signed the ICLA
> https://people.apache.org/unlistedclas.html
> <
> https://www.google.com/url?q=https%3A%2F%2Fpeople.apache.org%2Funlistedclas.html=D=1=AFQjCNHVf2UABS2lcykR7HChP0QJk-kI-Q
> >
>
> --
> Tanmay Muley
> Enterprise Embedded Engineer
> Hotwax Systems
>

Re: Update of the wiki "Apache OFBiz User List" page

[Jacques Le Roux]

Hi,

I received this message from Corent Technology Inc  and when I get there I see nothning interesting and related with OFBiz but 
hear an annoying musak (I listen to online music constantly and I hate this kind of intrusion so 90s)


So I have decided to unilaterally drop the line in the wiki page.

Done, this can of course be amended with an explanation...

It also seems to me that http://syracus.net/ no longer works and should be 
dropped...

Jacques


Le 01/07/2016 à 17:37, Corent Technology Inc a écrit :


Dear Jacques Le Roux,

Thank You for your interest in Corent Tech. A member of our team will reach out 
to you.

Kindly activate your account by clicking on the following link: 
http://www.corenttech.com/images/feedback/activation.php?emailId=jacques.le.r...@les7arts.com=Demo


Thanks & Regards,
Sales Team,
Corent Technology Inc.




Le 01/07/2016 à 22:29, Jacques Le Roux a écrit :

Thanks Gil

Jacques


Le 01/07/2016 à 18:32, gil portenseigne a écrit :

Thanks Jacques,

I did removed Neogia that is do no exists anymore !

Gil

On 01/07/2016 17:40, Jacques Le Roux wrote:

Hi All,

At the top of https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+User+List there is a list of "Products and Projects based on Apache 
OFBiz"


At the moment

http://www.orrtiz.com/

and

http://www.neogia.org/wiki/index.php/D%C3%A9mo_en_ligne

don't respond. Please do the needed or tell us to remove them.

Thanks

Jacques

Re: Update of the wiki "Apache OFBiz User List" page

[Jacques Le Roux]

Thanks Gil

Jacques


Le 01/07/2016 à 18:32, gil portenseigne a écrit :

Thanks Jacques,

I did removed Neogia that is do no exists anymore !

Gil

On 01/07/2016 17:40, Jacques Le Roux wrote:

Hi All,

At the top of https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+User+List there is a list of "Products and Projects based on Apache 
OFBiz"


At the moment

http://www.orrtiz.com/

and

http://www.neogia.org/wiki/index.php/D%C3%A9mo_en_ligne

don't respond. Please do the needed or tell us to remove them.

Thanks

Jacques

How do do drop shipments

[Skip]

Drop shipments are a fact of life in many businesses.  In Ofbiz, an order is
invoiced when it is packed for shipment.  However, in the case of drop
shipments, we do not know when the supplier actually ships the product(s).
To avoid errors, I would like to write something to keep track of these drop
shipments so someone can stay on top of it.

I am wondering if any of you face similar problems and if so, how you handle
it.

Thanks in advance

Skip

Re: Update of the wiki "Apache OFBiz User List" page

[gil portenseigne]

Thanks Jacques,

I did removed Neogia that is do no exists anymore !

Gil

On 01/07/2016 17:40, Jacques Le Roux wrote:

Hi All,

At the top of 
https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+User+List 
there is a list of "Products and Projects based on Apache OFBiz"


At the moment

http://www.orrtiz.com/

and

http://www.neogia.org/wiki/index.php/D%C3%A9mo_en_ligne

don't respond. Please do the needed or tell us to remove them.

Thanks

Jacques

Re: Update of the wiki "Apache OFBiz User List" page

[Pierre Smits]

Thanks Jacques,

I am looking into the ORRTIZ.COM situation. It seems DNS related.

Best regards,

Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

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

On Fri, Jul 1, 2016 at 5:40 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Hi All,
>
> At the top of
> https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+User+List
> there is a list of "Products and Projects based on Apache OFBiz"
>
> At the moment
>
> http://www.orrtiz.com/
>
> and
>
> http://www.neogia.org/wiki/index.php/D%C3%A9mo_en_ligne
>
> don't respond. Please do the needed or tell us to remove them.
>
> Thanks
>
> Jacques
>
>

Re: Update of the wiki "Apache OFBiz User List" page

[Jacques Le Roux]

I just noticed that

http://www.businessesnetwork.com/control/automation/

is in the same situation.

I'll also try the Corent application (demo) ...

Jacques


Le 01/07/2016 à 17:40, Jacques Le Roux a écrit :

Hi All,

At the top of https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+User+List 
there is a list of "Products and Projects based on Apache OFBiz"

At the moment

http://www.orrtiz.com/

and

http://www.neogia.org/wiki/index.php/D%C3%A9mo_en_ligne

don't respond. Please do the needed or tell us to remove them.

Thanks

Jacques

Update of the wiki "Apache OFBiz User List" page

[Jacques Le Roux]

Hi All,

At the top of https://cwiki.apache.org/confluence/display/OFBIZ/Apache+OFBiz+User+List 
there is a list of "Products and Projects based on Apache OFBiz"

At the moment

http://www.orrtiz.com/

and

http://www.neogia.org/wiki/index.php/D%C3%A9mo_en_ligne

don't respond. Please do the needed or tell us to remove them.

Thanks

Jacques

Request to become a contributor

[Tanmay Muley]

Hello,

Please register me as OFBiz contributor.
My account details are as follows :

Full Name : Tanmay Muley
User Name : tanmay.muley
Email : tanmay.mu...@hotwaxsystems.com 

I have signed the ICLA
https://people.apache.org/unlistedclas.html


-- 
Tanmay Muley
Enterprise Embedded Engineer
Hotwax Systems

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

[Charl Bouwer]

Hi all

Where does it leave a new user that is planning to become a contributor. I
am past the R stage and meeting my business partner next week to inform
him I already have 2 possibly 3 clients that is interested in a POC. In the
next month I am building a POC based on the 13.07 build.

I was already able to setup eclipse with debugging enabled and have both
the trunk and 13.07 SVN repositories. I am busy doing the same with
Intellij/GIT setup, my preferred IDE environment. I am planning to use the
POC to customise for my region, including the initial seed data. Which in
turn will lead to me working on the multi tenancy aspect.

Should I continue with 13.07 as base with the intention to have a
production server in the next say 3-6 months.
Any suggestions on how I should proceed from here?

Sorry I only subscribed to the dev-list today

Thanks
Charl


On Fri, Jul 1, 2016 at 9:01 AM, Sharan Foga  wrote:

> Hi Pierre
>
> I'd be happy summarise what my understanding is, but beforehand I'd like
> to point out that any decision on this discussion thread isn't “the shared
> conclusion of the PMC”. The discussion was raised on this list specifically
> to get feedback from our community and it's from that feedback that any
> conclusions are drawn or decisions taken .
>
> My understanding is that there was general consensus for the following:
>
> - There would be no more releases from 13.07 so the current release that
> is out would be the last one in that series
>
> - We would not backport any of the gradle changes into the 14.12. or 15.12
> branches because it would cause instability
>
> - We would leave 14.12 and 15.12 as unreleased branches as they are now
> (and not make them into releases as to do that we would need to remove all
> the jar files and this would create instability).
>
> - We would focus on implementing the gradle changes into the trunk and
> then creating and stabilising a 16.x release ASAP
>
> - The benefits for our community are that developers and service providers
> will still have access to the complete codebase for 14.12 and 15.12
> including the special purpose components to be able to support their client
> base.
>
> I suggested taking the discussion to the development list so that we can
> talk in more detail about the release planning and also the duration of
> support the unreleased branches. This again, will be a community discussion
> and decision. Once we have these details we can communicate them to our
> user community.
>
> This was my understanding, so if anyone has a another interpretation or
> understanding then please feel free to comment.
>
> Thanks
> Sharan
>
> On 2016-06-30 15:40 (+0200), Pierre Smits  wrote:
> > It seems to me that Sharan is jumping the fence a bit to soon. Multiple
> > suggestions have gathered support.
> > This makes any 'this solution', without repeating what that solution is ,
> > multi-interpretable and would not only continue the discussion. But also
> > the confusion.
> >
> > I suggest to repeat once more what the shared conclusion of the PMC is
> > regarding this discussion, so that the entire community can anticipate to
> > what is coming in the near future, and what the PMC will take to the dev
> ml
> > for planning purposes regarding the short term actions.
> >
> > Best regards,
> >
> >
> > Pierre Smits
> >
> > ORRTIZ.COM 
> > OFBiz based solutions & services
> >
> > OFBiz Extensions Marketplace
> > http://oem.ofbizci.net/oci-2/
> >
> > On Thu, Jun 30, 2016 at 2:26 PM, Sharan Foga 
> wrote:
> >
> > > Hi Everyone
> > >
> > > Thanks very much for the feedback. I'm glad that this solution will
> > > resolve our current problems without taking away any functionality
> from the
> > > service providers or developers that are using the unreleased branches.
> > >
> > > Our next step will be to create and stabilise the 16.x release ASAP so
> > > that our user community will have another release available. This will
> > > become our top priority.
> > >
> > > I suggest that we close off the discussion now as I think we've had
> quite
> > > a detailed discussion and it looks like we have come to a consensus and
> > > resolved the issues. We can now take the discussion back to the dev
> list
> > > where we can talk about the timings, release roadmap and also the
> support
> > > timeframe for the unreleased branches.
> > >
> > > Thanks
> > > Sharan
> > >
> > > On 2016-06-30 11:01 (+0200), Michael Brohl 
> > > wrote:
> > > > Great idea, +1
> > > >
> > > > Michael Brohl
> > > > ecomify GmbH
> > > > www.ecomify.de
> > > >
> > > >
> > > > Am 30.06.16 um 09:05 schrieb Sharan Foga:
> > > > > Thanks for the response -Jacopo. (You posted a minute before I
> did!)
> > > > >
> > > > > Anyway I think that I might have an idea that could solve our
> problem
> > > – let's just leave 14.12 and 15.12 as unreleased branches.
> > > > >
> > > > > The jar 

Fwd: [jira] Subscription: Patch Available in OFBiz

[Pierre Smits]

FYI.


Pierre Smits

ORRTIZ.COM 
OFBiz based solutions & services

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

-- Forwarded message --
From: 
Date: Fri, Jul 1, 2016 at 2:01 AM
Subject: [jira] Subscription: Patch Available in OFBiz
To: pierre.sm...@gmail.com


Issue Subscription
Filter: Patch Available in OFBiz (200 of 263 issues)
Patch Available issues in OFBiz
Subscriber: pfm.smits

Key Summary
OFBIZ-7683  Error occurred when making Shopping list public/private from
Party Detail screen
https://issues.apache.org/jira/browse/OFBIZ-7683
OFBIZ-7679  Asset Maintenance : FTL formatting
https://issues.apache.org/jira/browse/OFBIZ-7679
OFBIZ-7678  BI : FTL formatting
https://issues.apache.org/jira/browse/OFBIZ-7678
OFBIZ-7676  Forum group name is not showing up on forum group roles and
purposes screens
https://issues.apache.org/jira/browse/OFBIZ-7676
OFBIZ-7673  Create demo PartyStatus data for existing parties for
applications component
https://issues.apache.org/jira/browse/OFBIZ-7673
OFBIZ-7672  Create demo PartyStatus data for existing parties for special
purpose component
https://issues.apache.org/jira/browse/OFBIZ-7672
OFBIZ-7671  SpecialPurpose/googlebase: Correct all the checkboxes and radio
buttons in all the googlebase FTLs.
https://issues.apache.org/jira/browse/OFBIZ-7671
OFBIZ-7668  SpecialPurpose/ebay: Correct all the checkboxes and radio
buttons in all the ebay FTLs.
https://issues.apache.org/jira/browse/OFBIZ-7668
OFBIZ-7663  FromDate and ThruDate shows empty for WorkEffort Children
https://issues.apache.org/jira/browse/OFBIZ-7663
OFBIZ-7654  Success message should be shown on screen for successfully
applied promotion
https://issues.apache.org/jira/browse/OFBIZ-7654
OFBIZ-7653  OFBIZ-7649: Display From date with default now() on all screens
under Manufacturing Application
https://issues.apache.org/jira/browse/OFBIZ-7653
OFBIZ-7652  "Tasks" menu is showing selected when click in scrum component
https://issues.apache.org/jira/browse/OFBIZ-7652
OFBIZ-7648  Page bottom navigation problem with grid and include-grid
https://issues.apache.org/jira/browse/OFBIZ-7648
OFBIZ-7636  Framework : FTL formatting
https://issues.apache.org/jira/browse/OFBIZ-7636
OFBIZ-7630  Enforce noninstantiability to ServiceEcaUtil class
https://issues.apache.org/jira/browse/OFBIZ-7630
OFBIZ-7629  Add content lookup when adding Content to Product Config Item
https://issues.apache.org/jira/browse/OFBIZ-7629
OFBIZ-7627  Workeffort Agreement Appls redirect to wrong page and also
gives error
https://issues.apache.org/jira/browse/OFBIZ-7627
OFBIZ-7622  Add "changeByUserLoginId" field for CustRequestStatus
https://issues.apache.org/jira/browse/OFBIZ-7622
OFBIZ-7621  Add "changeByUserLoginId" field for RequirementStatus
https://issues.apache.org/jira/browse/OFBIZ-7621
OFBIZ-7620  Add "changeByUserLoginId" field for ContactListCommStatus
https://issues.apache.org/jira/browse/OFBIZ-7620
OFBIZ-7619  Add "changeByUserLoginId" field for BudgetStatus
https://issues.apache.org/jira/browse/OFBIZ-7619
OFBIZ-7618  Add "changeByUserLoginId" field for ShipmentStatus
https://issues.apache.org/jira/browse/OFBIZ-7618
OFBIZ-7617  Add "changeByUserLoginId" field for InvoiceStatus
https://issues.apache.org/jira/browse/OFBIZ-7617
OFBIZ-7616  Add "changeByUserLoginId" field for PartyStatus
https://issues.apache.org/jira/browse/OFBIZ-7616
OFBIZ-7609  Work Effort keywords are not listing
https://issues.apache.org/jira/browse/OFBIZ-7609
OFBIZ-7608  On Product>>Agreement screen rename the button label to create
new agreement from "Edit Agreement" to "Create Agreement"
https://issues.apache.org/jira/browse/OFBIZ-7608
OFBIZ-7601  Enforce noninstantiability to UtilURL class
https://issues.apache.org/jira/browse/OFBIZ-7601
OFBIZ-7600  Enforce noninstantiability to UtilPlist class
https://issues.apache.org/jira/browse/OFBIZ-7600
OFBIZ-7599  Entered To Name is not getting stored when creating Party
Invitation
https://issues.apache.org/jira/browse/OFBIZ-7599
OFBIZ-7597  Entity auto services doesn't returns success message
https://issues.apache.org/jira/browse/OFBIZ-7597
OFBIZ-7593  Enforce noninstantiability to UtilNumber class
https://issues.apache.org/jira/browse/OFBIZ-7593
OFBIZ-7591  Enforce noninstantiability to UtilJavaParse class
https://issues.apache.org/jira/browse/OFBIZ-7591
OFBIZ-7590  Enforce noninstantiability to UtilIO class
https://issues.apache.org/jira/browse/OFBIZ-7590
OFBIZ-7589  Enforce noninstantiability to UtilHttp class

Re: [DISCUSSION] Anticipate the end of life of the 13.07 branch and backport some non-bug related changes to the 14.12 and 15.12 branches

[Sharan Foga]

Hi Pierre

I'd be happy summarise what my understanding is, but beforehand I'd like to 
point out that any decision on this discussion thread isn't “the shared 
conclusion of the PMC”. The discussion was raised on this list specifically 
to get feedback from our community and it's from that feedback that any 
conclusions are drawn or decisions taken . 

My understanding is that there was general consensus for the following:

- There would be no more releases from 13.07 so the current release that is out 
would be the last one in that series

- We would not backport any of the gradle changes into the 14.12. or 15.12 
branches because it would cause instability

- We would leave 14.12 and 15.12 as unreleased branches as they are now (and 
not make them into releases as to do that we would need to remove all the jar 
files and this would create instability). 

- We would focus on implementing the gradle changes into the trunk and then 
creating and stabilising a 16.x release ASAP

- The benefits for our community are that developers and service providers will 
still have access to the complete codebase for 14.12 and 15.12 including the 
special purpose components to be able to support their client base.

I suggested taking the discussion to the development list so that we can talk 
in more detail about the release planning and also the duration of support the 
unreleased branches. This again, will be a community discussion and decision. 
Once we have these details we can communicate them to our user community.

This was my understanding, so if anyone has a another interpretation or 
understanding then please feel free to comment.

Thanks
Sharan

On 2016-06-30 15:40 (+0200), Pierre Smits  wrote: 
> It seems to me that Sharan is jumping the fence a bit to soon. Multiple
> suggestions have gathered support.
> This makes any 'this solution', without repeating what that solution is ,
> multi-interpretable and would not only continue the discussion. But also
> the confusion.
> 
> I suggest to repeat once more what the shared conclusion of the PMC is
> regarding this discussion, so that the entire community can anticipate to
> what is coming in the near future, and what the PMC will take to the dev ml
> for planning purposes regarding the short term actions.
> 
> Best regards,
> 
> 
> Pierre Smits
> 
> ORRTIZ.COM 
> OFBiz based solutions & services
> 
> OFBiz Extensions Marketplace
> http://oem.ofbizci.net/oci-2/
> 
> On Thu, Jun 30, 2016 at 2:26 PM, Sharan Foga  wrote:
> 
> > Hi Everyone
> >
> > Thanks very much for the feedback. I'm glad that this solution will
> > resolve our current problems without taking away any functionality from the
> > service providers or developers that are using the unreleased branches.
> >
> > Our next step will be to create and stabilise the 16.x release ASAP so
> > that our user community will have another release available. This will
> > become our top priority.
> >
> > I suggest that we close off the discussion now as I think we've had quite
> > a detailed discussion and it looks like we have come to a consensus and
> > resolved the issues. We can now take the discussion back to the dev list
> > where we can talk about the timings, release roadmap and also the support
> > timeframe for the unreleased branches.
> >
> > Thanks
> > Sharan
> >
> > On 2016-06-30 11:01 (+0200), Michael Brohl 
> > wrote:
> > > Great idea, +1
> > >
> > > Michael Brohl
> > > ecomify GmbH
> > > www.ecomify.de
> > >
> > >
> > > Am 30.06.16 um 09:05 schrieb Sharan Foga:
> > > > Thanks for the response -Jacopo. (You posted a minute before I did!)
> > > >
> > > > Anyway I think that I might have an idea that could solve our problem
> > – let's just leave 14.12 and 15.12 as unreleased branches.
> > > >
> > > > The jar issue is only an issue if we want to convert the unreleased
> > branches into a release. Unreleased they can contain the jar files and the
> > special purpose components etc – but if we want to release them then 
> > we
> > need to fix the jar file problem before it can be released.
> > > >
> > > > Christian mentions that people are using the unreleased branches, so
> > by leaving them unreleased, we are actually giving our users something that
> > can help them move from 13.07.
> > > >
> > > > So I suggest that we seriously consider leaving 14.12 and 15.12 as
> > unreleased branches.
> > > >
> > > > For the next point – I think our next release should be the 16.x 
> > > > –
> > so that means that we are not backporting any changes and can take a branch
> > directly from the trunk once the gradle changes have been applied.
> > > >
> > > > Comments anyone?
> > > >
> > > > Thanks
> > > > Sharan
> > > >
> > > >
> > > > On 2016-06-30 07:25 (+0200), Jacopo Cappellato <
> > jacopo.cappell...@hotwaxsystems.com> wrote:
> > > >> On Wed, Jun 29, 2016 at 11:49 AM, Christian Geisert <