WeeklyUpdates/2014-01-27: Difference between revisions

Jump to navigation Jump to search
Line 159: Line 159:


=== IT ===
=== IT ===
''Speaker Location:''
''San Francisco:''
 
Etherpad tips
 
Some people have periodically mentioned issues of an etherpad failing to load after much use. In order to avoid these problems, Mozilla IT recommends following these guidelines...
 
To explain a little further:
- etherpad works best when you're doing short term team planning.
- It is not efficient for long term tasks, or pad name re-use.
 
Why, Obi-Wan, is this not so?
- Etherpad stores EVERY update in the database (even single character changes if there's a small pause between them)
- therefore gets clogged/slowed down after ~24 hours of use in a pad (may be faster or slower depending upon how much info is input into the pad).
 
A few general guidelines of how to make etherpad work better and more reliably for you:
 
- Don't reuse pads just to have the same pad name.
(This is the biggest reason why pads crash. People delete the contents of a pad and re-use it to keep the same pad name. This is a bad idea. What's really happening is the old pad is still there, you're just writing over top of it, and making the pad that much larger in the database)
 
- If you've been working on a pad for more than 3-4 days of work (e.g. 4 Mondays in a row, or 4 days in a row, all the same), start a new pad.
 
- If you have a large copy/paste section, don't put it in the pad, pastebin it and put the pastebin link in the pad.
 
- If you've put a lot of text into a pad ( would equate to 5-10+ pages worth of a word document), start a new pad.
 
- If you plan on doing any of the above, use google docs instead.


=== Web Compatibility ===
=== Web Compatibility ===
Confirmed users
50

edits

Navigation menu