Thank you for your quick approach and I hope important pads will be recovered soon!
I tried to recover an urgent working pad of our local SuMo team, but failed to do so. Can you please give me a copy of this pad. This pad is very much important for our running sprint, if we can not recover it, we (reviewer) will have hard time .
Wow, thats service. I have connection to the former etherpad and coult save our meetingcontent.
Thank you very much.
(and sorry for my poor english;-)
We now have a process for retrieving team pads … please use this form to make a request.
I’ve started a topic in Community WebDev to discuss what features are missing from Etherpad Lite:
Update – Public pads from the following teams have been migrated to the new Etherpad Lite instance using the “http://public.etherpad-mozilla.org/p/teamname-oldpadname” format. For example https://remo.etherpad.mozilla.org/call-20-08-15 becomes https://public.etherpad-mozilla.org/p/remo-call-20-08-15
Many of the pads are named slightly differently. Instead of the “-” after the teamname, it should be “.” … if a pad doesn’t work, please try this different naming convention.
Those admins who requested access for these pads (through http://goo.gl/forms/0qD9tkRlBU) have been emailed a list of the pads that have been migrated and the new URLs. Please continue using that form and we will continue migration.
Sorry … bangladesh should have been included in the list. It has been migrated.
Thank you George for driving this and the rest of the team for making it happen.
Are there any plans for the private or password protected pads?
More pads migrated. See updated list:
We’re working on plans for this.
I still don’t know if I should laugh or cry. One word before shutting it down and all our work would have been saved (in a matter of minutes). But now, WE are in a panic and YOU have all this extra work. And the private pads that are the most critical are gone for now >_>
Thanks for trying to fix this mess, at least… I guess…
[quote=“seeam, post:18, topic:4529”]
I am a volunteer from Mozilla Bangladesh community. Mostly I contribute on SuMo l10, forum and advocacy. The thing is all of our past event and meeting records, future events planning was written in Etherpad. Even we have two event on Friday and Saturday. All the session planning was there and that pad was so important for us. Now I can’t recover it through the method you describe. Closing etherpad for bugs is a good decision but it’s really really very bad decision doing it without our acknowledgment. I think there are so many Mozillians who find this odd. Because that was our data and it’s gone without our confirmation. You people are just saying it now that, “It must be retired”. That means you were planning to close it, so you may give us a notice to shift our data before closing. In a open and broad community closing a key communication tool without any confirmation, it is really poor decision. … So I am really frustrated about this decision.[/quote]
Exactly. This is typical corporate behavior. Which Mozilla claims to be different from because of its transparency/open communication. The only way to have found out about this in advance was to accidentally stumble across the etherpad retirement bug (still hidden behind a security flag; closest public bug: Bug 831448) or hear about it from a Mozilla employee who happened to know.
Tons of sites in the past have announced retirement dates for parts of their sites months in advance, giving people enough time to backup/recover what they need. The exaggerated “security” issues mentioned here were not enough to require a immediate takedown. I felt completely blindsided by this. Sometimes Mozilla gets it right (old Sync servers graceful retirement [plus bonus 2nd notice with firm shutdown date], the Webmaker tools retirement/updates, Personas move to AMO Themes + Migration progress Update) and other times they get it wrong (this current Etherpad mess). Anyway, no need to send this feedback to the “appropriate channels” where it shall fall on deaf ears, I just wanted to say my piece. Til the next time when MozillaWiki gets forcibly retired with zero notice. Which I thought to be impossible but now I’m not so sure.
Who from IT will stand up and say they could have done this retirement better? Even the VP of IT couldn’t do the email blast for reasons unknown. Anyway, thanks George for trying to make the best of a bad situation.
Yes I feel the same way. Also Mozilla Manifesto states that, “Transparent community-based processes promote participation, accountability and trust.”. And I think that “appropriate channels” have failed to maintain the manifesto.
My open-source project team lost its entire project planning archive when you took your Etherpad service down. As I said in January when I filled out the form you provided for recovering team pads, it would have been really nice to get some kind of advance warning that this was going to happen, so that we could rescue our data.
It would also have been really nice to get any response whatsoever from submitting that form. Since it’s now almost March, no one has contacted me, and the URL patterns provided don’t work, I’m trying again. Is there any way to recover our old pads?
FWIW, I also emailed the above comment to EtherpadTransition@mozilla.com. George responded within 24h and I had my team’s pad archive back within 48h. Thanks, George and Justin!
I and my group have been collaborating using public.etherpad-mozilla.org for a while now - and have found it helpful to embed the page using iframe. But since a day or so ago (today is 22nd November 2016) our web browsers raise a security alert and don’t allow the page to load. It appears to be the security settings of the etherpad page. Is there any way to get it back to as it was - because the mozilla etherpad has been the most stable that we have used.
Probably not the best idea… Old outdated plugins, development stagnated or stopped and all you can find are Translation Wiki commits (that’s not active development). Open PRs, no reaction to bugs introduced with commits. That’s what I can see while looking through this project.
The transition happened over two year ago