From: Till Kamppeter <till.kamppeter@gmail.com>
To: Open Printing <printing-architecture@lists.linux-foundation.org>
Cc: Matthew Morikawa <Matthew.Morikawa@dda.kyocera.com>
Subject: [Printing-architecture] Hosting of OpenPrinting
Date: Tue, 12 Jul 2016 13:30:18 -0300 [thread overview]
Message-ID: <57851B1A.8010700@gmail.com> (raw)
Hi,
for the time being until I will (hopefully) come around with the call
next week, I will give you all something to think about and a call for help.
It is about the web hosting of OpenPrinting. You now that we are hosted
at the Linux Foundation currently. And with the Linux Foundation there
are problems, in the form that I do not get any help by the system
admins any more. The front page (www.openprinting.org) is messed up and
I cannot change it any more. Therefore I asked the help desk already
several times and never got an answer.
So for me it seems that the best is to move.
For the BZR repositories I am thinking about converting to GIT and use
GIThub. CUPS and many other projects are already there. I would also
handle the bug tracking there.
What does not work on GIThub (or does it already?) is to have a general
LAMP (Linux, Apache, MySQL, PHP/Python/Perl) server to run the database
and also the documentation, mailing lists, announcements, ... I think I
would drop the forums then and go back to mailing lists.
Perhaps the PWG could help me?
A problem would be the domain www.openprinting.org, to get it moved from
the Linux Foundation to the new place. Or should we perhaps rename the
project as a last mean.
I appreciate any kind of help.
Till
next reply other threads:[~2016-07-12 16:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 16:30 Till Kamppeter [this message]
2016-07-12 23:46 ` [Printing-architecture] Hosting of OpenPrinting Michael Sweet
2016-10-14 20:18 ` Brian Norris
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=57851B1A.8010700@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=Matthew.Morikawa@dda.kyocera.com \
--cc=printing-architecture@lists.linux-foundation.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.