Re: Re-designing the ‘Security’ interface

[Kev2600]

unsubscribe

On Fri, May 10, 2019, 12:53 PM Mathieu Lirzin, 
wrote:

> Hello,
>
> I have opened the ticket OFBIZ-11019 which deprecates a method in the
> ‘org.apache.ofbiz.security.Security’ interface (see rationale in the
> JIRA ticket). If nobody disagree in the meantime, I will commit the
> attached patch in a week.
>
> With OFBIZ-11019, near half of the declarations of that interface are
> now deprecated which is a symptom a poor initial design.  As a
> consequence I think it is time to consider re-designing a new interface
> to superseed ‘org.apache.ofbiz.security.Security’.
>
> In order to achieve a better design, it would help if people currently
> implementing ‘org.apache.ofbiz.security.Security’ outside of the
> framework could describe their use-case and requirements.
>
> If nobody step-up, It will consider that as a sign that this extension
> mechanism might not be useful anymore and could be removed.
>
> Thanks in advance.
>
> [1] https://issues.apache.org/jira/browse/OFBIZ-11019
>
> --
> Mathieu Lirzin
> GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37
>

Re: Reviving the OFBiz community day

[Kev2600]

Unsubscibe

On Thu, May 9, 2019 at 8:42 AM Pawan Verma 
wrote:

> +1 Swapnil
>
> --
> Kind Regards,
> *Pawan Verma*
>
>
> On Thu, May 9, 2019 at 4:05 PM Swapnil M Mane 
> wrote:
>
> > Thanks so much everyone for your comments.
> >
> > The community days are organized once per quarter so a total of four (4)
> > events throughout the year. Since we skipped the February 2019 month.
> Here
> > are the proposed dates for this year's community day.
> > Contributors can select any single day based on there availability and
> > preferences.
> >
> >
> >- Q1 - Community Days *February 2019*  - N/A
> >
> >
> >- Q2 - Community Days *May 2019* are *Friday 24th, Saturday 25th,
> Sunday
> >26th, Monday 27th and Tuesday 28th*
> >
> >
> >- Q3 - Community Days *August 2019* are *Friday 23rd, Saturday 24th,
> >Sunday 25th, Monday 26th and Tuesday 27th*
> >
> >
> >- Q4 - Community Days* November 2019 *are *Friday 22nd, Saturday 23rd,
> >Sunday 24th, Monday 25th and Tuesday 26nd*
> >
> >
> > If we are fine these days, I will share the *detailed* updates on user's
> > mailing list.
> >
> >
> > - Thanks & Regards,
> > Swapnil M Mane,
> > ofbiz.apache.org
> >
> >
> >
> > On Fri, Apr 26, 2019 at 2:06 PM Nicolas Malin 
> > wrote:
> >
> > > I follow you on this way :)
> > >
> > > On 26/04/2019 09:09, Sanjay Yadav wrote:
> > > > Nice initiative, Swapnil. I am in for community day.
> > > >
> > > > Best Regards,
> > > >
> > > > *Sanjay Yadav* | Manager, QA
> > > > HotWax Systems 
> > > > 80, Scheme No. 78, Indore, M.P. 452010, India
> > > > Mobile Phone: 787 918 8830 | Linkedin: Sanjay-Yadav
> > > > 
> > > >
> > > >
> > > > On Thu, Apr 25, 2019 at 10:54 AM Swapnil M Mane <
> > swapnilmm...@apache.org
> > > >
> > > > wrote:
> > > >
> > > >> Hello team,
> > > >> We are having a great community, I would like to thank everyone for
> > > their
> > > >> participation.
> > > >>
> > > >> In year 2017, we start celebrating the OFBiz community days [1].
> > > >> The contribution during community days played very significant role
> in
> > > >> improvement of framework.
> > > >> Should we start this celebration again, thought?
> > > >>
> > > >>
> > > >> [1]
> > > https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Community+Days
> > > >>
> > > >>
> > > >> - Best Regards,
> > > >> Swapnil M Mane,
> > > >> ofbiz.apache.org
> > > >>
> > >
> >
>

Re: Policy on commit

[Kev2600]

Unsubscribe

On Thu, Aug 30, 2018 at 7:04 AM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Thanks Nicolas,
>
> I'll wait a bit more for opinions and if we mostly agree will being to
> write a draft.
>
> Not a hurry, but of course all opinions, and especially ideas even if in
> draft form , are welcome!
>
> Jacques
>
>
> Le 30/08/2018 à 11:20, Nicolas Malin a écrit :
> > Hi Jacques,
> >
> > I agree with the main Michael's idea and yours to load it as best
> practice.
> >
> > Now I'm not the better man to rewrite a formulation. But if no
> inspiration here I can try a first prose
> >
> > Nicolas
> >
> >
> > On 27/08/2018 10:15, Jacques Le Roux wrote:
> >> Hi Michael, All,
> >>
> >> First, thank you Michael for your effort in trying to clarify what to
> discuss in dev ML (this has already been , when to revert a commit, and
> I'll
> >> add relations with Jiras status.
> >> I know it's important for you to correctly deliver the information
> about OFBiz activity in the monthly blog post
> >>
> >> My goal here is to decide if we should write best practices for that in
> >>
> https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Contributors+Best+Practices
> >> <
> https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Contributors+Best+Practices
> >
> >>
> >> And if yes, to clearly write them. This to avoid future confusion and
> conflicts in the community about these subjects.
> >>
> >> Before beginning on that, I have already collected some information,
> I'd like to be sure we all agree about doing so. Then, if we agree we can
> >> begin to discuss what to write...
> >>
> >> Thanks for your attention
> >>
> >> Jacques
> >>
> >>
> >> Le 19/08/2018 à 11:28, Michael Brohl a écrit :
> >>> I have not the time to dig into the specific details right now so will
> just give my thoughts on the process in general because of the citations:
> >>>
> >>> 1. we have to distinguish between (a) completely new functionality or
> major refactorings and (b) the enhancement of functionality which is
> already
> >>> in the code base
> >>>
> >>> 2. for (a), we should first have consenus that we want the proposed
> solution and we should look for a complete, well designed and carefully
> tested
> >>> solution before the first commit will be done. This is to prevent the
> introduction of new problematic code.
> >>>
> >>> 3. for (b), I think every improvement of existing code/functionality
> helps and should be committed if there are no flaws in the design or
> >>> technical solution and it does not break existing funtionality. of
> course, it should be complete within the *scope* of the improvement.
> >>>
> >>> 4. if the solution for (b) does not cover other wishes or things which
> could be enhanced also, this would be no reason to not commit the
> >>> improvement. If people have further requirements, they can provide
> concepts and solutions/patches anytime to make things better.
> >>>
> >>> In this case, for me it is important if Suraj's commit
> >>>
> >>> a. breaks anything?
> >>>
> >>> b. is vetoed by other committers in view of code quality or design
> flaws?
> >>>
> >>> If none of these questions get a "yes", then I see no reason to revert.
> >>>
> >>> If you have additional requirements, you are encouraged to provide
> solutions or concepts for them.
> >>>
> >>> Thanks,
> >>>
> >>> Michael Brohl
> >>> ecomify GmbH
> >>> www.ecomify.de
> >>
> >>
> >
> >
>
>

Re: Website Translation in French need contributors

[Kev2600]

First time contributor. I'll translate.
Je sais pas si tu es très sévère avec les fautes de français.

Anyways. Give me something to do.

On 2018/04/26 16:47:05, Olivier Heintz  wrote:
> Hi all French contributors and committers and all others ;-)>
>
> I have create a JIRA to propose a French version of the Apache OFBiz
website. (https://issues.apache.org/jira/browse/OFBIZ-9800)>
>
> The idea is to propose a French version which is just a perfect
translation of the original content and doesn't introduce French specific
content, to>
> avoid difficulties for reviewing it for most of the committers and PMC
members.>
>
> A website translation is acceptable if and only if it is synchronized
very rapidly, each time there is a commit on standard website.>
> For the last 6 month I have done the sync and it's not a big job, BUT,
only one people is not enough for warrantee the it will be maintain in the
futur>
>
> This mail is a call for contributors : who is ready to be record as a
contributor on French translation of the Website ?>
> If there are enough people and the French website is publish,>
> a wiki page will be created with all the names and emails address to
contact you directly if a commit on the website is not manage for the
French>
> translation after 1 week.>
>
> Hoping a lot of of answer ;-)>
> Olivier>
>
>
>
>
>
>