From: Kai-Uwe Behrmann <ku.b@gmx.de>
To: printing-architecture@lists.linux-foundation.org, kwin@kde.org,
desktop-devel-list@gnome.org, lxde-list@lists.sourceforge.net,
xfce4-dev@xfce.org, kde-core-devel@kde.org,
enlightenment-devel@lists.sourceforge.net,
matede-velopment@lists.sourceforge.net,
unity-dev@lists.launchpad.net, webkit-dev@lists.webkit.org,
events@lists.mozilla.org
Subject: [Printing-architecture] [Announce] Linux Color Management Hackfest 2012
Date: Fri, 25 May 2012 18:28:54 +0200 [thread overview]
Message-ID: <4FBFB346.8070502@gmx.de> (raw)
During the recent LGM[1] we started to organise a hackfest[2]. The
event aims at bringing developers of the Linux applications and desktops
and experts interested in color management (CM) together and support the
integration of CM inside their open source projects and distributions. The
hackfest will happen
from 16th until 19th November 2012 in
Brno, Czech Republic.
The Red Hat offices[3] are kindly offered during the event and be well
equipped for our purpose.
We spotted three main focuses:
* desktop applications, including window managers,
* web browsers and
* printing.
These topics are already worked on, but in a scattered way. By meeting in
person in one place, we want to get something done and build a good
understanding of the role of each participating group for a working end to
end color management.
If you are interested in joining the hackfest, please fill your name and
information on the OpenICC wiki page [4] to help us estimate resources. In
case you need a visa, please write us preferedly soon as mail can take a
while. Submission deadline for obtaining sponsoring will be 30th of
September.
regards,
Kai-Uwe Behrmann
--
organisation for openicc.info
[1] http://www.oyranos.org/2012/05/linux-color-management-hackfest-idea/
[2] http://en.wikipedia.org/wiki/Hackfest
[3] http://g.co/maps/taqng
[4] http://www.freedesktop.org/wiki/OpenIcc/Events/Hackfest/2012
reply other threads:[~2012-05-25 16:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FBFB346.8070502@gmx.de \
--to=ku.b@gmx.de \
--cc=desktop-devel-list@gnome.org \
--cc=enlightenment-devel@lists.sourceforge.net \
--cc=events@lists.mozilla.org \
--cc=kde-core-devel@kde.org \
--cc=kwin@kde.org \
--cc=lxde-list@lists.sourceforge.net \
--cc=matede-velopment@lists.sourceforge.net \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=unity-dev@lists.launchpad.net \
--cc=webkit-dev@lists.webkit.org \
--cc=xfce4-dev@xfce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.