Re: prominent message on website about "use only on

Quoting [email protected] (from Tue, 01 Aug 2017 16:54:43 +0200):

> 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?)

I can have a look at the configure parts.

> *Someone applies the pending security patches
> *Someone writes down the release process (GB)
> *Someone releases 3.99.6 (GB?)

Fine so far for me (also if libmpg123 is not the target for the next release).

> *Someone switches the source code (and its history) to git (where?  
> on GitHub?)
> *Someone handles the move from Sourceforge to GitHub

You can switch from CVS to git on SF.
http://blog.gorwits.me.uk/index.html%3Fp=529.html

With this the big part is done, and people can use it. We don't need  
to switch to github (directly) -> less work (think about the content  
we have on the website and in the bugtracker and so on).

Bye,
Alexander.

-- 
http://www.Leidinger.net [email protected]: PGP 0x8F31830F9F2772BF
http://www.FreeBSD.org    [email protected]  : PGP 0x8F31830F9F2772BF
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot