FWIW, I'm trying to get webgui as an official Debian package. I've been packaging
it for a couple of years now, for my personal and business use. The package has been
cleaned up and reorganized several times in order to comply both with Debian Policy
and my experience using WebGUI in cooperation with other applications under Debian.

Three weeks ago, my sponsor attempted a new package upload. The package was
accepted in the incoming queue, meaning the _form_ of the package is correct and
passes all the structural tests, but was rejected by FTP masters, meaning the
_contents_ of the package has several problems that need to be addressed in
order for it to become an official Debian Package.

I took care of most of the objections regarding placement of the JS libraries, but still
need to address several issues, so I turn to you guys to see what can and cannot
be done.

According to Debian Policy there will never be a package in Debian containing
non-free or non-freely-redistributable code, also there cannot be a package
that simply "includes" a wholesale third party program or library. That was the
major reason for rejecting the package as explained both to me and my sponsor
by the FTP masters. So, I've been going through every single file in www/extras
and need the following issues clarified:

1. I assume every image file, HTML document and JavaScript code fragment
there is Copyright of PlainBlack unless a license saying otherwise is found.
It would be nice to have a file (README, LICENSE, whatever) stating
which files are copyright PlainBlack; it would be even nicer if each file had
a short copyright note. If this is seen as annoying, I will still need some evidence
(an e-mail will suffice) stating "the files ... are Copyright blah blah blah ... and
are licensed under the GPL (or whatever)".

2. There are some JavaScript libraries there that have explicit licenses. I'm
_almost_ sure they will need separate packaging for Debian, but hopefully not.
Having to package those libraries separately will take time now and in the future,
unless I can remove them safely from the webgui package in case they are not being
used. I'm currently worried about the following fragments:

a. www/extras/calendar. It has an LGPL license. If it's being used I MUST
package it separately.

b. www/extras/coolmenus. It has a free license. If it's being used I MUST
package it separately.

c. For the stuff in www/extras/js/ I'm pretty sure the license is not
free enough, so I cannot package it for Debian main. If it's being used I
need to surgically remove references and see how that impacts WebGUI's
behaviour :-/ If the impact is severe, then I'm afraid the current webgui
package will not make it into Debian main.

d. www/extras/Navigation. It has a free license. If its being used I
MUST package it separately.

e. www/extras/slider. It's GPL. If its being used I MUST package it
separately.

f. There's tinymce, tinymce2 and tinymce-webgui. Tinymce2 is already in
Debian, so it's a matter of symlinks... Is tinymce still being used? I
assume tinymce-webgui has your local changes to tinymce2.

g. www/extras/yui-carousel. It has a CC license. If its being used I
MUST package it separately.

If any of these libraries is not being used, it can be removed from the
package, but need to know for sure it's not going to break anything. Just
so you know, I've already removed YUI from www/extras and symlinked to
Debian's provided YUI and everything is working as expected.

We can always distribute the Debian packages including all this stuff: they will
be outside Debian but will work fine in Debian and will be installed using aptitude
or synaptic directly from my custom repository (or a plainblack sponsored repository
if you like). In order for the package to make it _into_ Debian, which is my objective,
all its contents MUST be properly licensed and, if necessary, packaged independently
(no third-party "wholesale" allowed).

Hope we can sort this out in time for the Lenny freeze starting on july :-)

--
Ernesto Hernández-Novich

colink wrote:

As discussed in IRC, extras/calendar is used by ProjectManager.pm, and by template EventManagerTmpl000002.tmpl.  Is it possible to change them to use the YUI calendar instead?

http://www.plainblack.com/webgui/dev/discuss/fixing-webgui-to-comply-with-debian-policy/re-fixing-webgui-to-comply-with-debian-policy

--

Plain Black, makers of WebGUI
http://plainblack.com

The yui-carosel is not being used anymore, I'll delete it.

Some of this has already been fixed in 7.5, but unfortunately you're working on 7.4. You can backport our changes if you want. I'd be happy to spend some time over the next couple of weeks to get rid of cool menus in favor of YUI nav, but again that's only going to be for 7.5, not for 7.4.

I've dropped the 7.4 package in favor of 7.5. I mentioned it on IRC but you weren't there at the time.

Al the issues I've mentioned are with 7.5.10 which is what the package currently has, waiting for 7.5.11 to attempt a NEW PACKAGE upload again.

The target for Lenny is webgui 7.5.11 or better.

--

Ernesto Hernández-Novich

Is there any progress in getting WebGUI into Debian Testing aka Lenny?

I would like to get my hands dirty on it.

I just read this post: http://lists.debian.org/debian-volatile/2008/05/msg00003.html

In that post was the link to the actual request to get WebGUI into debian:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=471697

On this page is the clear statement that the request is now 128 days old and modified 78 days ago.

Here is the development page of Ernesto http://alioth.debian.org/users/emhn-guest/

Too bad I cannot find the packages created by Ernesto anywhere, can someone point me to them?

Koen de Jonge - ProcoliX
http://www.procolix.com
Hosting - WebGUI - Virtualization