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

[Sébastien Villemot]

Le lundi 07 mars 2016 à 22:32 -0400, David Prévot a écrit :
> Le 07/03/2016 12:43, Sébastien Villemot a écrit :

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

[...]

> > 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.

Thanks for providing this information. I realize that the situation is
indeed quite difficult. I won't open a wnpp bug by myself, since I
understand that you don't think it's a reasonable solution.

> 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.

Do you plan to continue maintaining those extra PHP packages?

I'm asking because I plan to move to a manual installation of ownCloud
using upstream provided tarball (I won't use the upstream provided .deb,
because if this .deb is not good for inclusion in Debian, then it can't
be good for installation on my system). Do you think such setup will be
viable (especially with respect to the various dependencies) on a sid
system?

Cheers,

-- 
 .''`.    Sébastien Villemot
: :' :    Debian Developer
`. `'     http://sebastien.villemot.name
  `-      GPG Key: 4096R/381A7594