Mozilla

Mozilla Hacks Weekly, May 24th 2012

It’s Thursday and time for us in Mozilla’s Developer Engagement Team to share some great links!

At the end of this blog post, you also have all the Developer Engagement team members and what they work on. If you are interested in discussing more, contributing or taking part of our work, don’t hesitate to contact us or follow us on Twitter!

Weekly links

If there is anything you think we should read or know about, don’t hesitate to post a comment, contact us on Twitter or through any other means.
The picks this week are:

The Developer Engagement team

Mozilla’s Developer Engagement team work with writing articles, documentation – such as MDN (Mozilla Developer Network) – public speaking and generally helping and informing about open technologies and Mozilla products. If you are interested in following our work, here are the team members:

Christian Heilmann

Christian is Mozilla’s Principal Evangelist and is working with HTML5, Open Web, BrowserID and Developer Tools in Firefox. He is also maintaining the @mozhacks account together with Robert Nyman.

Blog: http://christianheilmann.com/
Twitter: @codepo8

Eric “Sheppy” Shepherd

Eric is the Developer Documentation Lead for the MDN documentation and everything surrounding it.

Blog: http://www.bitstampede.com/
Twitter: @sheppy

Havi Hoffman

Havi works with Mozilla Labs and WebFWD, and maintains the @mozlabs account.

Twitter: @freshelectrons.

Janet Swisher

Janet is working on MDN documentation and is organizing doc sprints to ensure we have premium quality on MDN.

Blog: http://www.janetswisher.com/
Twitter: @jmswisher.

Jean-Yves Perrier

Jean-Yves is another one of our technical writers working on MDN documentation.

Twitter: @teoli2003.

Jeff Griffiths

Jeff is working with the Add-ons SDK (Jetpack).

Blog: http://canuckistani.ca/
Twitter: @canuckistani

Joe Stagner

Joe is working with Web Apps Developer Ecosystem & Partner Engagement, HTML5 and the Open Web.

Blog: http://www.misfitgeek.com/
Twitter: @MisfitGeek

John Karahalis

John is working on Dev Derby.

Twitter: @openjck

Rob Hawkes

Rob is working on HTML5 games and the Open Web.

Blog: http://rawkes.com/
Twitter: @robhawkes

Robert Nyman

Robert is working with HTML5, Open Web, Firefox, WebAPI and maintains the @mozhacks account.

Blog: http://robertnyman.com
Twitter: @robertnyman

Shezmeen Prasad

Shezmeen is working on everything regarding events, organization and connecting conferences with Mozilla speakers.

Stormy Peters

Stormy is the Team Lead for the Developer Engagement team. managing it and evaluating our objectives.

Blog: http://stormyscorner.com/
Twitter: @storming

Tristan Nitot

Tristan is our Mission Evangelist and is focusing on the bigger picture of Mozilla.

Blog: http://standblog.org/blog/en
Twitter: @nitot

Will Bamberg

A picture of Will Bamberg Will is working on documentation for the Add-ons SDK (Jetpack).

6 comments

Comments are now closed.

  1. Pseudonymous Coward wrote on May 24th, 2012 at 07:40:

    Robert,

    I love Mozilla Hacks, but putting the bios of the development team over and over again and again on Planet Mozilla for every single article from Mozilla Hacks is just unreadable. I understand that people are worth acknowledging, but it seems superfluous to acknowledge the whole team for every article.

    Thanks,
    PC

    1. Robert Nyman wrote on May 24th, 2012 at 14:27:

      Thanks for your input.

      If you read regularly, I understand that that can be a lot of information, and that’s why we put it last in the blog post. However, we also need to take into account that people reach this blog post coming from Twitter, a search engine or any other means, and in most cases they don’t have any background information about Mozilla Hacks Weekly or the Developer Engagement team (the team info is only included in the Mozilla Hacks Weekly blog posts).

      So, having it as one big footer to the blog post is, for now, the compromise to tend to all kinds of targets. Any suggestions of other ways of achieving that is welcome! Thanks!

      1. David Mulder wrote on May 25th, 2012 at 04:25:

        You could add some javascript to read out “document.referrer” and if it’s from hacks.mozilla or planet mozilla then hide the div. (Not that I care much :P ), but it might be a simple solution.

        1. Robert Nyman wrote on May 27th, 2012 at 02:23:

          Well… Then you have some JavaScript dependency, and it’s not desirable in general to have JavaScript as part of a post, I think. Thanks for the suggestion, though!

          1. David Mulder wrote on May 29th, 2012 at 07:20:

            The beatiful thing about it is that you actually do not have a javascript dependency, as without javascript the div will simply show. And it’s not like you don’t already have javascript on this page. The reason why I suggested it was because you wouldn’t have to play around with the CMS itself but could simply include it on a post level. Oh well, as I said, I don’t mind the team list (although I have never looked at it tbh and it feels quite pointless :P )

          2. Robert Nyman wrote on May 29th, 2012 at 10:51:

            Well, yes, it could be done. But generally I think it would be a hassle/too much work to do it for each post.
            And it’s ok if you find it pointless. :-)

            But for us who attend a lot of conferences, it’s a good way for people to see us and recognize us from a Mozilla context.

Comments are closed for this article.