Closed
Bug 449252
Opened 16 years ago
Closed 16 years ago
Blog aggregator for messaging blogs
Categories
(Mozilla Messaging Graveyard :: Server Operations, defect)
Mozilla Messaging Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: sipaq, Unassigned)
Details
Per the weekly confcall: Something like planet.mozillamessaging.com would be a cool thing. Blogs to add from looking at planet.mozilla.org: - http://www.visophyte.org/blog - Andrew Sutherland - http://clarkbw.net/blog - Bryan Clark - http://weblogs.mozillazine.org/calendar/ - Calendar Weblog - http://weblogs.mozillazine.org/dmose/ - Dan Mosedale - http://ascher.ca/blog - David Ascher - http://blog.mozilla.com/bienvenu - David Bienvenu - http://blog.instantbird.org/ - Instantbird - http://quetzalcoatal.blogspot.com - Joshua Cranmer - http://ccgi.standard8.plus.com/blog - Mark Banner - http://noc.mozillamessaging.com - Mozilla Messaging NOC - http://gozer.ectoplasm.org/blog/ - Philippe M. Chiasson - http://home.kairo.at/?d=w&i=1&m=v&f.lang=en - Robert Kaiser - http://www.rumblingedge.com - The Rumbling Edge - http://scott-macgregor.org/blog - Scott MacGregor - http://weblogs.mozillazine.org/seamonkey/ - SeaMonkey - http://weblogs.mozillazine.org/seamonkey-qa - SeaMonkey QA - http://smtt.blogspot.com/ - SeaMonkey Trunk Tracker
Comment 1•16 years ago
|
||
We can easily run a planet aggregator somewhere on our shiny, new, hardware, no problem. I'll file dependant bugs on the required work items.
Summary: Create a blog tracker for messaging-related blogs → Blog aggregator for messaging blogs
Reporter | ||
Comment 2•16 years ago
|
||
Gozer, any news on this? I haven't seen any dependencies in this bug yet?
Comment 3•16 years ago
|
||
Busy sorting out a web infrastructure to run this service on. It's completed now, so running our own planet can proceed shortly. I'd expect to see it live, possibly ugly, sometime next week (Sept 1 - Sept 5)
Reporter | ||
Comment 4•16 years ago
|
||
Gozer, any update? It's been a few weeks...
Comment 5•16 years ago
|
||
I'll put on my plate this week, once Alpha 3 is behind us.
Comment 6•16 years ago
|
||
Configuration and templates are here: http://svn.mozilla.org/projects/mozillamessaging.com/planet.mozillamessaging.com/trunk/ Staging preview is here: http://stage.planet.mozillamessaging.com/ (Note, it's not automatically updating yet, just a starting point for look-and-feel customization)
Comment 7•16 years ago
|
||
(In reply to comment #6) > Configuration and templates are here: > > http://svn.mozilla.org/projects/mozillamessaging.com/planet.mozillamessaging.com/trunk/ Ugh, please don't pollute the svn namespace like that. If you need a new svn repo, just ask. Don't reuse existing ones for completely different things.
Comment 8•16 years ago
|
||
Actually, that's the opposite of pollution, the goal is to group all mozillamessaging.com things in SVN under http://svn.mozilla.org/projects/mozillamessaging.com/ www.mozillamessaging.com/trunk /tags planet.mozillamessaging.com/trunk /tags spreadthunderbird.com/trunk /tags And so on. Right now, www is still not moved because of some automation scripts that'll need to change. The idea is to keep everything under a single roof (so to speak) to keep things clearly separate. Just my 0.02$
Comment 9•16 years ago
|
||
If you want to do that, why not just get you a top-level directory like http://svn.mozilla.org/momo/ (substitute momo for "mozillamessaging" if you like) and just put stuff under there? That makes more sense, I think.
Comment 10•16 years ago
|
||
Ping? How do we want to proceed with this one? The basic aggregator is in place, but do we want to just launch it like this? I'd think we'd want somebody to get it better integrated with the current look-n-feel of mozillamessaging.com, no ?
Comment 11•16 years ago
|
||
It's at : Production: http://planet.mozillamessaging.com/ Staging: http://stage.planet.mozillamessaging.com/ Trunk: http://trunk.planet.mozillamessaging.com/
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•