Just a reminder to everyone that there is an ongoing Skype conversation
around the framework refactoring sub-project.
If you are not part of the conversation, please ask to join.
It is not very active so you will not get a lot of notes to read
However, it provides a place where you can quickly get input from the
rest of the team working on the sub-project.
It is a good place to look for feedback or advice before you start to
work on a task or have to make a design choice that may have affects on
other parts of the project.
There is also a much larger group on Skype that is more active that
involves many of those working on OFBiz in general.
You can join these groups even if you are not currently actively
contributing to the project.
That being said, the Skype conversations are not designed to replace the
wiki of the ML so don't forget to confirm decisions or summarize
important discussions in the appropriate official record.
Ron
PS:
Taher's recommended readings are worth a quick read.
Well written.
Lots of good ideas and important reminders about coding practices.
-
On 08/04/2016 8:18 AM, Taher Alkhateeb wrote:
Hi Sharan and all,
To all contributors to the project, I highly recommend reading:
- Refactoring: Martin Fowler
- Clean Code: Robert Martin (AKA uncle Bob)
- SOLID principles of OOP
- Test Driven Development (TDD)
I also encourage fellow committers to think of design changes and areas
they dislike in the framework to add to the list in the wiki page. I'm sure
with the combined expertise of everyone we can speed up this project a lot.
Regards,
Taher Alkhateeb
On Friday, 8 April 2016, Pranay Pandey <[email protected]>
wrote:
+1 will be extra careful going forward.
Best regards,
Pranay Pandey
HotWax Systems
http://www.hotwaxsystems.com/
On Fri, Apr 8, 2016 at 12:36 PM, Sharan-F <[email protected]
<javascript:;>> wrote:
Hi Everyone
It's great to see the progress happening on the framework and code
re-factoring. Tasks from our to do list are being picked up and worked
on,
so thank you to everyone involved in this.
As this is a code clean-up, I'd really like to emphasize that we need to
be
extra careful because we are changing the way we currently code. This
means
that there is some extra responsibility for the committers in the review
process to ensure that the quality of the code going in is an improvement
to
the existing code (I.e we dont want to commit anything that keeps our
code
untidy or makes it even worse)
If we can include stronger quality checks while the re-factoring is going
on, we can be sure that we are definitely making and delivering code
improvements.
What do people think?
Thanks
Sharan
--
View this message in context:
http://ofbiz.135035.n4.nabble.com/Framework-Code-Re-Factoring-Maintaining-Quality-tp4679123.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
