Bug#859808: composite: Composite not ready for being qualified package of Debian yet.

[MAROQQO digital media]

Hi, thanks for your thoughts on this, Jaromir but:

On 04/08/2017 08:52 AM, Jaromír Mikeš wrote:
> composite package builds fine and seems to have it's own users ... by popcon
> https://qa.debian.org/popcon.php?package=composite

To simply say "well, it has its own users" by showing install graphs of 
150 installs is a very simplified point. Sure it has statistically it's 
"own users". Every available download has that. Pro audio users tend to 
test available software by just grabbing it for a go while they often 
miss a good overview at first. But it says nothing about its real usage. 
Pro audio users often even have no real clue about the OS they run. 
That's why there are so many pro audio multi-packaged bundles around. 
Since I have tested the package I can say that this a 100% copy of an 
old Hydrogen version without progression. Many new users will not know 
what they have here, since there is no explanation about it. It's a lil' 
bit like the mess with ffmpeg and libav and the misleading notice while 
installation back in the days. The reason for the install statistics 
even more prove my worries but do not invalidate them.

To be honest I really wonder about what qualifies a package to be added 
to the repositories of Debian, since I used to tend to the impression, 
that Debian is very picky about it (one of the reasons I choose Debian).

On 04/08/2017 08:52 AM, Jaromír Mikeš wrote:
> I am very sorry that some hydrogen users are confused but I personally
> don't think it is reason strong enough to remove composite from debian archive

Well, this is not the only reason if you read my start post and btw ... 
it actually is one of the smaller points actually, and "Some" is the 
wrong word here since - as I stated - Composite is a complete copy of an 
8 year old Hydrogen version package and many acknowledged users, who 
know which audio software is available on Linux don't even know this 
package. They were very confused when I told them about it. Even audio 
software developers were confused. It's odd and I can't believe that the 
fact that it is a simple copy of old code which has never started to 
grow and shows no progress isn't reason enough. I really winder how this 
even came in? I am sad that you don't go into any further details about 
all other points I stated and that a simple install graph which grows by 
itself over the years is reason enough for you to say it's ok.

Again:

  + Composite describes its own status as "a broken version of Hydrogen" 
(Look at the sources I have posted, its in their own words)
  + This status has never been changed since 2009
  + Composite stuck in early alpha and completely feels, acts, looks and 
works like Hydrogen, a well known and in active development being audio 
application with the exactly same GUI and features atm.
  + The road map shows that this package is in early state and only
confuses Hydrogen users now since this fork has never left any copy
  paste state yet despite of its name

I am even not sure if there isn't a copyright infringement going on 
since Hydrogen code is published on Github under GPL 2 license which 
resticts you to only use this code by using the same license, but the 
"author" of Composer has no license statement on their site at all. I am 
sorry for sounding offending here, this is not my purpose, but I really 
really wonder about all this ignored points.