I think contrib is the place to go - the idea behind main and contrib is, that bundles in main are the ones we as a community are able to support for a long time - so I guess this boils down to the point that we have more than one committer working on this stuff.
Not a very strict rule, but I think new stuff should always go to contrib first - we can easily move it later without requiring to change packages or project coordinates etc. Carsten 2013/1/21 Ian Boston <[email protected]>: > Hi, > The code looks complete and very compact. > +1 to move it to the contrib area. > +1 to move to main area if a simple test to spin up the bundle can be > added. I started to do something generic in common to make that easier > a while back. > Ian > > > On 21 January 2013 10:26, Felix Meschberger <[email protected]> wrote: >> Hi all, >> >> Over the weekend I have created an FTP Server for Sling [1]. It uses Apache >> Mina FTP Server internally exposing the Sling Resource Tree as the file >> system. As such, it just uses the Resource API. >> >> Except for the User Management part: Here the Jackrabbit User Management is >> used. In a plain installation with the Jackrabbit Server bundle, this works >> great. >> >> I think we could move that from my white board [1] to either the contrib >> folder or the main bundle area. >> >> WDYT ? >> >> How to use: Compile and deploy and then create configuration -- The FTP >> Server requires configuration to be active. Default values for users are in >> the configuration. Some values (like general ability to login, throughput) >> can be configured on a per-user basis. >> >> Regards >> Felix >> >> [1] http://svn.apache.org/repos/asf/sling/whiteboard/fmeschbe/ftpserver -- Carsten Ziegeler [email protected]
