[lwip-users] Re: [lwip] The future of lwIP

[John C. Toman]

Hi Adam,

You can count me in as a collaborative developer. My lwIP DNS client 
code, written from scratch, is nearly complete and I should be releasing 
it in a week or so.

I'm going to be working on other protocols such as SMTP, POP3, SNTP and 
an HTTP client which will work with lwIP, and which I will release back 
into the community, in the very near future. I'm also interested in 
developing/contributing/helping with RFC1948-based TCP ISS code to help 
avoid that security issue. And I'm also interested in reducing the code 
size / execution time for little endian architectures in particular 
(without impacting the big endian architectures, of course), and have 
some ideas as to how to proceed along those lines.

By the way, I like what's been done with etharp in the latest CVS stuff. 
Much better.

Will the license stay BSD-style? I am certainly interested in it 
remaining so.

Regards,

John

Adam Dunkels wrote:

>Hi all!
>
>After reading through some 160 mails and sending out nearly 30 myself,
>I'm feeling pretty red-eyed right now 8-)
>
>As you all have noticed the last few months, my lwIP-time has been way
>to small. I feel really bad about the fact that there are several
>patches and bugfixes that haven't been applied and that the 0.6 version
>should have been put out months ago.
>
>Therefore, I have decided to put up lwIP on the open source development
>portal sourceforge.net. This will make it possible for anyone to follow
>the development with anonymous read-only CVS. But most importantly: this
>will open up the CVS to other developers besides me.
>
>I have opened an lwIP account on sourceforge and will be uploading the
>homepage to http://lwip.sourceforge.net/ soon. This will be the new
>official URL for lwIP.
>
>I am currently reading through the documentation from sourceforge on how
>to install the CVS account there and will commit the current lwIP
>development version.
>
>This will also mean that the lwIP mailing list will be moved over to
>sourceforge. I'm not sure that it is possible to move everyone from this
>list to the new list automatically, but I'll see what can be done.
>
>So, who would be interested in becoming a collaborative developer with
>CVS write access? I am not sure about the way lwIP ought to be managed;
>I guess we'll see how many that are interested in joining in and work it
>out from there. What do you think?
>
>/adam
>  
>




[This message was sent through the lwip discussion list.]