You're quite the impressive guy, Leonardo! I was a pretty aggressive 15 year-old as well, so I really respect your drive.
First, let me applaud your bash/linux focus. I was fortunate enough to work
with two guys early in my career who would routinely use bash/linux to generate
and modify code. Particularly for test cases where you have to test
combinations. Say you wanted to test how 5 rest endpoints
(Users,Groups,Items,Producst,Orders) behaved with each of the different common
HTTP methods (GET,POST,PUT,PATCH,DELETE,OPTIONS,HEAD). They'd whip up a bash
loop like this:
for n in
testHttp{GET,POST,PUT,PATCH,DELETE,OPTIONS,HEAD}to{Users,Groups,Items,Producst,Orders}Endpoint;
do
echo $n
done
Except it wouldn't just print the test case name, it'd actually invoke the rest
endpoint, record the response and generate the full test method asserting that
response. Most developer will write all their test cases by hand. They would
write one test by hand, then go to the command line and use a bash script to
duplicate 200+ test cases just like it. Mind-blowing stuff. I followed in
their footsteps and can definitely say it's one of the biggest secrets to my
coding ability.
Anyway, I have a couple ideas of things we need that you might be good
challenges for you:
- Automating our website publishing. We need a Jenkins job that will checkout
our website source from git, build it, then commit all the generated html to a
different git repo. The difficult part about helping with that is you don't
have access to our Jenkins server or commit access to that second git repo.
But perhaps you could setup a test Jenkins install on your machine and create a
jenkinsfile that builds the website source and commits to a test git
repository. You could submit a PR for the Jenkinsfile and one of the
committers can set it up on the Apache Jenkins.
- Building RPMs or other non-docker image types. We already have a
contributor, Rod, who maintains Docker images, but we can always use more ways
to distribute TomEE. We've never really had good support for the classic
formats like rpm or deb. If you're interested in contributing anything in that
regard or for newer image types, that'd be a very welcome addition.
If any of that sounds fun, let me know and I'll try to write some details. If
none of them sound fun, there are many other areas where we need help, so
that's ok!
-David
> On Apr 20, 2021, at 4:05 PM, Leonardo Alonso <[email protected]>
> wrote:
>
> Hello guys, my name is Leonardo Alonso and I'm Brazilian!
>
> I am 15 years old, I study programming and operating systems for about 3
> years.
>
> I am currently in my first professional experience, in a local company, in
> the Cloud Computing / Middleware team
>
> I would like to know how I can contribute to TomEE, as I am very
> interested. (I think it could help more in the part of images for
> containers, and all the part of tunning, help in the correction of eventual
> bugs, TomEE tests in Linux, however if you need for other activities, I'm
> available to learn)
>
> Some of my knowledge are:
>
> * Solid knowledge in Linux / Unix
> * Java application servers
> * Development in C, Shell Script (Bash) and Java
> * Cloud computing and containers in general
> * CI / CD and code versioning
>
> **** Sorry for errors in English, I'm still improving ****
smime.p7s
Description: S/MIME cryptographic signature
