Write blog post for Glow 1.0 retirement

RESOLVED FIXED

Status

Websites
website-archive.mozilla.org
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: ryansnyder, Unassigned)

Tracking

Details

A stub blog post for Glow 1.0 has been placed at:
http://blog.mozilla.com/website-archive/2011/06/14/glow-1-0/

John and Mayumi, please submit a 1-2 paragraph writeup about the accomplishments of Glow into this ticket.  Also include the best 3-5 articles about Glow that we can link to.

Daniel, please submit a 1 paragraph writeup about the technical side of Glow in this ticket.  Also include a link to the blog post that describes the technical aspects of Glow in depth.

I will add screenshots for Glow to the blog post.

Comment 1

6 years ago
First pass at copy from me & Mayumi. I'd be happy to edit this & Daniel's text once we have both so they fit together well.

Here's what we have for now:

We launched the first version of glow.mozilla.org with the Firefox 4 release in March as a way to visualize Firefox downloads and community involvement around the world.  Thanks to the development skill of Matthew Claypotch and Jeff Balogh, and the design talents of Sean Martell, it was a great success, with more than 1.2 million unique visitors and frequent press mentions. (It was also a pretty nifty demo of some of the best open technology the modern web has to offer.)

As we move toward a new rapid release cycle, we are finding new ways of measuring Firefox success across the globe. So, we've temporarily pulled Glow offline while we cook up the next awesome iteration. Thanks for your support, and stay tuned for more Glow in the near future!  

If you are interested in learning the technical details behind Glow check out the source code at [insert link], or view an _archived version of the original site_. 

(not sure if "archived version" is the right way to refer to what Jeff mentioned the other day, so feel free to update)

Also, here are some links to articles that refer to Glow. We can either point to some of these from "frequent press mentions" in the first paragraph, or just list some at the end of the post. Am open to whatever you prefer:

http://www.geek.com/articles/news/mozillas-real-time-view-of-firefox-4-downloads-20110322/ 
http://www.goodgearguide.com.au/article/380693/mozilla_site_shows_firefox_4_downloads_real-time/ 
http://www.pcmag.com/article2/0,2817,2382394,00.asp
http://asia.cnet.com/crave/firefox-4-doubles-ie9s-download-tally-in-24-hours-62208009.htm
http://www.computerworld.com.au/article/380979/firefox_4_speeds_past_20_million_downloads/?fp=4&fpid=1968336438
http://unplugged.rcrwireless.com/index.php/20110324/news/7903/firefox-4-48-hours-18-million-downloads/
http://www.pcworld.in/news/mozilla-firefox-4-approaching-6-million-downloads-and-counting-47252011
http://techleash.com/2011/03/firefox-downloaded-5-million-times-counting-within-24-hours/ 
http://www.tomshardware.com/news/Firefox-4-Downloads-Internet-Explorer-Day-one-Stats,12437.html
Blocks: 655402
Blog post updated at:
http://blog.mozilla.com/website-archive/2011/06/14/glow-1-0/

Comment 3

6 years ago
Looks great, thanks Ryan.
(In reply to comment #1)
> 
> If you are interested in learning the technical details behind Glow check
> out the source code at [insert link], or view an _archived version of the
> original site_. 
> 

The first version of Glow used several technologies including SQLStream and HBase to process download request logs in real time and make them available for the site to display.
If you are interested in learning the technical details behind Glow read this article from the Mozilla Metrics team [ http://blog.mozilla.com/data/2011/03/22/how-glow-mozilla-org-gets-its-data/ ] which has links to the source code repositories.
Thanks Daniel - Blog post updated at:
http://blog.mozilla.com/website-archive/2011/06/14/glow-1-0/
Is this complete?
Calling this complete.  Let me know if any changes are needed on the post.  Thanks!
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.