Planet Jetpack *BETA* & the return of @mozillajetpack

Jeff Griffiths

8

Last month at the all-hands someone ( Wes Kocher? ) suggested the idea of curating a list of feeds and posts specifically focused on the Jetpack project. I’ve been crazy busy since then but finally got around to deploying Planet Jetpack yesterday to my Linode box as a beta as I wait some more formal hosting. The web page is here, but more importantly the feedburner feed is here. The source code is of course on github.

If you’re interested in keeping up with the Jetpack project and community, feel free to subscribe! As well, if you post on your blog about the SDK and would like those posts aggregated, please either email me at jgriffiths (at) mozilla.com, open an issue on github or ( ideally! ) do this:

  • fork the github repo
  • check out the platnet-jetpack branch
  • add your feed to jetpack/config.ini
  • send me a pull request.

I also recently discovered the nascent @mozillajetpack account on twitter. After some searching I managed to discover the former owners who set it up when Jetpack was still a Labs project. The intention is to post a low-traffic, high signal-to-noise ratio stream of tweets about SDK events, posts and people. If this is of interest to you please follow or add the account to a list. If you see anything in your web travels that might be of interest to other people in the Jetpack project, feel free to share with @mozillajetpack and I will RT!

8 responses

  1. John Nagle wrote on ::

    We need fewer places where information about Mozilla add-ons appears, not more of them.
    There’s MDN, there’s AMO, there’s a Google group, there’s a blog, there’s a forum, there’s a Twitter feed, and there’s Bugzilla. Most of which have separate log-in systems.

    So let’s add a Facebook page!

    No, really. Some of those need to die off.

    1. Johan Sundström wrote on ::

      More is indeed less.

      And less, as in one authoritative central place with well curated, accessible and kept-up-to-date details of the hows and whats, good practices, and so on, is more.

      And much harder to create.

      1. John Nagle wrote on ::

        Indeed, an authoritative central place is harder to create.

        I forgot MozillaZine and the Mozilla Wiki! That’s 9 places, which is about 5 too many.

        1. Jeff Griffiths wrote on ::

          If I’m successful, you should be able to track most or all SDK-related posts ( as opposed to docs or non-SDK add-on posts ) by subscribing to this one feed.

          I agree that there are too many channels. I have no plans to add a FB page :). Aggregating a bunch of Jetpack-centric blogs still feels like a win though, as it feels like a more convenient way to track a bunch of disparate sources without having to susbcribe to the PMO firehose.

          In my experience the valuable channels are these blogs, the jetpack tag on stackoverflow and the jetpack google group. We do get some questions from developers on the amo forums, but markedly less than the google group. It’s been in the back of my mind to streamline this, and I’d love any suggestions you might have.

          1. John Nagle, Silicon Valley, CA wrote on ::

            I didn’t know about the jetpack tag on stackoverflow. That’s 10.

  2. Jeff Griffiths wrote on ::

    For me the ‘valuable’ list is 3, but I hesitate to start killing off information channels. Which ones do you think provide the most currently?

    Assuming that Planet Jetpack is the new kid on the block and should get some time to prove its worth. :D

  3. John Nagle, Silicon Valley, CA wrote on ::

    One login to rule them all. Get the keepers on a single sign in system and kill the others.

    1. Jeff Griffiths wrote on ::

      John: I completely agree wit you on single-sign-on. I’m hoping we can use browserId for this; it has as one of its design goals that it should be easy to implement on legacy systems ( of which we have a lot! )