The health of the project from my perspective is not necessarily in how many patches / pull requests are approved. In fact, there is nothing easier than simply going through all patches and applying them one by one. For me quality wins over quantity and 10 clean lines of code are better than 100 hasty ones. There is in fact a term for hasty and low quality code. It's called technical debt.
One place where cleanup is needed in fact are the tickets themselves. Perhaps in the community days we can focus on that part. Some of tickets are better off closed instead of keeping them as dead weight. On Monday, May 11, 2020 14:23 +03, Pierre Smits <[email protected]> wrote: While I agree that improving the content in the wiki is important and should be a theme of upcoming OFBiz Community Days, collaborating to get as much patches (currently more than 300 tickets listed, see [1]) as possible reviewed and/or implemented into the code base is equally important. Not only does it shorten the list of open tickets (currently more than 1500), but it also sends a strong signal to (adopters) and contributors: that the community works as fast as possible to get the (valuable) contributions of members implemented. [1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20OFBIZ%20AND%20status%20%3D%20%22Patch%20Available%22%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC%2C%20updated%20DESC Met vriendelijke groet, Pierre Smits *Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> since 2008 (without privileges) *Apache Trafodion <https://trafodion.apache.org>, Vice President* *Apache Directory <https://directory.apache.org>, PMC Member* Apache Incubator <https://incubator.apache.org>, committer Apache Steve <https://steve.apache.org>, committer On Mon, May 11, 2020 at 11:20 AM Jacques Le Roux < [email protected]> wrote: > Thanks Devanshu, > > After our move to Git we have finally cleaned our site from information > referring to Svn, and that's good. > > But there is still much such info in the wiki and it can be confusing. > > I suggest that we concentrate much of our efforts during this Community > Day to clean the wiki. > > We can adapt to Git and keep in wiki when needed, or move in Attic under a > specific "Subversion" page when really too deprecated. > > I know, for most of us, it's not as easy as coding with Git and GitHub. > But Confluence now also easily allows to share tasks and merge when needed. > > We should not hesitate to prune much, nothing worse than obsolete and > confusing documentation > > I hope everyone will help, it's really long due :) > > Thanks > > Jacques > > > Le 11/05/2020 à 06:40, Devanshu Vyas a écrit : > > Hello all, > > > > We are back with OFBiz Community Days, hope you are excited too! :-) > > The community days are organized once per quarter so a total of four (4) > > events throughout the year. > > > > We are having a sequence of 5 days that form the Community Days. This > > extends the time frame and gives people more flexibility to contribute. > > So, this month our Community Days will be from *22nd – 26th May 2020*. > > > > If you are new to the concept of Community Days then please take a look > at > > the following wiki pages: > > https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Community+Days > > > https://cwiki.apache.org/confluence/display/OFBIZ/OFBiz+Community+Days+Dates > > > > This is such an event where anyone can participate (and we would like to > > encourage as many people as possible to do so) > > > > If there is an OFBiz task or particular area that you would like to work > on > > then please see if you can set aside some time over the next few days to > do > > it. (Even an hour will help!) > > > > Remember that you do not have to work on it alone, our Community Days are > > also a chance to collaborate with others in the community. > > > > Our Community Days are not only coding related, but we would also like to > > do some tidy up of our wiki and our project documentation. > > > > *Testing, Review and Committing Patches* > > Testing and applying patches is always an important area. Many > contributors > > from the community have provided patches for bugs and improvements but > > before committing them we need to test to them. > > > > Patches can become out of date very quickly meaning that if they are not > > tested early enough then they can miss out on being included. We have a > > large number of patches available so this could be a good opportunity for > > test, review and commit. > > > > *Documentation* > > We know that our current documentation could be a whole lot better so any > > contribution that helps us improve it is welcome. > > > > *Jira Sprint* > > I will create a Jira sprint "OFBiz Community Day (May 2020)" so please > add > > any Jira tasks when you are working on it. > > This Jira Sprint helps us track and report on the work done during the > > Community Days so please try to make sure your work is included. > > To set the sprint on an existing issue, simply click on the "Edit" option > > on the issue and select the sprint field. > > > > We should add the Sprint in all the cases: > > 1.) If we create a ticket we should add it. > > 2.) If we start working on an existing ticket (adding patch or closing it > > after a commit) we should add sprint if it is missing. > > > > Basically adding Sprint will make sure the contribution will be counted > in > > OFBiz community days event, which is from 22nd – 26th May. > > At the end of May's OFBiz Community day i.e. after 26th May, this will > help > > us in reporting. > > > > *OFBiz Slack Channel* > > If you haven't already taken a look, our OFBiz Slack channel is available > > all the time but can be especially useful when collaborating during our > > Community Days event. Please join our room using the link below: > > https://s.apache.org/ofbiz-slack-channel > > > > To chat with users and developers of Apache OFBiz. Please create a Slack > > account using this invite link <https://s.apache.org/slack-invite> and > join > > the *#ofbiz channel*. <https://s.apache.org/ofbiz-slack-channel> Please > do > > *not* ask OFBiz questions/discussion in the #general channel. > > > > Let's all collaborate to improve OFBiz, have fun and enjoy working > together. > > > > Thanks & Regards, > > Devanshu Vyas. > >
