welcome to Fedora infrastructure. You can start by looking at https://fedoraproject.org/wiki/Infrastructure/GettingStarted and I recommend you to join our weekly meeting, which is each
Thursday at 16:00 UTC in #fedora-meeting-1 channel on Freenode. If you have any questions feel free to ask. :-)
Michal
On 11. 01. 21 23:50, Leonardo Alonso
wrote:
Hello guys, How are you?
First of all, it is a pleasure to be able to participate in the Fedora community, my name is Leonardo Alonso (IRC : LeonardoAlonsooB), I am 15 years old and I am Brazilian
I am in my first professional opportunity in 1 year, but I study Linux / Development in 3 years (with most studies done with Red Hat and Fedora)
Whatever you need if I know how to solve (if I don't know how to learn) I am 100% available to help.
Some of my knowledge:
Programming languages: Shell Script, Python and Java Back-end
Linux services: SFTP, FTP, Samba, NFS, Apache HTTP, NGINX, TomCat, LDAP, Squid, Bind, cPanel, Syslog / Rsyslog, SSH
In addition to the part of containers, Cloud Computing, automation and IAC.
I am very interested in participating in the Fedora Infrastructure Apprentice, in what you need just call.
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
