Re: prominent message on website about "use only on

On 2017-08-01 11:24, Alexander Leidinger wrote:
> 
> Well... what about first doing a summer-cleaning (fixing the issues),
> and then switching (if there is a volunteer, why not?) for the
> hope/benefit of maybe attracting new blood?
> 
> One more thing which may play a role here... we don't really have the
> release process written down, do we?

Good point, the release process might also be a barrier.

What about this plan:
*Someone is working on the switch to libmpg132 (TO)
*Someone puts Robert's changes in a branch, and revert the HEAD to 
3.99.5 (GB?)
*Someone ensures that the switch to libmpg123 is properly working 
(configure changes?)
*Someone applies the pending security patches
*Someone writes down the release process (GB)
*Someone releases 3.99.6 (GB?)
*Someone switches the source code (and its history) to git (where? on 
GitHub?)
*Someone handles the move from Sourceforge to GitHub
*Someone becomes new maintainer

There are a lot of "someone" there :-), but those seem to be the 
required steps (not necessarily in this order).

Do we have volunteers for the unassigned tasks?

Regards,

--
Gabriel Bouvigne




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot