From: Tim Waugh <twaugh@redhat.com>
To: Till Kamppeter <till.kamppeter@gmail.com>,
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: Mon, 13 Jul 2015 11:05:40 +0100 [thread overview]
Message-ID: <1436781940.5156.14.camel@redhat.com> (raw)
In-Reply-To: <559D7321.8070804@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
On Wed, 2015-07-08 at 15:59 -0300, Till Kamppeter wrote:
> 2. Create an organization named OpenPrinting on GitHub and move
> ippusbxd to there. Move also the other projects to there converting
> them to GIT.
One very big advantage of using GitHub is that you get to use tools
like Travis CI/Jenkins for continuous integration easily, so that every
time a change is made or proposed you can see whether it will break the
build. If there was a test suite, it could also run that. You can also
link projects to coverity-scan for free usage. Here's an example using
both those things:
https://travis-ci.org/twaugh/patchutils/builds/70706661
(I think coverity defects are only visible to the project owner.)
GitHub also has a useful mini-patch-review system. When anyone submits
a pull request from their own repository or from a branch in the main
project, you can comment on individual lines that are changed.
> And then keep Bugzilla on OpenPrinting or use the GitHub issue
> tracker instead?
If you wanted to stick with Bugzilla there's a GitHub webhook to
integrate with it. (I've never used it myself.)
https://github.com/github/github-services/blob/master/docs/bugzilla
I think all those things happen automatically with GitHub's issue
tracker.
Tim.
*/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-07-13 10:05 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
2015-07-13 10:05 ` Tim Waugh [this message]
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=1436781940.5156.14.camel@redhat.com \
--to=twaugh@redhat.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 \
--cc=till.kamppeter@gmail.com \
/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.