/usr/share/doc/dancer-ircd/dancer-oper-guide.html/philosophy.htm is in dancer-ircd-doc 1.0.36-8ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Freenode Philosophy</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="Operators guide for the dancer IRC server"
HREF="index.htm"><LINK
REL="UP"
TITLE="Introduction"
HREF="intro.htm"><LINK
REL="PREVIOUS"
TITLE="Introduction"
HREF="intro.htm"><LINK
REL="NEXT"
TITLE="Dancer operators"
HREF="newopers.htm"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>Operators guide for the dancer IRC server</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="intro.htm"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 1. Introduction</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="newopers.htm"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="PHILOSOPHY"
>1.2. Freenode Philosophy</A
></H1
><P
> The dancer IRC server was written for the <A
HREF="http://www.freenode.net"
TARGET="_top"
>Freenode Network</A
>,
and designed with FN philosophy in mind. As such, it may have features which are at odds with other networks
and their philosophies.
</P
><P
> The Freenode Net philosophy has several components. FN exists to
provide interactive services to projects and groups involved with
"Open Source, Open Technology and Open Information." We work to provide
an interaction environment in which free software community members can
improve their skills in the areas of communication and coordination of
effort. We also try to provide an environment which serves to introduce
new participants to the free software community.
</P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN31"
>1.2.1. Principals</A
></H2
><P
> The basic principles of FN are:
</P
><P
></P
><UL
><LI
><P
> Community members benefit from better access to each other. Putting a
number of projects in close proximity in an interactive environment
creates linkages between developers and projects, and helps community
members take better advantage of each other's work.
</P
></LI
><LI
><P
> Communication and coordination skills are important to community projects.
Free software and open source work because the paradigm works. Developers
and community members are not unusually gifted at project coordination and
communication. But improving those skills can make projects work better.
</P
></LI
><LI
><P
> Friendly interaction is more efficient than flaming. Calm, relaxed discourse
without angry contention provides for better exchange of information. Flaming
produces situations in which the listener must contend with the state of
his or her emotions at least as much as with the comprehension of a speaker's comments.
</P
></LI
><LI
><P
> Open source developers are self-driven. No one guarantees your work will
be used, but only you decide whether a project is worth doing. There is no
single right approach to any coding or support problem, and friendly
competition is a fundamentally good thing.
</P
></LI
><LI
><P
> The free software community is small, and needs to grow. Many valuable
projects chronically lack skilled, motivated developers with time to devote
to them. Our potential developer base includes programmers in all fields and
disciplines, and both students and working professionals. Our potential user
base includes individuals and organizations standing to benefit from software
projects we successfully pursue. The community must continue to grow.
</P
></LI
><LI
><P
> Free software is about the software. Free software and open source were not
born in the recent venture-capital, pre-IPO environment. Our roots are in
coders coding software for the benefit of themselves and their organizations,
and for the pleasure of producing quality work. It is completely legitimate to
profit monetarily from coding and supporting free and open applications.
Corporate sponsors of open source projects are welcome on FN. It's time,
though, for the community to get back to its roots.
</P
></LI
></UL
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN47"
>1.2.2. Practicalities</A
></H2
><P
> The FN IRC network provides a controlled environment in which open projects can
communicate between developers and users. To this end, FN is centrally maintained,
and operators are expected to try and resolve situations without actually exercising
their power when possible. They are also expected to stay out of channel politics and
arguments, so don't bother asking them to intervene if you disagree with the people
who run a channel. They won't.
</P
><P
> FN runs a full services implementation, which allows nicks and channels
to be registered and protected by the server, thusly making channel takeovers largely
impossible, while maintaining a consistant interface for channels to be managed.
</P
><P
> If an individual has somehow gained ops on a channel, then the channel founder, or
people with an appropriate level of access, can handle it themselves with chanserv;
refer to the dancer users guide for details. If somebody has managed to take
founder access (by guessing the founder password, or whatever), then the original
founder should come to channel #freenode ASAP so that the situation can be resolved.
</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="intro.htm"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.htm"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="newopers.htm"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Introduction</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="intro.htm"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Dancer operators</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
|