Richard:
Interesting. So, you would say that it definitely would be a replacement for the telnetd bundle at oscar-osgi.sf.net then? Sounds like it.
I think it would be missing the shell that provides the OSGi console part. However, it would be the better codebase to start from (because I have fixed, extended and worked on it for a while longer; and we have it in use for a while at Coalevo).
Sounds good. Well, if you are planning on developing this on your end, then it is not unreasonable to just let you go about your business and do it (i.e., the bundle portion of your work doesn't have to be done here). However, if there is sufficient interest in moving the bundle aspects here as a subproject, then it could also be considered.
I am developing this mainly for a community platform I am working on (that would be Coalevo), where we are trying to preserve a shell access similar to old style BBS systems.
For your needs, I suppose that there is currently too much functionality and too many additional dependencies, so maybe we should make a split approach and coordinate it: 1) a base bundle of telnetd-osgi, providing all functionality that the felix project would be interested in
2) a shell bundle that provides the OSGi console for felix.1 could live either at felix (Apache) or at Coalevo (I prefer the legal backup for the license); in both cases it will be released under Apache 2 License. I would need input to know the requirements, and if we want to go Maven, some help (haven't worked much with it yet).
2 should live at felix (Apache) and may be derived from the old codebase. If you point me to a codebase I could get started from, I can invest some time to port and make it working with the newer telnetd codebase (i.e. 1).
I think that your group/committee should decide if you want to get 1 and 2 or just 2 into the felix project. Either way I'd be doing as much as I can; it's a long term interest (because the online community I am a part of since years will switch soon, and we will continue to use the codebase in a production environment; all OSGi btw.).
Regards, Dieter
smime.p7s
Description: S/MIME cryptographic signature
