@AllanSmithee The archive took hours to make and was obviously done before you had made changes.
I think that content is only accessible through a bit of a process. How important is it to you? And how urgent?
Wouldn’t it be possible for converting all public+team pads to public.etherpad-mozilla.org/p/team-padname automatically and set a redirect from the old link?
@asdofindia Right now that can’t be done unless we have admin access to the team in order to get the list of all URLs (among other requirements).
Good Question:-)
We used the etherpad for protocolling a meeting. So I would say quite important and urgend.
Thanks for your quick answer. I would appeciate, if you can tell me, what is possible to recover and in wich periode of time.
Hello George,
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. Even I have tried so many preferences tweak after seeing the “Secure Connection Failed” error on etherpad’s website. And I think many other Mozillian will do the same thing. So I am really frustrated about this decision.
3 Likes
Thanks for the feedback on the impact that this is having. I will pass it
along to those in Mozilla IT.
We’ve created a process now for getting the info required to recover team
pads. We can’t commit to a timeline on this yet but please fill out the Doc
and we’ll keep you updated:
Thank you for your quick approach and I hope important pads will be recovered soon!
Hi @george
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;-)
1 Like
We now have a process for retrieving team pads … please use this form to make a request.
1 Like
I’ve started a topic in Community WebDev to discuss what features are missing from Etherpad Lite:
https://discourse.mozilla-community.org/t/what-do-we-want-in-etherpad-lite/4550
4 Likes
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.
remo
participation
mozhispano
partinfra
cbt
koolkids
fdn
fundraising
hivechi-team
kt
teach
codingrights
bangladesh
datacarpentry
demeeting
frenchmoz
gurumukhi
harvardinformatics
mozillatunisia
pakistan
stn
654fa15
kerala
mozillahyderabad
team17
l10n
majken
mcr
mozafrica
mozilla-my
mozillasec
mozita
moznativo
peru
romania
ropensci
soft
swcarpentry
yomo
advocacy-in
antivig
apc
apc-impact
arabicmozilla
balkans
boletimav
chaasof
cipp
madagascar
melek
yo
cschh
unefox
babokimscans2
viglug
mozqabd
appdaystirupati
festival
kerala
frish
bfr
remocamp14
ireland
linksceem
cartwright
keenkiwis
mozmex
rpgpl
zbraniecki
l20n
mozillarian
multilinguismo
webmaker
kuga
india
rpgogogo
mssl
marincecritmaispastresbien
oneocii
eac
mfti
fkv
tilidinmann
fs15
mzfr
onso-collaboration
tedic
dclauzel
foundation
brazil
onso
hybr1s
ia
solartraveller
gaa
naegajeiljalnaga
ourhouse
time
dd
wcsedu
pokarokamoka
2 Likes
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:
https://discourse.mozilla-community.org/t/etherpad-transition-to-etherpad-lite/4529/25
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…
1 Like
[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]
Well said!
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.
1 Like
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.