Closed
Bug 700485
Opened 13 years ago
Closed 13 years ago
people.mozilla.com/~faaborg/ is 404
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: clarkbw, Assigned: dumitru)
References
()
Details
The pages from Alex Faaborg's people site are either down or have been removed.
https://people.mozilla.com/~faaborg/
I'd like to have those pages put back up as they were please. There are a number of bugs and other places that reference the work that Alex places in his people.mozilla account.
for example: bug 683635
Thanks!
Assignee | ||
Comment 1•13 years ago
|
||
Alex Faaborg does not work for us any more, according to phonebook.
This is why his people account got disabled. However, the files are still there.
I cannot enable that link unfortunately.
A solution would be to move the files into someone else account, but Alex will need to approve that.
Assignee: server-ops → dgherman
Summary: faaborg people space → people.mozilla.com/~faaborg/ is 404
Comment 2•13 years ago
|
||
This is not a new problem. What has been done in the past that allowed this to keep working when employees left (as this same exact thing has been requested multiple times)? Why can't you just chown faaborg's directory to some other user (apache, for example), which would keep it working?
All existing links need to continue to work.
Reporter | ||
Comment 3•13 years ago
|
||
(In reply to Reed Loden [:reed] (very busy) from comment #2)
> All existing links need to continue to work.
yes, this is key. thanks!
Assignee | ||
Comment 4•13 years ago
|
||
There is no policy in place for such cases, thus I will go first through mrz/Corey/infrasec.
tl;dr
If an employee leaves the company, what happens to the files that were publicly available on people.m.o? The un-official hack was an Alias in apache to point the location back to the users public_html, but this sounds horrible to me.
Waiting for some infrasec policy on that.
Whiteboard: [infrasec policy?]
Comment 5•13 years ago
|
||
I'm fine with providing continued read access to files on a per request basis (such as this).
Comment 6•13 years ago
|
||
Can you fix sayre's blog too? Losing http://blog.mozilla.com/rob-sayre/2010/08/02/mozillas-new-javascript-value-representation/ caused lots of pain.
Assignee | ||
Comment 7•13 years ago
|
||
OK, should be working now.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [infrasec policy?]
Assignee | ||
Comment 8•13 years ago
|
||
(In reply to Jesse Ruderman from comment #6)
> Can you fix sayre's blog too? Losing
> http://blog.mozilla.com/rob-sayre/2010/08/02/mozillas-new-javascript-value-
> representation/ caused lots of pain.
This should be filed as a separate bug since it has nothing to do with the original request, thank you!
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•