The state of FileZilla server development.

[dirty_white_hat]

The last build published was on 2017-02-08. Looking at the issue tracker I'm seeing some most issues have been stale for years, up to 15 years in one case. So my question is: "What is the state of FileZilla Server development?" Does anyone maintain the issue tracker? Is there a process for submitting code to be reviewed?

I'm used to using GitHub to contribute to FOSS projects. Usually I fork, work on my fork, then I can issue a pull request from my fork to the main branch. This way, anyone can submit code to the project. I'm not familiar with SVN. If I wanted to contribute how would I go about interacting with the development team?

[botg]

FileZilla Server is currently being rewritten from scratch.

Patches can be submitted through the issue tracker in the form of unified context diffs. Patches need to be of high quality if they are to be accepted. If a patch adds new functionality, it also needs to fit the project's vision.

[boco]

@botg: What about a small intermediate release of the old server, with no changes but updated OpenSSL libs? The ones included with 0.9.60 are quite dated. Trying to use the updated ones from Windows-OpenSSL-packages does not work.

[botg]

I'm having difficulties building this dated piece of software.

[boco]

Would it work to build only the SSL libs, for manual replacement? As I mentioned, the ones from the shelf don't work.

[botg]

Possibly.

[dirty_white_hat]

FileZilla Server is currently being rewritten from scratch.

Thanks botg! If this is an open source effort where is the code repository for the new version? I'm curious about the progress.

[botg]

Nothing in a sharable state yet.