Hello All:

  I must say before anything that I'm not a user of ion3, just a Debian user 
and I was concerned about this discussion because it's a topic that affects 
not only ion3 but Debian and some of its upstream sources. Having asked for 
permission, let me elaborate a rationale about the problem. I know I'm not an 
important part here, so excuse if you feel bothered by this public wondering.

  I have to say that I understand both positions upstream and Debian. For free 
software, both are possible and even more, necessary but in order for both to 
prevail they have to reach an agreement.

  THE PROBLEM
  Upstream must understand Debian philosophy and that means that a very 
important distro (among the most importants right now) will provide its users 
with such an upstream technology, in this case ion window manager.

  Besides, Debian must understand what providing that technology means. I'm 
sure that it almost understood since its long history and experience, but 
maybe there still some work to do as this is not the first and only upstream 
project that complaints about Debian methods.

  THE SOLUTION
  As it is said "In medio consistit virtus" (in the middle point you have the 
virtue) for me that point is feedback between the two sides and in the time a 
stable version is needed by Debian, upstream would have to understand the 
situation and tell which version is better once asked. 

  Also Debian have to take care of that version because normally as Debian 
stable haven't to coincide with upstream stable, upstream couldn't care about 
that "transition" version anymore.

  At this point the friction between the parts is maximum, I think largest 
complaints upstream are:

  · Users ask for support at the wrong place. Support should be provide there 
by Debian, not by upstream, This is the worst case IMHO. Upstream should 
suggest the Debian stable version so accepting that version will be present 
more or less widely, hence being aware that support could also requested.

  · Major or important divergences once the application is packed, maybe 
becuase is not deployed as upstream author/s would like.

  · Add your own here.

  Finally, everypart is free of doing what their licenses grant. So ion3 could 
possibly forbid its inclusion into Debian as Debian maintainer could not 
accept the ion3 intended upgrade policy and leave ion3. But I could hardly 
see what is the point in this case :P 

  So I hope this will have a happy ending and I humbly encourage you to reach 
and agreement if possible for the good of those who like and will like Debian 
and ion3.

  Regards,
-- 
     Raúl Sánchez Siles
----->Proud Debian user<-----
Linux registered user #416098

Attachment: pgpf0tbhWQcIp.pgp
Description: PGP signature

Reply via email to