|Re: IRC provider: Roadmap [message #600745 is a reply to message #600739]
||Tue, 14 February 2006 06:16
| Scott Lewis
Registered: July 2009
> There has been some activity lately on including the IRC provider into
> ECF CVS repo as a project. I had some poke around with the IRC provider
> code and had some Q's :
> a) Is it planned to remove the current dependency on an external IRC lib?
Probably not. Rather given that the IRClib is licensed (dual) under
apache 2 we'll try to get it approved for inclusion into EPL-licensed
code (ECF project code). Since apache 2 is compatible with EPL this
would be likely doable.
OTOH, if someone would like to replace the dependency on IRClib with new
code that would be terrific. Even better if they are willing to
contribute that code back to ECF and distribute under EPL. The use of
IRC lib was for expediency...no pride of ownership there (although as
far as the usage has gone it's worked quite well).
> b) Is anyone actively involved with IRC provider code. I would be
> interested but not sure who to register my interest with.
What do you mean actively involved? I'm (Scott) the author of the IRC
provider code, but I haven't been able to work with it for several
releases significantly...just because I've been doing other (ECF) things.
> c) What's the roadmap for IRC provider?
Roadmap? Just kidding. I would like to see the IRC provider be
completed, as it's currently leaving out a number of operations. It's
sort of on the back burner for me right now, however, because of desire
to get datashare, fileshare, and a new VOIP 'call' API in place...as
well as solidify some of the other providers...like the JMS provider and
possibly the Yahoo provider.
But I would very much like to see a sub-project formed to move the IRC
provider forward. If there are people interested in such a sub-project
then let's put together a contributor team from this community and make
it happen. I can't, however, commit much of my own time to work on the
IRC provider specifically (just because I've got EclipseCon to prepare
for, the call API, etc., etc).
Powered by FUDForum
. Page generated in 0.03077 seconds