[Pkg-owncloud-maintainers] Bug#816376: Unfit upstream

[David Prévot]

Hi Sébastien,

Le 07/03/2016 12:43, Sébastien Villemot a écrit :

> On Tue, 1 Mar 2016 07:07:10 -0400 David Prévot <taffit at debian.org> wrote:
> 
>> Upstream doesn’t wish to see their software in Debian anymore. Unless
>> the situation changes in the next few months, owncloud will not be part
>> of Stretch.

[…]
> I am wondering whether this outcome could be avoided.
> 
> If I understand correctly, your decision is essentially based on social
> issues (upstream hostile to Debian packaging), coupled to some technical
> aspects (complex upgrade paths).

That description fits roughly my view of the problem, yes.

> At first glance, this does not seem to prevent the package from staying
> in Debian. Maybe this just means that the package needs a new
> maintainer, who is willing to handle the tough interaction with upstream
> and dealing with the technical issues

That might work. I honestly doubt upstream would be willing to have its
pet project properly packaged by anyone in the near future (most
distributions gave up before us), but I’d be happy to be proven wrong.

> You are certainly in a better position than me to ascertain whether the
> package can stay in Debian or not, but I think that it would be useful
> if you could give a little more background on the issues that you
> encountered.

Reading the (recent) threads on both the maintainer and upstream lists
should help anyone to make their mind about it (I’ll give a few
pointers). Seeing how Debian is described in upstream staff blog posts
and issue tracker goes further down (I don’t wish to publish some direct
links from the BTS, but they’re not hard to find).

[ When I realized they were going to make our life way more painful ]
https://lists.alioth.debian.org/pipermail/pkg-owncloud-maintainers/2016-February/002882.html

[ When they considered enforcing their trademark to throw us away ]
https://mailman.owncloud.org/pipermail/devel/2016-February/002106.html

> And, if you think it makes sense to orphan the package,
> that would help prospective new maintainers in making the decision to
> adopt the package or not.

I’m happy to give anyone write (and admin) access to our current
infrastructure. Feel free to open an RFA or O wnpp bug on my behalf if
you think it might help. But please, be aware that the enormous owncloud
package is only the tip of the iceberg: beyond the ~70 packages (some
were already removed via #816769) listed on the [DDPO], I was
maintaining a few more dozens on the PHP PEAR (and composer) Maintainers
team as well as some JavaScript packages.

DDPO:
https://qa.debian.org/developer.php?login=pkg-owncloud-maintainers%40lists.alioth.debian.org

Regards

David

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-owncloud-maintainers/attachments/20160307/ae10475f/attachment.sig>