1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 3.2//EN">
4 <TITLE> [IRCServices Coding] Services
5
6 <LINK REL=
"Index" HREF=
"index.html" >
7 <LINK REL=
"made" HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%205&In-Reply-To=">
8 <META NAME=
"robots" CONTENT=
"index,nofollow">
9 <META http-equiv=
"Content-Type" content=
"text/html; charset=us-ascii">
10 <LINK REL=
"Previous" HREF=
"000015.html">
11 <LINK REL=
"Next" HREF=
"000019.html">
13 <BODY BGCOLOR=
"#ffffff">
14 <H1>[IRCServices Coding] Services
5</H1>
16 <A HREF=
"mailto:ircservices-coding%40ircservices.za.net?Subject=%5BIRCServices%20Coding%5D%20Services%205&In-Reply-To="
17 TITLE=
"[IRCServices Coding] Services 5">achurch at achurch.org
19 <I>Sat Dec
15 00:
02:
16 PST
2001</I>
21 <LI>Previous message:
<A HREF=
"000015.html">[IRCServices Coding] Services
5
23 <LI>Next message:
<A HREF=
"000019.html">[IRCServices Coding] Version
5 (feature request)
25 <LI> <B>Messages sorted by:
</B>
26 <a href=
"date.html#18">[ date ]
</a>
27 <a href=
"thread.html#18">[ thread ]
</a>
28 <a href=
"subject.html#18">[ subject ]
</a>
29 <a href=
"author.html#18">[ author ]
</a>
34 <PRE>><i>I hope other people don't know so much about ircservices as you know about
35 </I>><i>sourceforge. You probably wouldn't like to see your project named as
36 </I>><i>piece-of-shit-formerly-known-as-irc-services.
38 Everyone's entitled to their opinions, and I suspect someone with that
39 opinion wouldn't be using it in the first place so I'd never have to deal
43 <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org
</A>
44 <A HREF=
"http://achurch.org/">http://achurch.org/
</A>
46 >><i>3) Not really, mostly because it would be a pain to set up and manage.
47 </I>>><i>I may set something up once
5.0 has gone stable, but until then it's just
48 </I>>><i>too much to deal with. And I want absolutely nothing to do with the
49 </I>>><i>piece-of-shit-formerly-known-as-Sourceforge.
52 </I>><i><A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">Lamego at PTlink.net
</A>
55 </I>><i>-----Original Message-----
56 </I>><i>From:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org
</A> [mailto:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org
</A>]
57 </I>><i>Sent:
14 December
2001 09:
44
58 </I>><i>To:
<A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">ircservices-coding at ircservices.za.net
</A>
59 </I>><i>Subject: Re: [IRCServices Coding] Services
5
62 </I>><i> Looks like this didn't get through the first time, so:
64 </I>><i>1) No, because I have no clue how many bugs will turn up ;) At this point
65 </I>><i>I'm tempted to say beta in February and stable release in April or so, but
66 </I>><i>I have absolutely no basis for saying that, so don't quote me on it.
68 </I>><i>2) The notice is intended more for lamers who say
"ooh it's version
5!
" and
69 </I>><i>rush to download it. Feel free to use it on your production network, as
70 </I>><i>long as you take responsibility for any problems it causes. There aren't
71 </I>><i>too many major issues right now that I can think of, but it's the ones I
72 </I>><i>haven't found yet that worry me more. (One major issue I do know of is
73 </I>><i>that rehashing modules.conf doesn't work yet and could easily break
76 </I>><i>3) Not really, mostly because it would be a pain to set up and manage.
77 </I>><i>I may set something up once
5.0 has gone stable, but until then it's just
78 </I>><i>too much to deal with. And I want absolutely nothing to do with the
79 </I>><i>piece-of-shit-formerly-known-as-Sourceforge.
81 </I>><i>4) For autojoin in particular, it was pointed out to me that not everyone
82 </I>><i>always accesses IRC from the same computer, which would make client
83 </I>><i>settings irrelevant. In general, though, with the module system, I'm a bit
84 </I>><i>more lenient in terms of what I'll let in, since you can just disable
85 </I>><i>modules you don't need. (And the reason for almost everything being
86 </I>><i>enabled in the default config is so you'll all test them for me. ;) Some
87 </I>><i>will probably be disabled in beta/final releases.)
89 </I>><i> --Andrew Church
90 </I>><i> <A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">achurch at achurch.org
</A>
91 </I>><i> <A HREF=
"http://achurch.org/">http://achurch.org/
</A>
93 </I>>><i>Firstly, thanks to Andrew for releasing the alpha version. Hopefully he
95 </I>>><i>not feel that he has to later remove this opportunity.
97 </I>>><i>A few early questions that maybe Andrew or the Alpha team might be able to
98 </I>>><i>comment on.
100 </I>>><i>1) Do we have any idea on time scale for development beyond alpha? I
101 </I>>><i>understand that it is a difficult question to answer given RL committments
102 </I>>><i>but based on work so far and this extended open test hopefully highlighting
103 </I>>><i>major issues quite quickly, might make it easier to provide an estimate.
105 </I>>><i>2) Despite the warning not to run the alpha on a production network, it
107 </I>>><i>seem to be the best place to run it since it will give a much more
109 </I>>><i>test of the code. It is also very tempting to upgrade :) To this end, are
110 </I>>><i>there specific known issues at this time with the current build that would
111 </I>>><i>make it completely impractical to run on a small production network? The
112 </I>>><i>"knownbugs
" file does not seem to have anything specific to Services
5 and
113 </I>>><i>nothing serious mentioned either way but those who have already had chance
114 </I>>><i>to play with Services
5 may have a good idea of things that would make it
115 </I>>><i>unsuitable for risking in a production environment.
117 </I>>><i>3) At present we seem to be restricted to the mailing list for bug
119 </I>>><i>and discussion which makes the process qyute closed. Has there been any
120 </I>>><i>thought given to providing some kind of online tracking system which would
121 </I>>><i>both show what bugs are currently known and their status? Maybe something
123 </I>>><i>sourceforge or similar system would suffice.
125 </I>>><i>4) I was wondering about the reasons for AJOIN being included in Services
127 </I>>><i>It seems to place an overhead on NickServ that has been handled by many IRC
128 </I>>><i>clients for a number of years. Even clients which do not specifically
129 </I>>><i>support it, but that implement perform can easily provide AJOIN
130 </I>>><i>functionality. Any client supporting scripting could easily manage an AJOIN
131 </I>>><i>list. A number of clients support dynamic AJOIN lists by offering to
132 </I>>><i>remember hannels that a user uses on a regular basis.
134 </I>>><i>Since part of the ethos behind IRC Services development is not to perform
135 </I>>><i>tasks that really belong in IRCd or in clients or could be scripted, it
136 </I>>><i>seems odd that firstly this system has been implemented and secondly it is
137 </I>>><i>enabled in a default configuration.
139 </I>>><i>Is there something specific that I am missing about this services managed
140 </I>>><i>auto join list which makes it preferable to the existing client code which
141 </I>>><i>already performs this task?
144 </I>>><i>Anyway, back to play around with the source some more.
148 </I>>><i>------------------------------------------------------------------
149 </I>>><i>To unsubscribe or change your subscription options, visit:
150 </I>>><i><A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding
</A>
151 </I>><i>------------------------------------------------------------------
152 </I>><i>To unsubscribe or change your subscription options, visit:
153 </I>><i><A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding
</A>
154 </I>><i>------------------------------------------------------------------
155 </I>><i>To unsubscribe or change your subscription options, visit:
156 </I>><i><A HREF=
"http://www.ircservices.za.net/mailman/listinfo/ircservices-coding">http://www.ircservices.za.net/mailman/listinfo/ircservices-coding
</A>
164 <LI>Previous message:
<A HREF=
"000015.html">[IRCServices Coding] Services
5
166 <LI>Next message:
<A HREF=
"000019.html">[IRCServices Coding] Version
5 (feature request)
168 <LI> <B>Messages sorted by:
</B>
169 <a href=
"date.html#18">[ date ]
</a>
170 <a href=
"thread.html#18">[ thread ]
</a>
171 <a href=
"subject.html#18">[ subject ]
</a>
172 <a href=
"author.html#18">[ author ]
</a>
projects / irc.git / blob