Hi Sharan, It's really good to have you on board in this project, thank you for the positive energy :) I compile below my ideas based on your feedback:
First of all, the ideas I listed in this thread are just ideas that are subject to change. The important thing is moving forward and getting things done. So I ask everyone not to worry too much about the choice of technology or tool to use here or there. I'm sure whatever we decide to go with eventually is okay. In the end, these are tools, what matters is people and process. Second I noticed a problem that maybe you Sharan can help with. I observed multiple times from some community members that they actually _want_ to help but are overwhelmed with the complexity of this process and are not sure how to help. The hesitation for others to engage is because collaboration over the Wiki Page, Mailing List and JIRA is definitely not enough. Why? - Slow (feedback on progress, hints, guidance) - Not very friendly for beginners - Intimidating: some might be reluctant to ask basic questions on architecture or programming or so. - Overwhelming: We are discussing very technical matters and some people would freak out at the complexity. They need to understand that there are different tasks at different levels of complexity and that there are senior out there who are willing to help. The tools we are using for collaboration makes it difficult to convey this fact. - Impersonal and we cannot get people engaged. Things like conversations, brainstorming, assigning tasks, discussing, coaching, teaching and encouraging are difficult to do. These personal elements are crucial for knowledge transfer and support. In short, I think there are members in the society who are willing to help, but not sure how. It's really unfortunate not to engage these individuals because of communication barriers. My 2 cents! Taher Alkhateeb -----Original Message----- From: Sharan-F [mailto:sharan.f...@gmail.com] Sent: 06 June 2016 10:57 To: dev@ofbiz.apache.org Subject: Re: My experience with refactoring the framework Hi Taher Thanks for sharing your experience as I think it contains some real insights and also re-confirms an important task – we need to tidy up our code. And the one crucial message I hear loud and clear in your email is that we need everyone to help out too. (BTW I've seen the amount of work that you have done on the start.java which is looking very elegant now :-) Your list re-factoring ideas touch on a lot of areas that I'm sure will generate discussion and I hope that we don't get too caught up in the discussion that we don't act. We need to stay active by continually doing something that improves OFBiz. I agree that we should look at holding off adding new features or improvements now and just clean. I've seen the huge amount of activity that is happening at the moment so let's see if we can maybe focus some of that energy into tidying up our code and getting rid of our ' historic technical debt' (as mentioned by Jacques). It sounds like you have already a list of tasks to replenish our Current Re-Factor To Do list so let's do that and get the message out to the community about what they can do to help. I noticed that if we have a list of tasks that people can pick up easily, then they will. Going forward we may need to have a bit more co-ordination and also work together in small groups focussing on particular areas so things dont get broken, especially once the applications start being affected. I'm happy to help so just let me know how I can. Thanks Sharan -- View this message in context: http://ofbiz.135035.n4.nabble.com/My-experience-with-refactoring-the-framework-tp4682539p4682591.html Sent from the OFBiz - Dev mailing list archive at Nabble.com.
