Closed obiltschnig closed 5 years ago
I would suggest to put also NetSSL_Win & Crypt_Win in the core codebase for consistency.
What about the "NetEx" library we were talking about in the past?
On Wed, Sep 21, 2016 at 2:16 PM, zosrothko notifications@github.com wrote:
I would suggest to put also NetSSL_Win & Crypt_Win in the core codebase for consistency.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/pocoproject/poco/issues/1420#issuecomment-248680365, or mute the thread https://github.com/notifications/unsubscribe-auth/AAWkeQdKc4njs80eVSLZlW2DwOcpB6wAks5qsWZ-gaJpZM4KC3eZ .
NetEx should go into its own repository.
Regarding NetSSL_Win and Crypto_Win - these would need a bit more work and testing (especially Crypto_Win), as well as a regular maintainer.
I have a NetEx stale sandbox somewhere, with async HTTP client and everything moved (ICMP etc). I can take ownership of that portion transition.
I plan to reorganize the GitHub repository in the near future, with the goal to:
Note: this is a work in progress, subject to further discussion.
Ultimately, the poco repository will only contain the following libraries and tools:
All other libraries will be moved into their own repositories:
This will allow us to nominate maintainers for the various libraries and give them full GitHub access to these repositories, without having to give everyone full access to the poco repository. Also, it will get libraries that are currently not maintained (PDF, SevenZip) out of the main codebase.