When they're lazy consensus which demands a response and also overwhelming us, well then things get difficult and I don't feel bad about about raising it as an issue. I'm grateful for the commitment to the project but if I can't keep up then I don't know how else to respond. What else do you suggest?
Regards Scott On 25/09/2016 22:10, "Pierre Smits" <[email protected]> wrote: > I won't ask such a thing of any contributor. Maybe you (or others) feel the > need to dictate how and when other volunteers spend their energy on the > itches they want/need to scratch. > > Best regards, > > Pierre Smits > > ORRTIZ.COM <http://www.orrtiz.com> > OFBiz based solutions & services > > OFBiz Extensions Marketplace > http://oem.ofbizci.net/oci-2/ > > On Sun, Sep 25, 2016 at 11:07 AM, Scott Gray <[email protected] > > > wrote: > > > Is it a complicated thing to ask our most prolific contributor to slow > down > > so that we can all be effectively involved? Personally I don't think it > is > > complicated. > > > > On 25/09/2016 22:03, "Pierre Smits" <[email protected]> wrote: > > > > > Everyone participating can be blamed for complaints, or needlessly > > > prolonging discussions. Some want to discuss everything, Some blame the > > > other contributor. > > > > > > Does the blame game help the project? Instead of pointing out the > 'flaw' > > in > > > other, it is better to apply some introspection first wit respect to > one > > > own contributions and that helps the project forward. > > > > > > Best regards, > > > > > > Pierre Smits > > > > > > ORRTIZ.COM <http://www.orrtiz.com> > > > OFBiz based solutions & services > > > > > > OFBiz Extensions Marketplace > > > http://oem.ofbizci.net/oci-2/ > > > > > > On Sun, Sep 25, 2016 at 10:53 AM, Taher Alkhateeb < > > > [email protected]> wrote: > > > > > > > I find it exhausting that I cannot focus on coding in OFBiz because > of > > > the > > > > "machine-gun" like activities, many of which are triggered by > Jacques. > > I > > > am > > > > spending more and more time trying to limit code getting into the > > > framework > > > > than actually doing critical things like refactoring and improving > the > > > code > > > > base. > > > > > > > > Quality wins over quantity hands-down. We need to focus on quality, > we > > > need > > > > to focus our limited resources and efforts on fewer but more critical > > > > issues. It is really tiring to engage in these threads that go on > > > > indefinitely many of which I find not that important anyway. For > > example: > > > > > > > > - There were some long, long discussions on whether or not to add > > Gradle > > > > shortcut tasks. These tasks are minor and not that important in the > > first > > > > place. Why bloat the code early, this can always be visited once we > > > finish > > > > more critical work. > > > > - We had discussions on "Style guides" when we have some very bad > code > > > that > > > > needs to be cleaned first. Does it really matter if I say if(x==y) or > > if > > > > (x==y) when the bigger issues are unresolved like hidden mutable > shared > > > > state, no interfaces, poor design, poor documentation, faulty logic, > > and > > > > spaghetti code. Before focusing on style and spending a lot of energy > > > > there, let's look at the much much bigger problem of poor quality and > > > badly > > > > designed code. (REF http://markmail.org/message/cpqfhxn6fnu5zuu7) > > > > - There was another long discussion for example on semi colons in > > Groovy > > > > scripts. Again, is that the most important thing right now? I can see > > > much > > > > bigger problems in our groovy scripts than that. (REF > > > > http://markmail.org/message/rabzquyotw3gf3vx) > > > > - We had a long discussion on whether to make binary releases when we > > > > didn't even release! (REF http://markmail.org/message/ > 7up63poazemvgha2 > > ) > > > > - The themes discussion is not that important, it is more important > to > > > > focus on the underlying technology. We have major problems in the way > > > > themes are designed, web assets are fragmented between framework, > apps > > > and > > > > themes, there is a lot of duplication, the widget system is not pure > > and > > > > mixed with a lot of templates. These problems are more pressing and > if > > > > resolved, makes the themes a smaller problem. (REF > > > > https://issues.apache.org/jira/browse/OFBIZ-8293 > > > > > > > > So I think the philosophy (Less is More) is very relevant in here. We > > > need > > > > less long exhausting threads and more focus on critical technical > areas > > > to > > > > help improve the fundamentals of our project. > > > > > > > > On Sun, Sep 25, 2016 at 11:35 AM, Paul Piper <[email protected]> > wrote: > > > > > > > > > Aren't these meant to be private discussions between you guys > > (perhaps > > > > > within > > > > > the PMC ml)? > > > > > > > > > > I don't understand how Jacques' activity level has anything to do > > with > > > > the > > > > > topic discussed here, or on this thread > > > > > (http://ofbiz.135035.n4.nabble.com/Wiki-page-for-the- > > > > > monthly-Jira-issues-list-creation-in-the-blog- > > tp4694738p4695235.html). > > > > > > > > > > Oh and -1 on flatgrey as it is one of the few themes that aren't > > broken > > > > > within stock ofbiz. > > > > > > > > > > > > > > > > > > > > -- > > > > > View this message in context: http://ofbiz.135035.n4.nabble. > > > > > com/VOTE-Put-the-Flatgrey-theme-in-Attic-tp4695129p4695240.html > > > > > Sent from the OFBiz - Dev mailing list archive at Nabble.com. > > > > > > > > > > > > > > >
