All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] OpenPrinting Web site update
Date: Tue, 14 May 2013 21:46:04 +0200	[thread overview]
Message-ID: <5192947C.3040107@gmail.com> (raw)
In-Reply-To: <CA+PBKyLF+9b5qd0_i-qyy6HYeRhdQT20bedacfO7PmJCa5smqQ@mail.gmail.com>

On 05/14/2013 08:43 PM, Naruhiko Ogasawara wrote:
> Hi Till, OpenPrinting guys,
> 
> I've just checked OpenPrinting Web site:
> http://www.linuxfoundation.org/collaborate/workgroups/openprinting
> 
> And found some problems.
> I'm not sure they should be correct or not, but just itemize.
> 
> # Sorry I should say in the OpenPrinting Plenary track, but I lost
> # a timing.
> 
> 
> 1. Do you have any plan to recover our forum?
>    http://forums.openprinting.org/
>    This was great forum lead by communities to talk about cross-
>    distro printing problems, but unfortunately have dead since 2
>    years before.
> 

Yes, many people want to have it back.

> 2. Our tutorial:
>    http://www.linuxfoundation.org/collaborate/workgroups/openprinting/database/cupsprintingtutorial
>    seems only has a historic meaning, because most of all distros
>    already CUPS as a default, and the two link following "Read
>    it here..." point wrong place (LSB page).
>    I think this page should rewrite as cross-distro howto, for
>    example generalized how to report the CUPS bug.
> 

I will at least tell that it is old. I would need volunteers for writing
an up-to-date one.

   Till


  reply	other threads:[~2013-05-14 19:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 18:43 [Printing-architecture] OpenPrinting Web site update Naruhiko Ogasawara
2013-05-14 19:46 ` Till Kamppeter [this message]
2013-05-14 20:10   ` Naruhiko Ogasawara
2013-05-15 11:30     ` Till Kamppeter

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=5192947C.3040107@gmail.com \
    --to=till.kamppeter@gmail.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.