All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Goldstein <cardoe@cardoe.com>
To: Lars Kurth <lars.kurth@citrix.com>,
	George Dunlap <George.Dunlap@citrix.com>,
	Andrew Cooper <Andrew.Cooper3@citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: xenbits GitHub mirror?
Date: Wed, 3 Feb 2016 09:38:33 -0600	[thread overview]
Message-ID: <56B21EF9.60205@cardoe.com> (raw)
In-Reply-To: <D2CE8F3A.2512E%lars.kurth@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 2062 bytes --]

On 1/27/16 9:18 AM, Lars Kurth wrote:
> 
> Sorry, I have been a little bit unresponsive. Things were a little hectic
> in the last 2 weeks.
> 
> 
> On 27/01/2016 11:21, "George Dunlap" <George.Dunlap@eu.citrix.com> wrote:
> 
>>
>>> FWIW, I am +1 for setting up infrastructure like this, but lets do it
>>> properly.
>>>
>>> Lars: Thoughts?
> 
> I don't mind if we had an official github mirror. In fact, it may make the
> project a little bit more accessible to the younger crowd.
>  
> 
>> Doug says that you can mark a repo as a 'mirror', which will prevent
>> people from being able to send pull requests to it; so I think my
>> technical objection has been answered.
>>
>> I think the idea is still only half-baked though, as I'm not sure how
>> having a github mirror will make it so that most mail has a git repo
>> you can pull from (which would be necessary to reach the ultimate
>> goal, making it straightforward to apply patches sent to the list).
> 
> 
> I would be good, if we could identify any workflow issues (e.g. such as
> the mailing issue raised here). Maybe some of the people who have hands-on
> experience with Github and mailing lists can make a few suggestions. We
> then should also consider adding this to the How to submit patches wiki
> page
> 
> Lars
> 

I've gone ahead and created https://github.com/xen-project/xen I've also
reached out to GitHub to make it an "official" mirror. I can have GitHub
setup a periodic pull from the repo (this might take some time) or we
can add a post-receive hook that pushes to that repo.(git push --mirror)

I've also reached out to Lars off list to turn over the 'xen-project'
organization over to him.

As an aside I know we've got osstest but I've like to utilize the free
service from Travis CI to run simple compile tests on each commit. This
could potentially be wired into osstest as well. (In my organization we
use Travis CI for simple tests on commits and when those pass we kick
off our more in depth tests).

-- 
Doug Goldstein


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 959 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      parent reply	other threads:[~2016-02-03 15:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-19 20:51 xenbits GitHub mirror? Doug Goldstein
2015-12-21 11:54 ` George Dunlap
2015-12-23  8:53   ` Jon Ludlam
2016-01-26 16:48     ` Doug Goldstein
2016-01-26 16:55 ` Ian Campbell
2016-01-26 17:26   ` Doug Goldstein
2016-01-26 22:36     ` Doug Goldstein
2016-01-27  9:34     ` George Dunlap
2016-01-27  9:44       ` Ian Campbell
2016-01-27  9:45     ` Ian Campbell
2016-01-27 10:55       ` Andrew Cooper
2016-01-27 11:21         ` George Dunlap
2016-01-27 15:18           ` Lars Kurth
2016-01-27 15:45             ` Ian Campbell
2016-01-27 16:01               ` George Dunlap
2016-01-27 16:14                 ` Ian Campbell
2016-02-03 15:38             ` Doug Goldstein [this message]

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=56B21EF9.60205@cardoe.com \
    --to=cardoe@cardoe.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=George.Dunlap@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=lars.kurth@citrix.com \
    --cc=xen-devel@lists.xen.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.