+ 1
On Mon, Mar 31, 2014 at 9:44 AM, Matt Bruzek <[email protected]>wrote: > Hello Charmers, > > > I have been working for Canonical on the Juju Ecosystem team for 3 > months, and it is time to step up and apply for charmer status. > > > I have had two tours on the Charm Review Queue and performed reviews of > many charms. Most of my time has been spent doing the Charm Audit, writing > tests to verify that charms are doing what they claim to do. This often > involves diving in to learn the technology the charm provides, and figuring > out how to test that technology in an automated way. > > > Here are my credentials for your consideration: > > > *Authored charms*: > > > http://manage.jujucharms.com/charms/precise/openmrs > > OpenMRS is a open source electronic medical records platform written in > Java. > > > I have a charm on the way that installs/configures Apache Tomcat. This > charm will have many new features and will provide Juju a robust Java > Servlet and JSP framework. https://bugs.launchpad.net/charms/+bug/1295710 > > > I also engaged the Apache PMC team to gain permission to use the Apache > Tomcat icon in Juju! So the Tomcat charm will have the official Apache > Tomcat icon where the existing charms used the default icon. Once the > Tomcat charm passes a review I plan on replacing/deprecating the existing > tomcat6 and tomcat7 charms. > > > *Juju Presentations*: > > > Here is a UDS 2014 Charm School where I gave a deep dive on developing > charms: http://www.youtube.com/watch?v=ByHDXFcz9Nk&feature=share&t=10m15s > > > I have given a Juju presentation to the Rochester Minnesota Linux User > Group. You can view the presentation I created here: > http://prezi.com/7xgiezaajjek/juju/ > > > *Juju Documentation*: > > > Having worked on several software products, I hold the firm belief that > software need complete documentation to be a great product. I have > contributed to the Juju documentation where ever I see an opportunity. My > contributions can be reviewed here: > > > https://github.com/juju/docs/issues/35 > > https://github.com/juju/docs/pull/33 > > https://github.com/juju/docs/pull/23 > > And before the docs were on github: > > > https://code.launchpad.net/~mbruzek/juju-core/fixed-404-in-authors-charm-writing > > https://code.launchpad.net/~mbruzek/juju-core/Fixed-references-to-contents > > > *Bugs*: > > > Creating bug reports is an important component of the software > development process. As a developer myself I appreciate a complete bug > report, so the golden rule applies when I find things that can be improved. > I try to create bug reports with detailed descriptions and include steps on > how to recreate the issue. Here are a few examples: > > > #1299179 mysql hook failed: > "mongos-relation-changed"<https://bugs.launchpad.net/charms/+source/mongodb/+bug/1299179> > > #1279879 Juju error on HP cloud with Maximum number of attempts (3) > reached sending request<https://bugs.launchpad.net/juju-core/+bug/1279879> > > #1293878 Amulet should work with local charms that are not in version > control <https://bugs.launchpad.net/amulet/+bug/1293878> > > #1294690 Amulet should provide a way to detect the Juju > environment.<https://bugs.launchpad.net/amulet/+bug/1294690> > > #1296780 KeyError for units that were added by > add_unit<https://bugs.launchpad.net/amulet/+bug/1296780> > > #1284309 The rsync fails in error when the -o option is > used<https://bugs.launchpad.net/charm-tools/+bug/1284309> > > > I have reported 17 bugs that are currently open, you can see them all > here: https://bugs.launchpad.net/~mbruzek/+reportedbugs > > I am involved with 23 bugs at the moment, if you want to view them all go > to: https://bugs.launchpad.net/~mbruzek/+bugs > > > *Code*: > > > Most of my time has been spent writing Amulet tests for the Charm Audit. > Here are some branches that illustrate my understanding of different charms > and the amulet testing framework. > > > > lp:~mbruzek/charms/precise/rabbitmq-server/tests<https://code.launchpad.net/%7Embruzek/charms/precise/rabbitmq-server/tests> > > lp:~mbruzek/charms/precise/lamp/trunk<https://code.launchpad.net/%7Embruzek/charms/precise/lamp/trunk> > > lp:~mbruzek/charms/precise/memcached/trunk<https://code.launchpad.net/%7Embruzek/charms/precise/memcached/trunk> > > lp:~mbruzek/charms/precise/haproxy/trunk<https://code.launchpad.net/%7Embruzek/charms/precise/haproxy/trunk> > > > *Reviews*: > > > One of the most important responsibilities of a charmer is to welcome > the contributor to the community and help them create quality charms that > follow charm store policy. Sometimes that means giving the contributor > things to improve and fix before they are accepted in the charm store. I > have tried to be welcoming and give constructive suggestions in the reviews > that are listed below. > > > #1199052 New charm: mailman<https://bugs.launchpad.net/charms/+bug/1199052> > > #1272083 HPCC Charm initial check-in for > review<https://bugs.launchpad.net/charms/+bug/1272083> > > #1273790 Charm Needed: wildfly<https://bugs.launchpad.net/charms/+bug/1273790> > > > Please review my work thus far and consider me for the role of Charmer. > I am dedicated to ensuring the Juju community has the highest quality > charms. Much like the charming process there are opportunities where I > could be more effective. Let me know where I can improve and you have my > word that I will continue to progress to be the best representative of the > Juju community as I can be. > > > Sincerely, > > > Matt Bruzek <[email protected]> > > -- > Juju mailing list > [email protected] > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > >
-- Juju mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
