Embedding Policies
Some of these may look familiar as UPI policies. I did review them in terms of application to embedding and have decided they are to apply to both. :)
Policy: Do not offer custom embedding code.
Explanation: This is outside the scope of LiveJournal Support. You may only offer the code described on the Embedding Developer page.
Side Note: This is not to say that you must tell the user they can only use the methods and implementations offered at the developer page, but LiveJournal Support is not responsible for assisting the user in finding new or different ways of implementation.
Policy: Diagnose LiveJournal-related embedding only.
Explanation: It's outside the scope of LiveJournal Support to teach someone to use their choice of embedding method. If they are having difficulties recognising why something is not working, it is acceptable to point out the problem in general and recommend they consult the method's documentation if they do not understand how to resolve the issue.
Side Note: It is also acceptable to recommend they pick another method should they not successfully resolve the issue on their own.
Policy: Effective immediately but not retroactively, interims will be given only to those who are actively working in the category.
Explanation: Only those with experience and knowledge should have interims in embedding -- it seems illogical to remove privileges for inactivity or "tidyness" yet give them to people who may never use them. Additionally, the original logic for giving them was that not everything opened in embedding actually belongs there. It is preferable to have those experienced with embedding determing what to move. There is an abundance of people who are able to move, who do have this experience.
Side Note: Those who have received I2 without working in the category, or have jumped ahead of their current level, will either continue to be worked with to earn their level by merit or will be dropped for inactivity at the normally scheduled intervals of once per quarter.*
Exception: This does not apply to abuse I2s, where confidentiality, security and other sensitive information may factor in.
Policy: Do not show a preference for a certain embedding method.
Explanation: It's not within the scope of LiveJournal Support to lecture users on the pros and cons of each embedding method. It is, if applicable, acceptable to briefly explain the differences of each, though it is preferrable to warn a user that some may not be available to him/her.
Exception: Do not recommend PHP method #4, the include() method. If a user states that he or she is using this method, recommend that another method is chosen immediately. PHP method #4 presents a potential -- though likely obscure -- security problem, and developers may be unwilling to remove the method at present.
Policy: Do not refer users to Zilla items. Always CC me on embedding related Zilla items.
Explanation: If you report a bug that relates to userpics or embedding, please CC me so I can easily track its progress or comment on it without having to find it. Additionally, never tell a user a bug number or give a link in your support request. You may either say it is a known issue and being looked into, or you may say it's been reported (e.g. if you've just reported it). You can additionally offer workarounds if they exist.
Side Note: It is acceptable, if you are able to comment, to request diagnostic information (browser, OS, internet connection, link to the embedded page, embedded style ID, etc.).
Exception: If the user is, for example, a support volunteer or someone else you know to be already familiar with Zilla, you may post a link to the Zilla item.
Policy: All embedding supporthelps are required to watch this community as well as
lj_support.
Explanation: There are many discussions going on here that supporthelps should be watching, if not participating in. Participation is preferred, but not mandatory.
Side Note: It is not required that you actually "watch" the community in the sense of having it on your friends list, but the only other way I have of knowing you are keeping up is by participation -- in other words, if you aren't "watching," you will need to be participating.
Policy: All volunteers may be given the embedding tests to earn I1 and I2. Supporthelp is earned by hands-on experience.
Explanation: As embedding is the smallest category, the practical solution to judging experience is to offer a test to earn I1 and I2. However, I feel the best way to effectively learn embedding and earn supporthelp is through actual board experience, thusly supporthelp remains attainable solely through board experience and reviews thereof.
* Regularly scheduled intervals of priv-activity review will be once per quarter: January, April, July, and October.
That's all I can come up with right now. I'll edit this page if I get a flash of inspiration or one of you lovely people has a good addition. :)
Policy: Do not offer custom embedding code.
Explanation: This is outside the scope of LiveJournal Support. You may only offer the code described on the Embedding Developer page.
Side Note: This is not to say that you must tell the user they can only use the methods and implementations offered at the developer page, but LiveJournal Support is not responsible for assisting the user in finding new or different ways of implementation.
Policy: Diagnose LiveJournal-related embedding only.
Explanation: It's outside the scope of LiveJournal Support to teach someone to use their choice of embedding method. If they are having difficulties recognising why something is not working, it is acceptable to point out the problem in general and recommend they consult the method's documentation if they do not understand how to resolve the issue.
Side Note: It is also acceptable to recommend they pick another method should they not successfully resolve the issue on their own.
Policy: Effective immediately but not retroactively, interims will be given only to those who are actively working in the category.
Explanation: Only those with experience and knowledge should have interims in embedding -- it seems illogical to remove privileges for inactivity or "tidyness" yet give them to people who may never use them. Additionally, the original logic for giving them was that not everything opened in embedding actually belongs there. It is preferable to have those experienced with embedding determing what to move. There is an abundance of people who are able to move, who do have this experience.
Side Note: Those who have received I2 without working in the category, or have jumped ahead of their current level, will either continue to be worked with to earn their level by merit or will be dropped for inactivity at the normally scheduled intervals of once per quarter.*
Exception: This does not apply to abuse I2s, where confidentiality, security and other sensitive information may factor in.
Policy: Do not show a preference for a certain embedding method.
Explanation: It's not within the scope of LiveJournal Support to lecture users on the pros and cons of each embedding method. It is, if applicable, acceptable to briefly explain the differences of each, though it is preferrable to warn a user that some may not be available to him/her.
Exception: Do not recommend PHP method #4, the include() method. If a user states that he or she is using this method, recommend that another method is chosen immediately. PHP method #4 presents a potential -- though likely obscure -- security problem, and developers may be unwilling to remove the method at present.
Policy: Do not refer users to Zilla items. Always CC me on embedding related Zilla items.
Explanation: If you report a bug that relates to userpics or embedding, please CC me so I can easily track its progress or comment on it without having to find it. Additionally, never tell a user a bug number or give a link in your support request. You may either say it is a known issue and being looked into, or you may say it's been reported (e.g. if you've just reported it). You can additionally offer workarounds if they exist.
Side Note: It is acceptable, if you are able to comment, to request diagnostic information (browser, OS, internet connection, link to the embedded page, embedded style ID, etc.).
Exception: If the user is, for example, a support volunteer or someone else you know to be already familiar with Zilla, you may post a link to the Zilla item.
Policy: All embedding supporthelps are required to watch this community as well as
lj_support.Explanation: There are many discussions going on here that supporthelps should be watching, if not participating in. Participation is preferred, but not mandatory.
Side Note: It is not required that you actually "watch" the community in the sense of having it on your friends list, but the only other way I have of knowing you are keeping up is by participation -- in other words, if you aren't "watching," you will need to be participating.
Policy: All volunteers may be given the embedding tests to earn I1 and I2. Supporthelp is earned by hands-on experience.
Explanation: As embedding is the smallest category, the practical solution to judging experience is to offer a test to earn I1 and I2. However, I feel the best way to effectively learn embedding and earn supporthelp is through actual board experience, thusly supporthelp remains attainable solely through board experience and reviews thereof.
* Regularly scheduled intervals of priv-activity review will be once per quarter: January, April, July, and October.
That's all I can come up with right now. I'll edit this page if I get a flash of inspiration or one of you lovely people has a good addition. :)