I have been using the FTP server for some time. This is great news!!
On Jan 2, 2008 7:27 AM, Niklas Gustavsson <[EMAIL PROTECTED]> wrote: > Hi > > The MINA PMC has voted for accepting FtpServer from the Apache Incubator > as a subproject of MINA. For me, as a commiter on the FtpServer project > this is great. We've been using MINA as our main network implementation > for some time and I'm a big fan of the project. MINA is the perfect home > for FtpServer. > > FtpServer is a small project and I'm the only non-MINA commiter that > will be moving with the project. FtpServer has been in the Incubator for > quite some time and has it's roots in the now defuncted Apache Avalon > project. This still shows in some places and I'm currently working on a > major refactoring of our code. As part of this, we just voted on > dropping our Java 1.4 support, which means that we can loose our support > for blocking IO (this was previously needed as NIO SSL came in Java > 1.5). This lets us use MINA full-throttle which is wonderful. I expect > our code to be significantly easier and more flexible in the near > future. And I'm hoping for your input on how we should go ahead, I'm > very open for feedback and suggestions :-) > > Now, moving the project over to MINA means that we need to make some > decisions. > > 1. Migrate SVN: FtpServer is composed of a set of components, but have > been kept within a single trunk/tags structure. Where would be the > appropriate place to move this within the MINA SVN structure? As I > imagining we would like to release MINA and subprojects like FtpServer > separately, I'm thinking it should not go in the current trunk. How > about creating a new "subprojects" or "applications" directory on the > same level as sandbox? > > 2. Mailing lists: FtpServer currently has a dev list with a fairly low > traffic with on average one mail per day. Should we keep this separate > from the main MINA dev list or merge them? Since I would like input from > the entire MINA community on the work going on with FtpServer, I would > prefer using the main MINA dev list. That means, scrapping the current > FtpServer list. A major drawback with this is that users only interested > in FtpServer might get overwhelmed by the traffic on the MINA dev list. > Still, I think its the best option. > > 3. Confluence: FtpServer, like MINA, uses Confluence to generate its > site. My suggestion would be to move over our pages to the MINA space > and then delete our old with a .htaccess redirect the sends users to the > new pages. > > 4. JIRA: FtpServer, like MINA, uses JIRA for maintaining all it's > issues. I would suggest creating a new component in the MINA JIRA > project and moving over our issues. > > Again, it's great to be here. I hope we'll be a great addition to the > MINA community. > > /niklas > > -- -------------------------------- Talent hits a target no one else can hit; Genius hits a target no one else can see.
