While we got permission, I didn't grab the code. See - the whole problem (and it isn't just MailDaemon) is that someone has to keep those source trees in sync. Grabbing new source and updating ours. Pros: We have source. It can't disappear out from under us We look more finished and more inspiring. Cons: Someone has to build it, maintain it and update it Any changes that we make have to get ported back to the "main" code and get integrated. We have this issue with Mail Daemon, NewOS and more. If anyone has any great ideas on how we can manage this, let me know. >Hey fearless leader (Michael that is)... > >Did you ever get hold of the Mail Daemon code from Nathan? > >This might be of some real use to the net team. Once you get it, you >could find a place for it in the CVS repos _or_ I could create a spot >for it somewhere on the web site (it wouldn't have to be a public URL) > >[snip...] >> >>Could it be of interrest to contact former beos coders who did network >>related stuff to ask them if they would be interrested to join our >team or >>the OpenBeOS project ? >[snip...] >> >> Best Regards, >> >> Emmanuel > > >