Etherpad/Best Practices: Difference between revisions

Latest revision as of 22:15, 8 September 2015

Over time, we've noticed certain issues with Etherpad:

Etherpad does not cope well with certain Unicode characters / emojis. They may cause your pad to become inaccessible. Avoid them, if possible.
If you have a large number of changes to make to a pad, it is better to make the changes in a separate text editor, then cut-and-paste them into the Etherpad all at once. (Etherpad will then store them as one big change rather than multiple smaller changes.)
Pads that a large number of revisions / changes are hard to stay connected to. Examples include pads that are re-used for daily or weekly meetings. Please consider creating new pads for each meeting or occasionally archiving an old meeting pad (changing its name) and starting a new one (under the "regular" name).

If you encounter a problem with an Etherpad, you can get help in the #moc channel in IRC or file a bug in Infrastructure & Operations :: MOC: Service Requests

@@ Line 1: / Line 1: @@
-Test
+Over time, we've noticed certain issues with Etherpad:
+* Etherpad does not cope well with certain Unicode characters / emojis.  They may cause your pad to become inaccessible.  Avoid them, if possible.
+* If you have a large number of changes to make to a pad, it is better to make the changes in a separate text editor, then cut-and-paste them into the Etherpad all at once.  (Etherpad will then store them as one big change rather than multiple smaller changes.)
+* Pads that a large number of revisions / changes are hard to stay connected to.  Examples include pads that are re-used for daily or weekly meetings.  Please consider creating new pads for each meeting or occasionally archiving an old meeting pad (changing its name) and starting a new one (under the "regular" name).
+If you encounter a problem with an Etherpad, you can get help in the '''#moc''' channel in IRC or file a bug in [https://bugzilla.mozilla.org/enter_bug.cgi?product=Infrastructure%20%26%20Operations&component=MOC%3A%20Service%20Requests Infrastructure & Operations :: MOC: Service Requests]