[irc.git] / software / RELEASES / ircservices / achurch.org / services / lists / ircservices / 2007 / 005274.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
 <HEAD>
   <TITLE> [IRCServices] Services 5.1pre0 released
   </TITLE>
   <LINK REL="Index" HREF="index.html" >
   <LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%205.1pre0%20released&In-Reply-To=463d8f4b.23151%40msgid.achurch.org">
   <META NAME="robots" CONTENT="index,nofollow">
   <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
   <LINK REL="Previous"  HREF="005262.html">
   <LINK REL="Next"  HREF="005275.html">
 </HEAD>
 <BODY BGCOLOR="#ffffff">
   <H1>[IRCServices] Services 5.1pre0 released</H1>
    <B>Trevor Talbot</B> 
    <A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%205.1pre0%20released&In-Reply-To=463d8f4b.23151%40msgid.achurch.org"
       TITLE="[IRCServices] Services 5.1pre0 released">quension at mac.com
       </A><BR>
    <I>Sun May 13 12:57:01 PDT 2007</I>
    <P><UL>
        <LI>Previous message: <A HREF="005262.html">[IRCServices] Services 5.1pre0 released
</A></li>
        <LI>Next message: <A HREF="005275.html">[IRCServices] Services 5.1pre0 released
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#5274">[ date ]</a>
              <a href="thread.html#5274">[ thread ]</a>
              <a href="subject.html#5274">[ subject ]</a>
              <a href="author.html#5274">[ author ]</a>
         </LI>
       </UL>
    <HR>  
<!--beginarticle-->
<PRE>On May 6, 2007, at 1:18 AM, Andrew Church wrote:

&gt;<i>      The second, and more important, reason for posting the 
</I>&gt;<i> announcement to this list is that I intend version 5.1 to be the last 
</I>&gt;<i> version of IRC Services, at least under my care.  While I don't 
</I>&gt;<i> consider Services &quot;complete&quot;--software development is a neverending 
</I>&gt;<i> task, and in any case users' needs change over time--I do believe that 
</I>&gt;<i> it's time for me to move on to other things.  In fact, I already 
</I>&gt;<i> devote a fair amount of my time outside of work to other software 
</I>&gt;<i> development projects (such as the audio/video tool &quot;transcode&quot;, for 
</I>&gt;<i> those who are familiar with it), and I have other hobbies which I 
</I>&gt;<i> haven't been able to pursue as much as I'd like.  I've also found that 
</I>&gt;<i> I personally use IRC very infrequently these days, and that has 
</I>&gt;<i> inevitably lessened my interest in continuing Services development as 
</I>&gt;<i> well.
</I>
&gt;<i>      I realize that this &quot;end-of-life&quot; announcement for Services may 
</I>&gt;<i> come as a surprise to some, and for that I apologize.  As I mentioned 
</I>&gt;<i> earlier, I will continue to support Services for some time to come (my 
</I>&gt;<i> current thought is for two to three years after the release of 5.1.0); 
</I>&gt;<i> however, I did want to provide advance warning of my future 
</I>&gt;<i> intentions.  Thank you all for your support over the years.
</I>
Even though it's not &quot;over&quot;, I wanted to say a couple things.

First, thank you for all the work you've done during the last several 
years.  Besides IRC Services itself, most of the NickServ/ChanServ 
-style services packages in use today trace their origins to your 
software in one form or another.  Inspiring that much development is no 
small accomplishment.  I've certainly customized IRC Services for 
specific uses in the past.  We've also had discussions about irc3, 
which has inspired me personally to think about IRC in a slightly 
different way for several years now.  I've found that line of thought 
to be quite intriguing, and perhaps it will lead to me to create 
something useful later on.

And second, thank you for having an &quot;exit plan&quot;.  Far too many projects 
are simply abandoned by their authors and maintainers.  While obviously 
software such as this cannot take priority over other life concerns, 
it's great to see someone recognize they will be unable to continue 
ahead of time, and plan to make that eventuality as painless as 
possible for those who use it.

-- Quension

</PRE>


<!--endarticle-->
    <HR>
    <P><UL>
        <!--threads-->
	<LI>Previous message: <A HREF="005262.html">[IRCServices] Services 5.1pre0 released
</A></li>
	<LI>Next message: <A HREF="005275.html">[IRCServices] Services 5.1pre0 released
</A></li>
         <LI> <B>Messages sorted by:</B> 
              <a href="date.html#5274">[ date ]</a>
              <a href="thread.html#5274">[ thread ]</a>
              <a href="subject.html#5274">[ subject ]</a>
              <a href="author.html#5274">[ author ]</a>
         </LI>
       </UL>

</body></html>
Commit	Line	Data
3bd189cb JR	1	<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
	2	<HTML>
	3	<HEAD>
	4	<TITLE> [IRCServices] Services 5.1pre0 released
	5	</TITLE>
	6	<LINK REL="Index" HREF="index.html" >
	7	<LINK REL="made" HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%205.1pre0%20released&In-Reply-To=463d8f4b.23151%40msgid.achurch.org">
	8	<META NAME="robots" CONTENT="index,nofollow">
	9	<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
	10	<LINK REL="Previous" HREF="005262.html">
	11	<LINK REL="Next" HREF="005275.html">
	12	</HEAD>
	13	<BODY BGCOLOR="#ffffff">
	14	<H1>[IRCServices] Services 5.1pre0 released</H1>
	15	<B>Trevor Talbot</B>
	16	<A HREF="mailto:ircservices%40ircservices.za.net?Subject=%5BIRCServices%5D%20Services%205.1pre0%20released&In-Reply-To=463d8f4b.23151%40msgid.achurch.org"
	17	TITLE="[IRCServices] Services 5.1pre0 released">quension at mac.com
	18	</A><BR>
	19	<I>Sun May 13 12:57:01 PDT 2007</I>
	20	<P><UL>
	21	<LI>Previous message: <A HREF="005262.html">[IRCServices] Services 5.1pre0 released
	22	</A></li>
	23	<LI>Next message: <A HREF="005275.html">[IRCServices] Services 5.1pre0 released
	24	</A></li>
	25	<LI> <B>Messages sorted by:</B>
	26	<a href="date.html#5274">[ date ]</a>
	27	<a href="thread.html#5274">[ thread ]</a>
	28	<a href="subject.html#5274">[ subject ]</a>
	29	<a href="author.html#5274">[ author ]</a>
	30	</LI>
	31	</UL>
	32	<HR>
	33	<!--beginarticle-->
	34	<PRE>On May 6, 2007, at 1:18 AM, Andrew Church wrote:
	35
	36	><i> The second, and more important, reason for posting the
	37	</I>><i> announcement to this list is that I intend version 5.1 to be the last
	38	</I>><i> version of IRC Services, at least under my care. While I don't
	39	</I>><i> consider Services "complete"--software development is a neverending
	40	</I>><i> task, and in any case users' needs change over time--I do believe that
	41	</I>><i> it's time for me to move on to other things. In fact, I already
	42	</I>><i> devote a fair amount of my time outside of work to other software
	43	</I>><i> development projects (such as the audio/video tool "transcode", for
	44	</I>><i> those who are familiar with it), and I have other hobbies which I
	45	</I>><i> haven't been able to pursue as much as I'd like. I've also found that
	46	</I>><i> I personally use IRC very infrequently these days, and that has
	47	</I>><i> inevitably lessened my interest in continuing Services development as
	48	</I>><i> well.
	49	</I>
	50	><i> I realize that this "end-of-life" announcement for Services may
	51	</I>><i> come as a surprise to some, and for that I apologize. As I mentioned
	52	</I>><i> earlier, I will continue to support Services for some time to come (my
	53	</I>><i> current thought is for two to three years after the release of 5.1.0);
	54	</I>><i> however, I did want to provide advance warning of my future
	55	</I>><i> intentions. Thank you all for your support over the years.
	56	</I>
	57	Even though it's not "over", I wanted to say a couple things.
	58
	59	First, thank you for all the work you've done during the last several
	60	years. Besides IRC Services itself, most of the NickServ/ChanServ
	61	-style services packages in use today trace their origins to your
	62	software in one form or another. Inspiring that much development is no
	63	small accomplishment. I've certainly customized IRC Services for
	64	specific uses in the past. We've also had discussions about irc3,
65	which has inspired me personally to think about IRC in a slightly
66	different way for several years now. I've found that line of thought
67	to be quite intriguing, and perhaps it will lead to me to create
68	something useful later on.
69
70	And second, thank you for having an "exit plan". Far too many projects
71	are simply abandoned by their authors and maintainers. While obviously
72	software such as this cannot take priority over other life concerns,
73	it's great to see someone recognize they will be unable to continue
74	ahead of time, and plan to make that eventuality as painless as
75	possible for those who use it.
76
77	-- Quension
78
79	</PRE>
80
81
82	<!--endarticle-->
83	<HR>
84	<P><UL>
85	<!--threads-->
86	<LI>Previous message: <A HREF="005262.html">[IRCServices] Services 5.1pre0 released
87	</A></li>
88	<LI>Next message: <A HREF="005275.html">[IRCServices] Services 5.1pre0 released
89	</A></li>
90	<LI> <B>Messages sorted by:</B>
91	<a href="date.html#5274">[ date ]</a>
92	<a href="thread.html#5274">[ thread ]</a>
93	<a href="subject.html#5274">[ subject ]</a>
94	<a href="author.html#5274">[ author ]</a>
95	</LI>
96	</UL>
97
98	</body></html>