xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>,
	Doug Goldstein <cardoe@cardoe.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Lars Kurth <lars.kurth@citrix.com>
Subject: Re: xenbits GitHub mirror?
Date: Wed, 27 Jan 2016 10:55:52 +0000	[thread overview]
Message-ID: <56A8A238.9040009@citrix.com> (raw)
In-Reply-To: <1453887932.25257.55.camel@citrix.com>

On 27/01/16 09:45, Ian Campbell wrote:
> On Tue, 2016-01-26 at 11:26 -0600, Doug Goldstein wrote:
>> On 1/26/16 10:55 AM, Ian Campbell wrote:
>>> On Sat, 2015-12-19 at 14:51 -0600, Doug Goldstein wrote:
>>>> All,
>>>>
>>>> Now I'll start off by saying that "no" is a perfectly acceptable answer
>>>> to this suggestion. Basically I remember at the Xen Developer Summit a
>>>> few people mentioned it being nice if people provided a git tree where
>>>> their branches were available for testing. I was just thinking it might
>>>> be easier for third parties to do that if there was an official Xen
>>>> Project mirror of the main repos on xenbits on GitHub and people could
>>>> fork that repo and make their branch available. Just a thought.
>>> If forking the repo significantly easier than just creating an empty one of
>>> your own and pushing to it? Is the parent repo "important" in some way in
>>> the GH world? (Given that, as George says, we are unlikely to accept
>>> contributions via GH pull requests etc).
>>>
>>> Ian.
>>>
>> Its not easier or different. I just remembered from the Xen Developer
>> Summit that a few people complained that a lot of the patch series
>> posted to the ML really should be available as a repo because they were
>> quite large and hard to review. I see this comment come up over and over
>> on the ML myself as well so I was just trying to lower the barriers to
>> people doing that. I know the reason people don't isn't technical so
>> this isn't really a technical solution but I figured this is more a
>> social thing. GitHub has the ability to mark a repo as a mirror and not
>> allow pull requests or issues, which is what I would recommend. I'm just
>> looking at improving the community aspect. I could create an
>> organization called "xen-mirror" and get it setup and turn it over to
>> the Xen Project.
>>
>> Again, I'm fine with an answer of "no" here. Just trying to pitch out
>> ideas to solve what some see as an irritation.
> I don't think you need anybodies permission to do this if you think it will
> be valuable.

If there is going to be an official github mirror, then it should be
part of github.com/xen-project rather than hosted by a random developer.

FWIW, I am +1 for setting up infrastructure like this, but lets do it
properly.

Lars: Thoughts?

~Andrew

  reply	other threads:[~2016-01-27 10:55 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 [this message]
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

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=56A8A238.9040009@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=cardoe@cardoe.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).