Iain these are positive steps and seem to be an optimal use of the labour 
available.
I look forward to working with a lighter, tighter, 
even-more-easy-to-understand stack.

Any thoughts on when users of GnuTLS.jl should migrate to MbedTLS.jl?
(I'm a 0.3 user and won't be switching to 0.4 until it is stable, which I 
guess won't be far off anyway)



On Monday, September 7, 2015 at 1:53:29 AM UTC+10, Iain Dunning wrote:
>
> Hi all,
>
> JuliaWeb started off as a really mixed collection of packages, many of 
> them made by people who had moved on (Hacker School). Most were essentially 
> unmaintained.
>
> By putting them all these packages in one place, we've basically managed 
> to tread water for a while, trying to merge PRs if we understand them and 
> doing basic maintenance.
> It was clear it wasn't long term viable though - no one maintaining really 
> had a strong need or desire to 'own' these packages.
>
> Recently, we've taken some steps to reign things in and focus limited 
> resources:
> - Deprecate Meddle and Morsel.jl. These are "web framework" type packages 
> that were too complex to be maintained, but were seemingly somewhat popular 
> (by github stars, at least). 
> I've added a max version cap of 0.5 on all releases and master (so they'll 
> install on 0.4, but not 0.5), and made it clear in the README that they are 
> abandoned.
> I doubt someone will take over maintenance, so they are effectively out of 
> sight and mind now.
>
> - Move away from GnuTLS.jl. Apart from concerns about GnuTLS itself, this 
> package was also unmaintained and poorly understood, while being critical 
> to pretty much everything.
> @malmaud has created a new wrapper for MbedTLS, which should be simpler 
> and more importantly, it works. We'll be moving e.g. Requests, etc. to 
> MbedTLS.jl
>
> - We no longer support Julia 0.3. A branch was made on the last 
> 0.3-supporting commit, so people can submit PRs if they wish to backport 
> fixes to that line, but the limited volunteer
> power available will not be touching it. This is yielding benefits 
> already: last night I systematically went through HttpCommon.jl and was 
> able to get 100% coverage, no Compat.jl cruft,
> 0.4-style docstring on everything, and removal of redundant or unsupported 
> functionality. Contributions along these lines welcome for the other 
> JuliaWeb packages too.
>
> Thanks,
> Iain
>

Reply via email to