Closed Bug 609824 Opened 11 years ago Closed 3 years ago
Re-add Bloglines to the feed reader options
+++ This bug was initially created as a clone of Bug #595485 +++ (Bug 595485 Comment 20) > http://techcrunch.com/2010/11/04/exclusive-bloglines-will-be-resurrected-by-iac-funded-merchantcircle/ > > The patch should be backed out!
I don't think that "the patch should be backed out!" directly follows from that, for at least two reasons: * Despite all the repetition of "seamless" I don't see any reason for "During the month of December, you will be able to easily port your feeds over to the MerchantCircle-powered service." other than "it's not going to be at the same URL." Whoever at MoCo deals with getting honest answers out of partners needs to have assurance that the same subscription URL is going to continue working through the lifetime of Fx 4 before we put it back in just like it was. * There's no reason I can see to believe that MerchantCircle will be running something that we want to have as one of our few default feed readers. Ask found it too expensive to run, and the new owners not only have to pay for running it, but also have to pay Ask for it, unless it's so valueless that they got it for free. Maybe they will manage to either make it pay, or swallow a loss on it in return for having it working as a search engine for their own users, without having to turn it into something we wouldn't want to recommend, but at this point we have absolutely no idea what it's actually going to be like.
Assignee: philringnalda → nobody
Status: ASSIGNED → NEW
Summary: Undo: remove Bloglines from the feed reader options → Re-add Bloglines to the feed reader options
3 things: #1 Merchant circle is a block away from the Mozilla MV office #2 I have a contact there. I'll be talking with her tomorrow about this #3 Ccing kev
(In reply to comment #2) > #3 Ccing kev You didn't, but I just did for you.
Weird, I thought I did. Thanks for fixing.
Neither one of you did, since Axel cc'ed him to the original bug a couple of months ago, so he's been cc'ed to the clone all along.
Concur with comment #1, and will wait for Christian to have a meeting w/his contact to find out what the deal is. Since indications are that IAC is licensing the brand and Merchant Circle will be providing a different service with that brand, I want to wait until we have more info before changing course on anything related to the Bloglines branding/service.
We had the meeting, we are going to add this back.
(In reply to comment #7) > We had the meeting, we are going to add this back. Christian, any chance you can elaborate on the outcome of this, and in particular responding to philor's concerns with c#1 so I can try and evaluate the benefit of re-adding this service for SeaMonkey users.
(In reply to comment #9) > (In reply to comment #7) > > We had the meeting, we are going to add this back. > > Christian, any chance you can elaborate on the outcome of this, and in > particular responding to philor's concerns with c#1 so I can try and evaluate > the benefit of re-adding this service for SeaMonkey users. Yep, sorry. We met with Merchant Circle and they assured us that: a) They got handed the keys to the existing services so the transition would be smooth. They will not be moving the services off the existing domain/URLs. b) They intend to keep it at the core what it is now c) They think RSS has a huge future and they are in it for the long haul d) It would stay the same until this past December and then they would start adding features I think if in the future any of these don't hold true we can easily yank them back out, but for the time being Kev and I were satisfied.
(In reply to comment #7) > We had the meeting, we are going to add this back. (In reply to comment #10) > I think if in the future any of these don't hold true we can easily yank them > back out, but for the time being Kev and I were satisfied. Thanks for this update. Is there any way we can we see any data from Merchant Circle to try to inform our decision so our volunteer community doesn't have to do, undo, and possibly do this all again?
Attachment #505209 - Flags: review?(gavin.sharp) → review+
Comment on attachment 505209 [details] [diff] [review] Add bloglines back, undoing bug 595485 Approving as it is reviewed, I wrote it, and we told the partner we would get this back in.
Attachment #505209 - Flags: approval22.214.171.124+
Actually, reopening as it isn't fixes on trunk. I'm not going to land it there (or on mozilla-2.0) until I talk to Kev.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #14) > Actually, reopening as it isn't fixes on trunk. I'm not going to land it > there (or on mozilla-2.0) until I talk to Kev. LegNeato, did we ever get this convo going and/or what is our status here?
(In reply to Justin Wood (:Callek) from comment #15) > (In reply to comment #14) > > Actually, reopening as it isn't fixes on trunk. I'm not going to land it > > there (or on mozilla-2.0) until I talk to Kev. Kev, LegNeato... ping? WONTFIX, or what???
The conversation did happen, and we agreed it would be acceptable to re-add it to en-US and offer it up for locales to take at their discretion. Adding Asa to the conversation as well, and we should re-review whether bloglines is still offering the same service as before. Our news reader options are pretty limited, so I wouldn't mind re-adding them, but we should re-review the service and ensure the UX is still decent. I'll circle up with Asa on it, and ideally we can take a decision within 24 hours.
(In reply to Kev [:kev] Needham from comment #17) > I'll circle up with Asa on it, and ideally we can take a decision within 24 > hours. Sadly, life is not ideal. Almost a month later, any update?
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 3 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.