FTPServer future...

[Emmanuel Lécharny <el...@gmail.com>]

Hi guys,

I'd like to ask your opinion about what we should do with the FtpServer
project.

There is little activity around it, and in the last 3 years, I was the
only one committig patches and code to the source base.

OTOH, I know this project is being used, as  we have bug reports
periodically.

At this point, I'd like to know what you think we should o about it :

o move it to attic
o keep going and trying to find new committers
o having some existing committers more actively taking care of the code base

Ideally speaking, the third solution is the best, the second is ok too,
but requires some people to step in.

I don't have any time to investigate bug reports that are related to the
FTP functionality (I pretty much know nothing about FTP), but I can
spend time applying patches, fixing obvious bugs, or cutting releases.
So, what's your opinion ?

Many thanks !

PS: if any user is interested in participating in the project, we can
easily vote them in as committer : this is an open source project, those
who want to be part of it are very welcome.

-- 
Emmanuel Lecharny

Symas.com
directory.apache.org

Re: FTPServer future...

[Jonathan Valliere <jo...@emoten.com>]

FTP is just another from of HTTP; once I figure out how everything is
organized, it should be easy.  Nothing like that LDAP code.

On Wed, Apr 18, 2018 at 11:44 AM, Jonathan Valliere <jon.valliere@emoten.com
> wrote:

> Since it is basically Mina I/O, I can help maintain FTP Server.  It is a
> lot more “friendly” looking than the SSHD project.  Just need to get
> Eclipse to stop giving me Maven errors when loading the project.
>
> On Wed, Apr 18, 2018 at 11:35 AM, Guillaume Nodet <gn...@apache.org>
> wrote:
>
>> 2018-04-18 10:28 GMT+02:00 Emmanuel Lécharny <el...@gmail.com>:
>>
>> > Hi guys,
>> >
>> > I'd like to ask your opinion about what we should do with the FtpServer
>> > project.
>> >
>> > There is little activity around it, and in the last 3 years, I was the
>> > only one committig patches and code to the source base.
>> >
>> > OTOH, I know this project is being used, as  we have bug reports
>> > periodically.
>> >
>> > At this point, I'd like to know what you think we should o about it :
>> >
>> > o move it to attic
>> >
>>
>> I think the attic does not bring much to the community.  It should already
>> be pretty obvious that it's not actively developped.
>> The attic is imho interesting for a whole project, because the PMC is not
>> capable of overseeing the project anymore.
>> For a subproject, it does not bring anything
>>
>>
>> > o keep going and trying to find new committers
>> >
>>
>> Definitely, if people are interested in contributing, we should invite
>> them
>> as committers with a very low entry-bar.
>>
>>
>> > o having some existing committers more actively taking care of the code
>> > base
>> >
>> > Ideally speaking, the third solution is the best, the second is ok too,
>> > but requires some people to step in.
>> >
>> > I don't have any time to investigate bug reports that are related to the
>> > FTP functionality (I pretty much know nothing about FTP), but I can
>> > spend time applying patches, fixing obvious bugs, or cutting releases.
>> >
>>
>> Same here...
>>
>>
>> > So, what's your opinion ?
>>
>>
>> I'm not actively tracking JIRA issues.  I wonder if there would be a
>> better
>> way of applying patches.
>> Maybe github PR could be automatically validated (i.e. run a full build on
>> CI) and could be made more visible somehow ?
>> That way, if we know they build passes, a quick check could be sufficient
>> to merge the PR.
>>
>>
>> >
>> > Many thanks !
>> >
>> > PS: if any user is interested in participating in the project, we can
>> > easily vote them in as committer : this is an open source project, those
>> > who want to be part of it are very welcome.
>> >
>> > --
>> > Emmanuel Lecharny
>> >
>> > Symas.com
>> > directory.apache.org
>> >
>> >
>>
>>
>> --
>> ------------------------
>> Guillaume Nodet
>>
>
>

Re: FTPServer future...

[Jonathan Valliere <jo...@emoten.com>]

Since it is basically Mina I/O, I can help maintain FTP Server.  It is a
lot more “friendly” looking than the SSHD project.  Just need to get
Eclipse to stop giving me Maven errors when loading the project.

On Wed, Apr 18, 2018 at 11:35 AM, Guillaume Nodet <gn...@apache.org> wrote:

> 2018-04-18 10:28 GMT+02:00 Emmanuel Lécharny <el...@gmail.com>:
>
> > Hi guys,
> >
> > I'd like to ask your opinion about what we should do with the FtpServer
> > project.
> >
> > There is little activity around it, and in the last 3 years, I was the
> > only one committig patches and code to the source base.
> >
> > OTOH, I know this project is being used, as  we have bug reports
> > periodically.
> >
> > At this point, I'd like to know what you think we should o about it :
> >
> > o move it to attic
> >
>
> I think the attic does not bring much to the community.  It should already
> be pretty obvious that it's not actively developped.
> The attic is imho interesting for a whole project, because the PMC is not
> capable of overseeing the project anymore.
> For a subproject, it does not bring anything
>
>
> > o keep going and trying to find new committers
> >
>
> Definitely, if people are interested in contributing, we should invite them
> as committers with a very low entry-bar.
>
>
> > o having some existing committers more actively taking care of the code
> > base
> >
> > Ideally speaking, the third solution is the best, the second is ok too,
> > but requires some people to step in.
> >
> > I don't have any time to investigate bug reports that are related to the
> > FTP functionality (I pretty much know nothing about FTP), but I can
> > spend time applying patches, fixing obvious bugs, or cutting releases.
> >
>
> Same here...
>
>
> > So, what's your opinion ?
>
>
> I'm not actively tracking JIRA issues.  I wonder if there would be a better
> way of applying patches.
> Maybe github PR could be automatically validated (i.e. run a full build on
> CI) and could be made more visible somehow ?
> That way, if we know they build passes, a quick check could be sufficient
> to merge the PR.
>
>
> >
> > Many thanks !
> >
> > PS: if any user is interested in participating in the project, we can
> > easily vote them in as committer : this is an open source project, those
> > who want to be part of it are very welcome.
> >
> > --
> > Emmanuel Lecharny
> >
> > Symas.com
> > directory.apache.org
> >
> >
>
>
> --
> ------------------------
> Guillaume Nodet
>

Re: FTPServer future...

[Guillaume Nodet <gn...@apache.org>]

So maybe we could do the following:
  * move projects to gitbox rather than using git-wip, this would allow us
to leverage github PR
  * set up CI builds to run a full build on all PR
For the move, we just need to ask infra about it.  It just makes things
easier to deal with and provide a more native github integration.
I'd like to setup CI builds  for SSHD anyway, so once that's done, it
should be easy to do the same for other projects.

Guillaume

2018-04-18 17:35 GMT+02:00 Guillaume Nodet <gn...@apache.org>:

>
>
> 2018-04-18 10:28 GMT+02:00 Emmanuel Lécharny <el...@gmail.com>:
>
>> Hi guys,
>>
>> I'd like to ask your opinion about what we should do with the FtpServer
>> project.
>>
>> There is little activity around it, and in the last 3 years, I was the
>> only one committig patches and code to the source base.
>>
>> OTOH, I know this project is being used, as  we have bug reports
>> periodically.
>>
>> At this point, I'd like to know what you think we should o about it :
>>
>> o move it to attic
>>
>
> I think the attic does not bring much to the community.  It should already
> be pretty obvious that it's not actively developped.
> The attic is imho interesting for a whole project, because the PMC is not
> capable of overseeing the project anymore.
> For a subproject, it does not bring anything
>
>
>> o keep going and trying to find new committers
>>
>
> Definitely, if people are interested in contributing, we should invite
> them as committers with a very low entry-bar.
>
>
>> o having some existing committers more actively taking care of the code
>> base
>>
>> Ideally speaking, the third solution is the best, the second is ok too,
>> but requires some people to step in.
>>
>> I don't have any time to investigate bug reports that are related to the
>> FTP functionality (I pretty much know nothing about FTP), but I can
>> spend time applying patches, fixing obvious bugs, or cutting releases.
>>
>
> Same here...
>
>
>> So, what's your opinion ?
>
>
> I'm not actively tracking JIRA issues.  I wonder if there would be a
> better way of applying patches.
> Maybe github PR could be automatically validated (i.e. run a full build on
> CI) and could be made more visible somehow ?
> That way, if we know they build passes, a quick check could be sufficient
> to merge the PR.
>
>
>>
>> Many thanks !
>>
>> PS: if any user is interested in participating in the project, we can
>> easily vote them in as committer : this is an open source project, those
>> who want to be part of it are very welcome.
>>
>> --
>> Emmanuel Lecharny
>>
>> Symas.com
>> directory.apache.org
>>
>>
>
>
> --
> ------------------------
> Guillaume Nodet
>
>


-- 
------------------------
Guillaume Nodet

Re: FTPServer future...

[Guillaume Nodet <gn...@apache.org>]

2018-04-18 10:28 GMT+02:00 Emmanuel Lécharny <el...@gmail.com>:

> Hi guys,
>
> I'd like to ask your opinion about what we should do with the FtpServer
> project.
>
> There is little activity around it, and in the last 3 years, I was the
> only one committig patches and code to the source base.
>
> OTOH, I know this project is being used, as  we have bug reports
> periodically.
>
> At this point, I'd like to know what you think we should o about it :
>
> o move it to attic
>

I think the attic does not bring much to the community.  It should already
be pretty obvious that it's not actively developped.
The attic is imho interesting for a whole project, because the PMC is not
capable of overseeing the project anymore.
For a subproject, it does not bring anything


> o keep going and trying to find new committers
>

Definitely, if people are interested in contributing, we should invite them
as committers with a very low entry-bar.


> o having some existing committers more actively taking care of the code
> base
>
> Ideally speaking, the third solution is the best, the second is ok too,
> but requires some people to step in.
>
> I don't have any time to investigate bug reports that are related to the
> FTP functionality (I pretty much know nothing about FTP), but I can
> spend time applying patches, fixing obvious bugs, or cutting releases.
>

Same here...


> So, what's your opinion ?


I'm not actively tracking JIRA issues.  I wonder if there would be a better
way of applying patches.
Maybe github PR could be automatically validated (i.e. run a full build on
CI) and could be made more visible somehow ?
That way, if we know they build passes, a quick check could be sufficient
to merge the PR.


>
> Many thanks !
>
> PS: if any user is interested in participating in the project, we can
> easily vote them in as committer : this is an open source project, those
> who want to be part of it are very welcome.
>
> --
> Emmanuel Lecharny
>
> Symas.com
> directory.apache.org
>
>


-- 
------------------------
Guillaume Nodet