Merging or Linking Offers
From Tel'Laerad Wiki
Contents |
Introduction
Offers, typically from other IRC networks, but also from other online communities of other forms, to merge (also known as link) with Tel'Laerad, are quite welcome.
As part of aiming for our goals, as listed on the Goals of Tel'Laerad page, of being the best locale for roleplaying, gaming, and general discussion, and for actually conducting roleplaying, on the Internet, we're very much in favour of combining efforts with other people on these goals, and their own. If you have an interest in this, we very much do want to hear from you.
We, however, will not accept every offer that comes along, and are committed to ensuring that everyone relying on us can continue to do so, and that this is for the benefit of the users; continue reading for our general requirements when making an offer, and the information we want. Once you've some idea what you're saying, contact info@tellaerad.net, or one of the owners on IRC (Namegduf, Serian, or Taros), and we'll talk.
Offers Should Be Reasonable
Before even opening up communication, some things need considering. We are working towards our goals, We have, as our goals page mentions, our own ideas about how these goals are best accomplished. We have our own infrastructure and software. We have our own policies and relationship with our users. We have our own name and brand, our own style, and our own staff. And this is true for yourself, too.
This does not mean that we expect you to adopt our goals alone, all our ideas, all of our infrastructure and software, our policies entire and unchanged, and our name, brand, style, and staff. Nor does this mean that merger is impossible and impractical; if we are working on related, the same, or similar goals, there's no reason why we shouldn't be able to combine our efforts.
Rather, this means that you must be willing to negotiate. You must be willing to combine what we want with what you want. Precisely what is negotiable varies, depending on circumstances; as a general rule, if you can convince us your way of doing things is better for both our goals and philosophies for accomplishing them, then we'll be up for it. Sometimes, one or both sides will need to compromise. More elaboration on specific areas warranting it is below.
Name/Brand
We have invested a great amount of work into the "Tel'Laerad" brand. We are unwilling, as one of the few things we are quite firm on, to discuss the complete loss of our name; if you would require this, then it is unlikely to be worth your time contacting us.
You might be fairly fond of your own, and equally unwilling to do the same. Luckily, there is a large range of negotiation within that. In the case of major mergers, depending on circumstances, including sizes of both sides and whether there are sufficient differences in focus/services provided by the two sides, both names being brands of a larger organisation might be negotiable.
Software
Universally, convincing us to change software "just because we like ours better" is unacceptable in all major and most minor cases; if you would request this without reasoning to back it up, you are probably wasting your time.
As a general rule, our server software, its stability, reliability, and features are known and in most cases, believed to be the best existing. Some parts possesses numerous custom modules providing our special features, developed by ourselves, and patches tweaking it to function exactly as desired. Lastly, those directly used by the users are familiar to them, and they are who we above all else provide for.
At the current time, Tel'Laerad runs InspIRCd and Atheme on our IRC network. Our website runs Apache as the webserver, SMF as the forums, and MediaWiki as the wiki. It is exceedingly, exceedingly unlikely you can convince us change our IRCD at any point in the foreseeable future. Other software varies.
We are willing to talk, however, and for software we're not particularly attached to, if you know and prefer a better solution, it might not be such a hard sell. We can also develop functionality you like from other software for ours, and we like to add useful and good ideas.
Structure
Organisational structures vary; we like ours, but are willing to discuss others. As a general rule, you will need a better case than "historical reasons" for us to adopt something; for any good structure, this shouldn't be hard. Historical structures based solely around the oper levels of obsolete IRC server software, are likely to be a 'hard sell'; we are not purely an IRC network, nor do these levels make sense typically make sense for a network which is run as a single organisation (see "We Are One Organisation"), nor do they generally reasonably divide roles for an IRC network.
We Are One Organisation
Tel'Laerad does not follow the old models for its IRC network, or any other part, in which each server is an independent entity, their feature sets are determined separately per server, and users are entirely unsupported, and no global quality assurance happens, aside potentially via vote of the server admins.
Part of supporting the users and avoiding confusion or annoyance, in our view, is ensuring consistent rules, consistent availability of features, and thus requires consistent configuration, administration, software, and backups. Part of having high reliability and good features is ensuring that work can be carried out swiftly and without the bureaucratic need to contact numerous different people for different servers for the sole reason of avoiding shared access; time should be taken working on constructive things, not trying to get upgrades done. Additionally, staff selection must be selective and up to our standards.
As such, we are unwilling to adopt such a model, or any model whereby the two merging organisations are split into two "sides" still post-merger, or in which your server is simply linked to ours with no changes. This does not mean that we expect control of all servers and resources to be shared immediately post merger; some time to get to trust each other post-merger will be required on both sides and expected before all details are shared.
Rules
Tel'Laerad rules are, curiously as concepts go, designed to serve the users, by guaranteeing that they can use the network well by preventing factors outside their control or that they cannot repair from stopping them; the rules and active enforcement against harassment, account abuse and hijacking, and channel ban evasion particularly demonstrate this.
While accomplishing this goal, Tel'Laerad is fond of allowing the largest possible freedom of speech on its services; we like to let people use our services however they like, provided they are not disrupting other people or hurting anyone. As such, we do not adopt a "no adult materials or discussion whatsoever" policy; we adopt a fair saner rule for extreme cases, designed to hide them from sight and avoid them bothering those who would rather not interact with them or advertise places showing them.
In accomplishing these, we aim for simply explained, generic rules that outlaw precisely and just what is bad, and leave freedom to determine the "best" approach to violations to the enforcing staff; it's amazing what a polite word with someone can do in some cases, while other people simply need quick removal.
Outright scrapping any of the above is likely to prove impossible. While most forums are familiar with at least the first idea, IRC networks often are not; we regard this as part of supporting our users and are unwilling to change it.
We are proud of our rules, but quite willing to discuss changes to specific rules and policy, as this is an area in which a new, clearer way to write things, or a more solid but generic rule can easily be suggested, and new ideas are good. We may even be willing to adopt another base ruleset, probably with some revisions, if we like it, although this would be a hard sell; we consider ours some of the best out there.
Staffing
Tel'Laerad staff are people who contribute effort towards its maintenance, development, and support of its users; they all actively work towards us and volunteer their time, all are held to standards of proper behaviour and use of their power, and screwing them over is not an option; all staff must be able to remain staff. We are generally willing to let all active staff meeting these standards (which is often all) remain staff post merger ourselves.
Our primary requirement for staffship is that someone be able and willing to actively contribute in some way, even if only a few hours a week, and that they behave in a manner fitting for staff; our Staff Guidelines have more details. Lowering these standards significantly post-merger is likely to prove a hard sell; we have seen organisations without before. We may be willing to make a very limited number of exceptions to the activity requirements.
In terms of access, our principle concept is that all staff have access to what they need to do their jobs. Change to teams/granted access as policy goes fall under structure; what needs addressing here is that staff from both sides should still have access to what they need to do their job.