Sub-editors' Home Page | Why be a Sub-editor? | What do the Sub-editors do? | Sub-editors' Code of Conduct | Volunteer to be a Sub-editor

This document contains some common-sense guidelines to being a Sub-editor. By joining the scheme you accept this code of conduct; if you do not want to accept this code, then please let us know as soon as possible. This document is not supposed to be heavy-handed: it's just a sensible guide to being a good Sub-editor.

The Sub-editors' Code

Sub-editors are under no obligation to edit a specific number of entries in any specific period of time. All we ask is that you are committed to the project and that you let us know if you want to take a break. If you are unable to edit an average of one entry per week (that's four weeks for a batch of four entries, for example), we would rather you told us; we can then re-allocate the entries, and send you a new batch when you have more time to continue.

If at some point in the future you decide that you no longer wish to be a part of the project, please let us know.

Very few of our Sub-editors are professional journalists. It is very important to the project that entries are edited to a high standard. It is therefore important that Sub-editors have: a willingness to learn; are prepared to accept feedback from the in-house editorial team; and agree to follow the editorial guidelines and style guidelines. Whilst most subbed Guide Entries are accepted into the Edited Guide without further changes by the in-house editorial team, on occasion changes are made. We are happy to discuss alterations that we have made to subbed articles and give feedback to the Sub-editors, but it must be accepted that the Editor has the final decision.

Sub-editors have a responsibility to the Researchers whose work they are subbing and to the other members of the team. If someone is having difficulty in a particular area the in-house editorial team is only too willing to help and give feedback. But it is possible that the situation will arise when the quality of a Sub-editor's work falls consistently below that of the other team members, for whatever reason. If the Sub-editor fails to learn and respond to feedback from the in-house editorial team, they will eventually be asked to resign from the Sub-editor team.

Non-disclosure

One of the cool things about being an h2g2 volunteer is that we let you see new versions of the site before they go live - in fact, your comments are vital in enabling us to get new versions of the site just right.

To enable us to let you see everything, we ask that you do not talk about what you see with anyone who is not bound by this code. We will be explicit about things you should keep to yourself and will let you know if and when you may talk about those things on site - we will communicate this information via the mailing list. Anyone who leaks confidential information will obviously be asked to leave the scheme.

The main reason we need to keep a lid on confidential information is to prevent disappointment in the Community. If we show you a cool new feature and the rest of the site finds out about it, then if we decide to drop that feature (for whatever reason) then we will doubtless annoy considerable numbers of Researchers. It's just common sense, really.

Basic Terms and Conditions of h2g2

This section is just a reminder of the terms you have already agreed to on h2g2, and points out that the same terms apply to the mailing lists and email associated with the volunteer schemes. We're not asking you to agree to anything new.

Everyone who participates in h2g2 is bound by the House Rules of the site. The same rules apply to volunteers' participation in the volunteer mailing lists. It is very easy for messages to be misinterpreted, so it is important that everyone participating in the scheme takes great care not to offend or annoy other members. Anyone being deliberately offensive will be warned and, if necessary, will be removed from the scheme.