Differences between revisions 1 and 25 (spanning 24 versions)
Revision 1 as of 2012-03-23 22:48:02
Size: 485
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 1: Line 1:
Packaging Giraffe the open source variant of the Zarafa Collaboration Platform ## page was renamed from Giraffe
=
Packaging Giraffe =

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

== Resources ==
Line 5: Line 10:
=== To Do ===  * Mailing List: https://lists.alioth.debian.org/mailman/listinfo/pkg-giraffe-discuss
 * Upstream: https://community.zarafa.com/
Line 7: Line 13:
 * Rebranding
 * Patches against libical, libvmime
 * Embedded copies of Smarty, fckeditor
 * Use Debconf
== Current State ==
The packages are not available by the Debian repositories, the packaging process is not yet finished.
Line 12: Line 16:
(list originally provided by GuidoGünther in https://honk.sigxcpu.org/piki/agx/publications/2011-06-debian-groupware-zs.pdf) == To Do ==
 * 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)
 * import upstream version 7.2.0
 * Fix Lintian errors and warnings
 * 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.
 * Move dlopen'ed libs to private directory
 * Remove embedded copies of fckeditor via the dfsg-clean branch in git, (use DebPkg: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 [[http://people.debian.org/~seanius/policy/examples/dbconfig-common/doc/dbconfig-common-using.html|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 [[ReneHeinen|René Heinen]]. The graphics are used inside the web application.

The main login window.

{{attachment:Giraffe-login.jpg}}

The graphic on the left side on top.

{{attachment:giraffe_top_logo.gif}}
{{attachment:giraffe_top_logo_SLIVER.gif}}
{{attachment:giraffe_top_logo_WHITE.gif}}

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]