From: Lars Kurth <lars.kurth@citrix.com>
To: Andrew Cooper <Andrew.Cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
Lars Kurth <lars.kurth.xen@gmail.com>,
George Dunlap <dunlapg@umich.edu>,
David Vrabel <david.vrabel@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Anshul Makkar <anshul.makkar@citrix.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: xenbits "official" repo for XTF (was Re: [PATCH 0/2] xtf: add launcher (+1 bugfix)
Date: Fri, 8 Jul 2016 13:42:09 +0000 [thread overview]
Message-ID: <D3A565B5.2B17F%lars.kurth@citrix.com> (raw)
In-Reply-To: <2bf752dc-8be1-4aa2-e636-39b25790d8a4@citrix.com>
On 08/07/2016 14:06, "Andrew Cooper" <andrew.cooper3@citrix.com> wrote:
>On 07/07/16 18:17, Lars Kurth wrote:
>> Alright,
>>
>> it appears we are at an impasse here. Not hosting the code on xenbits as
>> suggested by David, seems to be the worst solution and will benefit
>> no-one.
>>
>>...
>> That should address everyones concern, as far as I can tell from the the
>> e-mail thread. If anyone disagrees, please shout within the next few
>>days.
>>
>> Best Regards
>> Lars
>> P.S.: I moved fixing some of our governance issues towards the top of my
>> TODO list
>
>I have no problem with Ian's earlier suggestion:
Alright. Ian confirmed on IRC that he has no problem either. Which means
the main issue is unblocked and the repo can be created.
>
>> "CI (continuous integration)" is the keyword that many people will
>> have for osstest.
>>
>> I would suggest
>>
>> (This is not the Xen Project's CI / Continuous Integration /
>> automated push gate system. For that, see
>> <a href="wiki">osstest</a>.)
>>
>> or something.
>
>Adding something like that to the XTF documentation is perfectly fine.
>I also have no problem with the other xtf changes in descriptions/etc
>suggested.
That makes perfect sense (but also see below).
>However, OSSTest has always been known as OSSTest (including all
>references in the automated emails), and not as a xen test framework.
>Taking any steps to make OSSTest retroactively searchable as a xen test
>framework is a dumb move, which will only confuse users.
>
>I fully admit that had OSSTest been named differently then I might not
>have chosen XTF as a name, but that didn't happen. Trying to rewrite
>history isn't the answer.
I am not trying to re-write history. Ultimately I don't mind what the
exact description of OSSTEST says, as long as it is accurate, which is why
I said "something along the lines of ...". Right now there is no wiki or
other xenbits documentation about OSSTEST which is outside the git tree
(except for a few blog posts). Which is mainly why I raised this.
Of course you are right that OSSTest is established and people who have
been around for a while know that. The key question is what newcomers who
don't know would search for: and to be honest I don't know. But it seems
reasonable to me that the "OSSTEST" page should come up when googling for
a combination/sub-set of the following keywords: "test", "xen",
"Continuous Integration", "CI", "suite", "push-gate" and maybe
"framework".
Lars
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-07-08 13:42 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 13:46 [PATCH 0/2] xtf: add launcher (+1 bugfix) Roger Pau Monne
2016-05-19 13:46 ` [PATCH 1/2] xtf: remove setting ROOT path in common.mk Roger Pau Monne
2016-05-19 13:52 ` Andrew Cooper
2016-05-19 13:46 ` [PATCH 2/2] xtf: add a launcher script Roger Pau Monne
2016-06-09 15:04 ` xenbits "official" repo for XTF (was Re: [PATCH 0/2] xtf: add launcher (+1 bugfix) Ian Jackson
2016-06-13 8:59 ` George Dunlap
2016-06-13 10:10 ` Andrew Cooper
2016-06-13 14:03 ` George Dunlap
2016-06-13 14:11 ` Ian Jackson
2016-06-14 17:27 ` Andrew Cooper
2016-06-15 8:31 ` George Dunlap
2016-06-20 17:03 ` Ian Jackson
2016-06-20 17:10 ` Konrad Rzeszutek Wilk
2016-06-21 10:17 ` Wei Liu
2016-06-21 10:36 ` David Vrabel
2016-06-21 10:42 ` Ian Jackson
2016-07-01 19:04 ` Ian Jackson
2016-07-06 11:19 ` Lars Kurth
2016-07-06 14:22 ` Konrad Rzeszutek Wilk
2016-07-07 11:10 ` Lars Kurth
2016-07-07 11:26 ` Andrew Cooper
2016-07-07 13:59 ` Ian Jackson
2016-07-07 14:02 ` David Vrabel
2016-07-07 14:58 ` Ian Jackson
2016-07-07 15:00 ` Ian Jackson
2016-07-07 14:11 ` Andrew Cooper
2016-07-07 17:17 ` Lars Kurth
2016-07-08 13:06 ` Andrew Cooper
2016-07-08 13:42 ` Lars Kurth [this message]
2016-07-08 13:48 ` Andrew Cooper
2016-07-12 15:13 ` George Dunlap
2016-07-15 10:21 ` Ian Jackson
2016-07-15 10:49 ` Lars Kurth
2016-07-18 14:36 ` Ian Jackson
2016-07-18 15:19 ` Lars Kurth
2016-07-18 15:30 ` Ian Jackson
2016-07-18 15:36 ` Lars Kurth
2016-07-18 15:58 ` Ian Jackson
2016-07-18 16:06 ` Lars Kurth
2016-07-18 15:31 ` Ian Jackson
2016-08-08 17:04 ` Ian Jackson
2016-07-07 15:22 ` Konrad Rzeszutek Wilk
2016-06-14 17:01 ` Konrad Rzeszutek Wilk
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=D3A565B5.2B17F%lars.kurth@citrix.com \
--to=lars.kurth@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=anshul.makkar@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=dunlapg@umich.edu \
--cc=lars.kurth.xen@gmail.com \
--cc=roger.pau@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).