On Tue, Jun 27, 2017 at 1:45 PM, Nicolas wrote:
> I was maintainer for piwigo package for many years.
> I cannot precisely why I stopped manage that package
Looking at the removal bug, it sounds like there wasn't time to make a
non-messy package; it was removed for lack of response to RC bugs,
security issues, missing dependencies, embedded code copies, non-free
content, upgrade issues etc.
https://bugs.debian.org/694820
https://bugs.debian.org/cgi-bin/pkgreport.cgi?archive= both;dist=unstable;package= piwigo
> acceptance rules are more and more constrainant. I think about minified
> stuff (_javascript_, stylesheets) that need to be unminified in debian.
These requirements have always been there for all of Debian, they
haven't become more restrictive over time. It was just that people
packaging web apps didn't think about the requirements and then the
rest of Debian noticed that was happening and started working on QA
efforts to automatically detect these problems and file bugs so that
maintainers would fix them.
> Upstream not always understand problem. And it gives maintainers more work
> to minified them afterwards to have a good visitors experience.
It should be simple for Debian to use the same automated minification
process as upstream does right?
> Flash is another big problem. I didn't find a solution even if flash's end of life is
> more and more real !
Flash is dead, it is time for everyone to stop supporting it. If your
packages build-depend on Flash related things, I strongly suggest
removing them from upstream.