Differences between revisions 23 and 25 (spanning 2 versions)
Revision 23 as of 2015-04-25 18:04:20
Size: 3470
Comment:
Revision 25 as of 2015-04-25 20:58:57
Size: 2936
Comment:
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
 * repackage [[http://www.vmime.org/|libvmime]] (removed from Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774306 )  * repackage [[http://www.vmime.org/|libvmime]] (removed from Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774306 , gcrypt bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638651)
Line 19: Line 19:
 * evaluate trademark policy changes and decide on the necessity of rebranding
 * depended Debranding if needed:
  * --(Remove Zarafa logos from Zarafa Web Access)--
  * --(Rename the packages from zarafa-* to giraffe-*)--
  * Replace the favicon in `giraffe-webaccess`
  * Don't rename any binaries/directories
   * Should we better rename all or none of them?
   * We still have to provide a place to mention Zarafa (see their license)!
 * Fix debian/copyright
Line 29: Line 20:
 * Review and forward patches against DebPkg:libical and DebPkg:libvmime on upstream. For now it seems we can run with the versions in sid.  * Review and forward patches against DebPkg:libical (and DebPkg:libvmime, see above) on upstream. For now it seems we can run with the versions of the revitalized package.
Line 32: Line 23:
  * Partially done, we need to create DFSG source via import filter.
 * Remove embedded copy of `php-webclient-ajax/client/widgets/swfupload/swfupload.swf` use of DebPkg:libjs-swfupload instead
  * To be re done with version 7.2
Line 41: Line 31:
  * installing giraffe-server breaks without this
  * `giraffe-server` shouldn't create the database on it owns (it needs to much mysql rights for this -> CREATE DATABASE is needed)
   * we can do the creation of the database by dbconfig-common and the setup of `giraffe-server` by the postinst script
  * installing zarafa-server breaks without this
  * `zarafa-server` shouldn't create the database on it owns (it needs to much mysql rights for this -> CREATE DATABASE is needed)
   * we can do the creation of the database by dbconfig-common and the setup of `zarafa-server` by the postinst script
Line 45: Line 35:
 * WebApp tarball ships jQuery, extjs (3.4) and TinyMCE 4.0. (TinyMCE does not seem to be in the debian repositories)  * !WebApp tarball ships jQuery, extjs (3.4) and TinyMCE 4.0. (TinyMCE does not seem to be in the debian repositories)
Line 57: Line 47:

Packaging Giraffe

Giraffe is the free open source variant of the Zarafa Collaboration Platform packaged for Debian.

Resources

Current State

The packages are not available by the Debian repositories, the packaging process is not yet finished.

To Do

  • repackage libvmime (removed from Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774306 , gcrypt bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638651)

  • import upstream version 7.2.0
  • Fix Lintian errors and warnings
  • Review and forward patches against libical (and libvmime, see above) on upstream. For now it seems we can run with the versions of the revitalized package.

  • Move dlopen'ed libs to private directory
  • Remove embedded copies of fckeditor via the dfsg-clean branch in git, (use fckeditor package)

    • To be re done with version 7.2
  • Use Debconf to generate the initial configuration
    • database name
    • database user
    • database login
    • place of the database (local or remote)
    • more needed?
  • Use dbconfig-common to generate the initial database configuration

    • installing zarafa-server breaks without this
    • zarafa-server shouldn't create the database on it owns (it needs to much mysql rights for this -> CREATE DATABASE is needed)

      • we can do the creation of the database by dbconfig-common and the setup of zarafa-server by the postinst script

  • Package webapp (which seems possible since it is AGPL3, too).
  • WebApp tarball ships jQuery, extjs (3.4) and TinyMCE 4.0. (TinyMCE does not seem to be in the debian repositories)

  • Test full functionality
    • We'd need some Outlook users here, too...
  • fix init script
    • systemd compatibility
    • error out when database is missing
  • systemd unit
  • clean up packages (empty packages etc.)
  • MTA integration
  • check package descriptions
  • logrotate
  • check pre-/postinstall scripts
  • z-push upstream update

The origin of this list is provided by GuidoGünther in https://honk.sigxcpu.org/piki/agx/publications/2011-06-debian-groupware-zs.pdf

Debranding/Rebranding

We have currently a re branded artwork made by René Heinen. The graphics are used inside the web application.

The main login window.

[ATTACH]

The graphic on the left side on top.

[ATTACH] [ATTACH] [ATTACH]