From Fedora Project Wiki

No edit summary
No edit summary
Line 29: Line 29:
Nowadays I also sparingly contribute to the linux kernel - where I got some patches accepted. The area of the kernel I'm interested into right now is the vfs and the overlay union filesystem (this is probably related to the fact that Docker itself uses overlay as one of its storage driver for containers and images).
Nowadays I also sparingly contribute to the linux kernel - where I got some patches accepted. The area of the kernel I'm interested into right now is the vfs and the overlay union filesystem (this is probably related to the fact that Docker itself uses overlay as one of its storage driver for containers and images).


I'm the owner and maintainer of `skopeo` (https://github.com/projectatomic/skopeo) which is a tool (and libraries) which makes your life easier when interacting with Docker registries - even if my idea is to make it more Docker-agnostic!
I'm the owner and maintainer of '''skopeo''' (https://github.com/projectatomic/skopeo) which is a tool which makes your life easier when interacting with Docker registries - even if my idea is to make it more Docker-agnostic!
I also maintain containers/image (https://github.com/containers/image) which are the libraries used by '''skopeo'''.


I love speaking at conferences - which was something I was always afraid of in the past to be honest!
I love speaking at conferences - which was something I was always afraid of in the past to be honest!

Revision as of 19:24, 13 July 2016

Antonio Murdaca
Antonio Murdaca
Personal Information
Birthday: {{{birthday}}}
Home: Rome, Italy
Fedora-specific Information
FAS-Name: runcom
Fedora-Mail: runcom@fedoraproject.org
Miscellaneous Information
Private Mail: {{{pmail}}}
GPG-Key: 0DE936B9
IRC: runcom on Libera.chat in
#fedora-devel
Badges (59)
Involvement Bona Fide If you build it... (Koji Success I) In Search of the Bull (Tester I) Partners in Crime Paranoid Panda Crypto Badger Mugshot You can call me "Patches" (SCM I) Baby Badger Junior Badger (Badger I) Is this thing on? (Updates-Testing I) Old Yeller If you build it... (Koji Success II) Let Me Introduce Myself What goes up... (Koji Failure I) If you build it... (Koji Success III) What goes around comes around (Karma I) What goes up... (Koji Failure II) Take this and call me in the morning You can call me "Patches" (SCM II) Discovery of the Footprints (Tester II) You can call me "Patches" (SCM III) What goes around comes around (Karma II) Like a Rock (Updates-Stable I) Is this thing on? (Updates-Testing II) Associate Badger (Badger 1.5) White Hat Binary Star What goes up... (Koji Failure III) Override, you say? Junior Editor Like a Rock (Updates-Stable II) Ambassador Crypto Panda Perceiving the Bull (Tester III) What goes around comes around (Karma III) If you build it... (Koji Success IV) What goes around comes around (Karma IV) LinuxCon Europe 2016 Attendee Is this thing on? (Updates-Testing III) Top 500 Egg Catching the Bull (Tester IV) Macaron (Cookie I) DevConf 2017 Speaker FOSDEM 2017 Attendee Speak Up! It still works! nest-attendee-2020 Senior Badger (Badger II) Tadpole with Legs Embryo Tadpole Fedora 37 Change Accepted Froglet Fedora 38 Change Accepted Associate Editor IoT Working Group Member
 


About Me

TL;DR;

  • Geek
  • Fedora Ambassador
  • linux maniac
  • Docker lover & upstream maintainer
  • Studied computer science and computer engineering
  • Joined Red Hat in Sept 2015 as a Sofware engineer for the Containers and Container Security teams

Full story;

Hello, my name is Antonio Murdaca. Some people may know me as "runcom" instead which is the nickname I use on github and IRC. I'm a Software Engineer at Red Hat Inc. since Sept 2015 where I currently work on containers technologies (from Docker, to rkt to many others). I'm also working on containers security stuff daily. My open source career (as I like to name it) started back in March 2015 when I started contributing to the Docker project. I had (and have) a strong motivation in contributing to the open source (I'll defer this to a blog post I wrote here https://blog.docker.com/2015/10/how-i-started-contributing-to-the-docker-project/ which I think it will be helpful for everyone hungry to get started at contributing). Previously I also worked as a Web Developer but my main area of interest was (and is) clearly system programming.

I started contributing to Fedora as part of my daily job. There I started packaging Docker due to I was familiar with its build process. After getting my hands dirty with Docker I started packaging other software - mainly containers-related but many of the packages I maintain are golang libraries.

Nowadays I also sparingly contribute to the linux kernel - where I got some patches accepted. The area of the kernel I'm interested into right now is the vfs and the overlay union filesystem (this is probably related to the fact that Docker itself uses overlay as one of its storage driver for containers and images).

I'm the owner and maintainer of skopeo (https://github.com/projectatomic/skopeo) which is a tool which makes your life easier when interacting with Docker registries - even if my idea is to make it more Docker-agnostic! I also maintain containers/image (https://github.com/containers/image) which are the libraries used by skopeo.

I love speaking at conferences - which was something I was always afraid of in the past to be honest! So far, my fear of publicly speaking has been overcome at:

  • DevConfCZ 2016 - lighting talk - Docker authorization plugins
  • CloudConf IT 2016 - Docker advanced features
  • flock2fedora 2016 - yeah, I'll update this one but I'll be talking about "Next generation containers"

I'm always interested in hearing from people how they started their open source career or why they still didn't! If you want just ping me on IRC or via email and I'd be happy to discuss!