All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Ira McDonald <blueroofmusic@gmail.com>,
	Johannes Meixner <jsmeix@suse.de>
Cc: Open Printing <printing-architecture@lists.linux-foundation.org>,
	Debian-printing@lists.debian.org, James Cloos <cloos@jhcloos.com>
Subject: Re: [Printing-architecture] Upstream future of ippusbxd
Date: Wed, 08 Jul 2015 15:59:45 -0300	[thread overview]
Message-ID: <559D7321.8070804@gmail.com> (raw)
In-Reply-To: <CAN40gSuQ70vpuCMX=1QCxiO0a+78y5G3OykniJepA08fM8V9Ng@mail.gmail.com>

Yes, I will maintain ippusbxd as a separate upstream package, and I will 
maintain it in a GIT repository. The only question is how to do it. 
There are two possibilities:

1. Create the GIT repo on the OpenPrinting web server, probably the 
Linux Foundation has already other problems under GIT. And they also 
have Bugzilla for bug tracking. In addition, move the other OpenPrinting 
projects to GIT.

2. Create an organization named OpenPrinting on GitHub and move ippusbxd 
to there. Move also the other projects to there converting them to GIT. 
And then keep Bugzilla on OpenPrinting or use the GitHub issue tracker 
instead?

WDYT? Which is the better method? And why?

    Till


On 07/08/2015 09:40 AM, Ira McDonald wrote:
> Hi,
>
> When Till and I talked about this on yesterday's OP monthly call,
> we concluded that keeping ippusbxd in a separate package was
> the best choice.  Till said that he would move the code to a Git
> repository (I hope this pleases you Tim) and link it off the Open
> Printing website.
>
> If anyone objects to keeping ippusbxd in a separate package,
> please speak up now.
>
> Cheers,
> - Ira


  parent reply	other threads:[~2015-07-08 18:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  1:15 [Printing-architecture] Upstream future of ippusbxd Till Kamppeter
2015-07-07  8:47 ` Johannes Meixner
2015-07-07 12:10 ` James Cloos
2015-07-07 14:16   ` Johannes Meixner
2015-07-07 16:02     ` James Cloos
2015-07-08  9:12       ` Johannes Meixner
2015-07-08 12:40         ` Ira McDonald
2015-07-08 14:10           ` Tim Waugh
2015-07-08 18:59           ` Till Kamppeter [this message]
2015-07-13 10:05             ` Tim Waugh
2015-07-07 15:33 ` Tim Waugh

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=559D7321.8070804@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=Debian-printing@lists.debian.org \
    --cc=blueroofmusic@gmail.com \
    --cc=cloos@jhcloos.com \
    --cc=jsmeix@suse.de \
    --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.