Open Stack

On 11/15/2014 06:27 AM, Gabriel Hurley wrote:
> So, I propose that a group gets together and defines criteria:
> we need to accept that the Horizon team (and those knowledgeable
> about web-app development) know best what tools they need, and
> they need to produce such a list as a starting point. We then
> need packagers and maintainers to examine that list and evaluate
> it for problems (non-free software, irresolvable dependencies,
> etc.). They're looking strictly for things which are un-packageable,
> not commenting on the necessity of said software. And we need people
> (thanks, Monty) willing to build new tools to find a way to turn
> that list into something the package maintainers can consume
> without burdening either side.
> 
> Make sense?
> 
>      - Gabriel

I'd be happy to be in this group.

Let me sum-up again my opinion.

Selenium
========
As I wrote previously, the biggest issue currently for me, is selenium.
It is very frustrating that I can't run these unit tests when building
package, and potentially loose the opportunity to discover problems. I
really would like this to be solved. There's 2 ways of solving it:

1/ Someone works so that the .xpi can be built together with the rest of
selenium, and therefore, selenium can leave the non-free repository of
Debian and go in main (and also be uploaded in other distros).

2/ We move away from Selenium and decide to use something else like
PhantomJS.

Tooling for JS dependencies
===========================
As for the tooling, we're currently talking about 7 new dependencies,
which isn't much. I believe it's preferable to continue to use XStatic,
because it has been very convenient in many aspects (I wont list here
why again...), and that doing 7 new xstatic packages will not be so much
work. But I wouldn't mind if there was some kind of environment used by
developers to experience new things faster, if that doesn't affect
packaging.

Can someone sum-up the other opinions for the other options?

Cheers,

Thomas Goirand (zigo)