Hi Andy, We are always happy for people to make great contributions to the project, > no matter how big or small. 'Together' we achieve a lot! >
+1 Thanks, but item 2) was dropped for me, due my ultra slow 'internet connection' i can't follow updates to get right builds. <https://bval.apache.org/>If there is 'anything' you struggled with because > of lack of documentation or help then please let me know. > I really want to get the documentation as intuitive as possible, and help > get people started on the right track. > I looked apache bval documentation about some aspects to contribute with 'apache projects' http://bval.apache.org/coding-standards.html http://bval.apache.org/building.html http://bval.apache.org/release-setup.html and so on.. Things happen, i need to get organized to get back to TomEE. ------------------------------------------- http://eprogramming.github.io On Fri, May 2, 2014 at 8:22 AM, Andy Gumbrecht <[email protected]>wrote: > Hi great Helio that's just brilliant! > > We are always happy for people to make great contributions to the project, > no matter how big or small. 'Together' we achieve a lot! > > If there is 'anything' you struggled with because of lack of documentation > or help then please let me know. > I really want to get the documentation as intuitive as possible, and help > get people started on the right track. > > Andy. > > > On 04/04/2014 11:58, helio frota wrote: > >> Hi great all devs, >> >> Following the path: >> http://tomee.apache.org/dev/contribution-tips.html >> >> 1) Final variables & fields are preferred where possible, but a lot of the >> >>> code is old. Feel free to add them and hand the code back. >>> *2)* If you have any skills with code coverage tools, then you'll >>> >>> probably find way too much to do! Tests are always welcome. >>> 3) There are over a 1,000 TODO comments in the code. Maybe some should be >>> deleted. Maybe some could be completed. They probably all should have a >>> JIRA id on them. >>> *4)* Pick a random class, see if you can figure out what it is doing and >>> >>> javadoc it. >>> 5) Add @Override where applicable >>> 6) Intellij has an 'Inspect Code' feature. Yikes does it produce a lot of >>> output. >>> 7) No doubt there is some exception handling that can be greatly >>> improved. >>> >>> >> Now i'm doing *2)* >> >> But going to do *4) *soon >> >> >> If has others things to do, please update contribution-tips page. >> >> I have personal real project (beginning) to use always the 'trunk' to >> force >> more feedback for TomEE >> https://github.com/EsmerilProgramming/fq >> >> cheers, >> helio >> >> ------------------------------------------- >> http://eprogramming.github.io >> >> > -- > Andy Gumbrecht > > http://www.tomitribe.com > [email protected] > https://twitter.com/AndyGeeDe > > TomEE treibt Tomitribe! | http://tomee.apache.org > >
