]> jfr.im git - irc/freenode/web-7.0.git/blob - content/news/2016-02-19-recent-events-and-future-changes.md
git pushMerge branch 'pages-fix' of github.com:freenode/web-7.0 into
[irc/freenode/web-7.0.git] / content / news / 2016-02-19-recent-events-and-future-changes.md
1 author: spb
2 date: 2016-02-19 13:11:54+00:00
3 slug: recent-events-and-future-changes
4 title: Recent Events and Future Changes
5 ---
6 Many of you have been asking questions about the recent rash of high-profile
7 staff resignations, and we feel we owe you all both an explanation and an
8 apology.
9
10 First, the explanation: in short, it's become clear over recent months that
11 freenode has lost its way somewhat, when compared to the ideals and goals that
12 we were created with. A growing sense of disillusionment amongst those of us who
13 remember the olden days, when we were far more friendly, approachable and
14 engaged in the communities we were set up to serve, has recently come to a head.
15 Naturally, when some of these people decided they could no longer continue with
16 the way things had become, it was time for us to think long and hard about what
17 had gone wrong and what we should do about it.
18
19 And so, to the apology. We're uncomfortably aware that freenode was set up with
20 the strong idea that the projects and communities which use it should be the
21 first, and often the only, priority. We've lost sight of that, and we're sorry.
22 We'll be doing our best, from now on, to get back in touch with the ideals that
23 made freenode such a great place.
24
25 This won't be easy for us, as we've got years of bad habits to break, but
26 hopefully you should start seeing some improvements in the coming months. If you
27 see anything that we're not doing that would help your communities, please tell
28 us and we'll try our best to find a way to make it happen. You might see a bit
29 of chaos or inconsistency while we try to find our way around again, but please
30 try to bear with us and we hope you'll see things get better in time.
31
32 And finally, because we're conscious that a lack of clarity around our
33 leadership structure has not helped matters, we've decided to set out
34 unambiguously how the staff management structure will work from now on. Our
35 activities and operations will be split roughly into four areas, each with a
36 designated lead.
37
38
39
40
41 * mist is head of staff, and in charge of day to day network operations and general staff issues.
42
43
44 * kloeri is head of infrastructure, in charge of making sure that the network continues to run in a usable fashion and that we have the right hardware and server platforms in place to provide the services we want to.
45
46
47 * spb is head of development, in charge of the software platforms that we use to run the network.
48
49
50 * christel is head of projects and communities, and also the overall project lead in charge of the other three heads. She'll be trying to make sure that we get back the levels of engagement that we once had with the projects we're here to serve.
51
52
53 These four, together, will take any decisions that affect the future direction
54 of freenode. While they each have their own area of focus, feel free to contact
55 any of us about any issues you may have -- we try to keep an open (virtual) door
56 policy.