Re: [screen-devel] screen maintainer

[Neal Fultz]

This sounds great; I was very impressed with how quick you merged my patch
in last week. I've been using your branch since then and been quite happy
with it.

I'd actually made that patch last summer and sat on it just because the
project seemed totally dead; the releases have been glacial, even by
gnu standards, and for several months the only traffic on the mailing list
was the same person asking how to change their background color over and
over.

I think a 4.1 release is a good first step to breathing some new life into
screen. If you want to put in the time and effort, go for it.



-Neal


On Wed, Apr 02, 2014 at 04:27:53PM +0200, Amadeusz Sławiński wrote:
> Hello,
> 
> seeing as we came yet again to standstill with new release, I would like
> to volunteer myself as GNU Screen maintainer.
> 
> Some of you may know that I maintain separate development tree on github
> (https://github.com/amade/screen/tree/devel/src) in which I have a more
> than 300 changes committed in comparison with official tree. So I may
> as well do this officially ;)
> Changes include:
> * new features (256 colors in hardstatus, hardstatus on top,
> truecolor, ...)
> * removal of ancient code (removed most of #ifdef for ancient systems)
> * removal of features which didn't seem useful or could be replaced
> * rewrites of some functionality
> * bug fixes
> * code reformatting (the source is much more readable now).
> Some of the removed things may need to be reintroduced, but that's what
> development is about. Goal is to hear what features people want and to
> get things going again.
> 
> First thing I would do, would be releasing current git tree as
> screen-4.1 also opening separate version 4 branch, only for bug fixes
> so distributions have something recent to base their packages on.
> Next step would be merging my 'devel' branch into master and start
> developing version 5.
> 
> Comments, suggestions, alternative solutions?
> 
> Amadeusz Sławiński
>