SwiftBlog

Archive for May, 2009

Hey,

I realised that it was perhaps time to sit down and write again, in view of the fact that three weeks have now passed since my (fabulous, if I can say so myself) introduction to the SwiftBlog.

Now, I put out a request for topics that users would appreciate some enlightenment towards, and ‘Zanith’ put through a very valid question as to how SwiftIRC’s policies come to be, and how we operate ‘behind the scenes’.

Now, first of all, let me apologise for the fact that the phrase ‘behind the scenes’ was (quite aptly) used. For me, network policies are really things that should be proclaimed for all to hear and see rather than be hidden away behind a ‘Staff Only’ curtain. Unfortunately, I realise this isn’t always possible, and in many circumstances perhaps isn’t desirable for various policy reasons, but I do see a need to correct this somewhat – which is really what I intend SwiftBlog to achieve.

Now, on to the issue at hand: SwiftIRC policies. First of all, I guess it really depends what issue is first being decided, as this will change the scope of consideration. If the issue being decided is whether or not a server should be test-linked, then this is put to a vote before all Network Administrators and Server Administrators. I’m not going to go into the exact guidelines we abide by in this process, but sufficient discussion between this administrative tier goes on such that all of us can make an informed decision. As to the question of why Server Administrators are deemed capable of voting, it comes down to the fact that they are heavily involved at a server-level, and all of them are quite capable of assessing both the technical aspects of the potential server, as well as the more subtle nuances involved in the potential for contribution by the potential administrator.

If the issue is something else, then generally it depends upon the scope and impact of the policy. If the scope is fairly narrow, then usually a single Network Administrator will have, as his or her prerogative, the right to make a decision then and there. If this becomes and issue, then this will be met by a majority vote of the Network Administrators, but for the purpose of practical considerations this is preferable to no decision being made due to the presence of a bottleneck is bureaucratic processes.

If any issue is deemed a bit bigger, such as the appointment of a new global operator, then this will call upon a majority vote by the Network Administrators as this is not something to be solely decided.  In the past, a draft might be presented, which is subsequently redrafted through compromises in successive rounds before being put to a final vote. Regardless of what path is taken, heavy discussion will usually take place in #opers, to various degrees of gravity depending on the actual decision.

Now, if a decision is even larger, such as current plans to revamp the structure of support provided to users on the network, this involves a far more in-depth level of discussion (We even have our own forum to discuss this!), with all staff from the global operators upwards working out what would be best. This is a fairly slow process, but at the same time a wide variety of opinions is infinitely more preferable than a single person make the decisions.

By way of discussion, this takes place in various areas. Firstly, all global operators have access to #opers, where a great deal of real-time discussion is pretty much constantly taking place. To make sure we don’t forget what goes on, we also make use of the forums, for which we have a separate subforum for each tier of staff, including the support operators.

So that’s pretty much how the policies and objectives of SwiftIRC are shaped. Although the hierarchical structure of SwiftIRC isn’t overly conducive to large changes, we feel that they are usually in the best interests of the users as the discussions are infinitely more thorough than any discussion that could be achieved by a single, or even handful of individuals.

Awong

Cower, mortals! Welcome to SwiftBlog!

Long has it been felt that the users of SwiftIRC have deserved far more information about the going-ons of SwiftIRC than has been otherwise available. This is beneficial to both the users and the administration as for the users, decisions that concern their network concern them. For the administration, the aim has never been to sit upon a pedestal, but rather to openly interact with the users of SwiftIRC so that their decisions reflect the best interests of as many users as possible. At the same time, change is being openly embraced as we seek to refine the services and support offered to our users to cater for as many users as possible in as fair and transparent a means as possible.

To serve these dual aims, the SwiftBlog has been set up with the hopes that users will be able to voice their opinions constructively at best, or at the very least have access to an update of the latest dastardly plans going on behind the veiled curtains of the administration. With any luck, these posts will hopefully reveal the rationale behind our decisions as well as our hopes for the various plans we have. As such, I openly encourage all users to take part in this project and share their thoughts as each post is brought out, offering their constructive feedback where possible.

Watch this space, and I hope to see you all around the network, so give me a buzz if I’m about!

Awong