UbuntuContributingDeveloper
|
Size: 1917
Comment:
|
Size: 4008
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
| ''Tell us a bit about yourself.'' | Systems Administrator and Network Engineer, right now I'm working at Canonical as Systems Integration Engineer. Been into Linux since kernel 1.2.13 back then starting with Slackware, then I moved to RedHat Linux and played a lot with Debian as well, have managed Ubuntu Servers in scale for the last 2 years before joining Canonical. Have been a contributor into FLOSS projects for quite a bit, had some active participation in the Linux LVM project and submitted patches to the mailman project to make it multi domain. My main body of work is into Systems Engineering, spawning my experience across six countries. |
| Line 11: | Line 17: |
| ''Tell us how and when you got involved, what you liked working on and what you could probably do better.'' | I started using Ubuntu Server daily almost three years ago, I was responsible of maintaining and expanding a platform with over 100 physical servers based in California, this required making new customized packages, tweaking configuration files automatically using Puppet and getting closely involved both with the PostgreSQL and the Ubuntu community. After this experience I joined Canonical into Corporate Services in order to help integrate new packages and solutions both cloud and bare metal based into Ubuntu to give it the compiting edge and getting a stronger foothold into the cloud. |
| Line 15: | Line 23: |
| I've contributed patches and extensions for cloud-init and squid-deb-proxy. In cloud-init I expanded the puppet module in order to not just append lines to the puppet config (with possible duplicates) but to parse the configuration properly and write a new puppet config file at the end of the process with all the new key values under their correct sections. In squid-deb-proxy I added debconf hooks to be able to disable/enable on demand the access to PPA repositories and also the ability to touch the cache ACLs for cloud enviroments. |
|
| Line 16: | Line 30: |
| ''Let us know what you worked on, with which development teams / developers you cooperated and how it worked out.'' ## As a per-package uploader, please give us some insight into the package maintenance and bug situation since you're working on it. |
My main area of work has been focused with the Server and Foundations team at Canonical, I'm one of the main developers for the Orchestra Project. I've been also heavily involved into integrating mcollective and its plugins into Ubuntu, this has involved day to day work with Puppet Labs, package sponsoring and bug crunching. |
| Line 20: | Line 35: |
| Try to avoid bad package behaviours as much as possible and learn more and more of the packaging policy while I keep contributing to Ubuntu. | |
| Line 23: | Line 39: |
| To keep being involved in projects to enhance the Ubuntu Server experience, introduce more Open Source projects into the Server platform and get heavily involved with the community and companies behind them. |
|
| Line 24: | Line 42: |
| ''Please describe what you like least in Ubuntu and what thoughts do you have about fixing it.'' | The package review process, completely necessary but right now extremely slow due to the workload of all the parties involved. |
I, Marc Cluet, apply for Ubuntu Contributing Developer.
Name |
Marc Cluet |
Launchpad Page |
|
Wiki Page |
Who I am
Systems Administrator and Network Engineer, right now I'm working at Canonical as Systems Integration Engineer.
Been into Linux since kernel 1.2.13 back then starting with Slackware, then I moved to RedHat Linux and played a lot with Debian as well, have managed Ubuntu Servers in scale for the last 2 years before joining Canonical.
Have been a contributor into FLOSS projects for quite a bit, had some active participation in the Linux LVM project and submitted patches to the mailman project to make it multi domain.
My main body of work is into Systems Engineering, spawning my experience across six countries.
My Ubuntu story
I started using Ubuntu Server daily almost three years ago, I was responsible of maintaining and expanding a platform with over 100 physical servers based in California, this required making new customized packages, tweaking configuration files automatically using Puppet and getting closely involved both with the PostgreSQL and the Ubuntu community.
After this experience I joined Canonical into Corporate Services in order to help integrate new packages and solutions both cloud and bare metal based into Ubuntu to give it the compiting edge and getting a stronger foothold into the cloud.
My involvement
Examples of my work / Things I'm proud of
I've contributed patches and extensions for cloud-init and squid-deb-proxy.
In cloud-init I expanded the puppet module in order to not just append lines to the puppet config (with possible duplicates) but to parse the configuration properly and write a new puppet config file at the end of the process with all the new key values under their correct sections.
In squid-deb-proxy I added debconf hooks to be able to disable/enable on demand the access to PPA repositories and also the ability to touch the cache ACLs for cloud enviroments.
Areas of work
My main area of work has been focused with the Server and Foundations team at Canonical, I'm one of the main developers for the Orchestra Project.
I've been also heavily involved into integrating mcollective and its plugins into Ubuntu, this has involved day to day work with Puppet Labs, package sponsoring and bug crunching.
Things I could do better
Try to avoid bad package behaviours as much as possible and learn more and more of the packaging policy while I keep contributing to Ubuntu.
Plans for the future
General
To keep being involved in projects to enhance the Ubuntu Server experience, introduce more Open Source projects into the Server platform and get heavily involved with the community and companies behind them.
What I like least in Ubuntu
The package review process, completely necessary but right now extremely slow due to the workload of all the parties involved.
Comments
If you'd like to comment, but are not the applicant or a sponsor, do it here. Don't forget to sign with @SIG@.
Endorsements
As a sponsor, just copy the template below, fill it out and add it to this section.
TEMPLATE
== <SPONSORS NAME> == === General feedback === ## Please fill us in on your shared experience. (How many packages did you sponsor? How would you judge the quality? How would you describe the improvements? Do you trust the applicant?) === Specific Experiences of working together === ''Please add good examples of your work together, but also cases that could have handled better.'' === Areas of Improvement ===
MarcCluet/UbuntuContributingDeveloper (last edited 2011-06-20 10:50:58 by 78)