From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] Request to create two new repositories
Date: Tue, 13 Jun 2017 14:15:54 +0200 [thread overview]
Message-ID: <593FD77A.1070904@codethink.co.uk> (raw)
In-Reply-To: <592E5385.6030704@codethink.co.uk>
Hi,
On 31/05/17 07:24, Agustin Benito Bethencourt wrote:
> Hi,
>
> in order to start working on CIP testing Action 2, we will need to
> create a new repository to host tests and another one for logs.
It was requested at the last CIP TSC meeting that I provide further
information for the needed repositories to be approved.
1.- We will need one repository to collect and store existing tests with
Open Source licenses that are not included in the CIP charter.
Name: upstream-kernel-tests
Location: https://gitlab.com/cip-project/cip-testing
2.- We will need a repository to collect the tests developed within the
CIP project, that will be published under CIP approved licenses.
Name: cip-kernel-tests
Location: https://gitlab.com/cip-project
3.- We will need a repository to collect the logs of the reference tests
for each feature. From the compliance perspective, it is uncertain to me
the license that these logs will have since it might be tied up to the
license of the tests and the license of the code being tested. To reduce
the risks I propose to add this repo in the Gitlab third party license
code subgroup, cip-testing.
Name: CIP-kernel-test-logs
Location: https://gitlab.com/cip-project/cip-testing
Please consider this proposal for potential approval.
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
prev parent reply other threads:[~2017-06-13 12:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 5:24 [cip-dev] Request to create two new repositories Agustin Benito Bethencourt
2017-06-13 12:15 ` Agustin Benito Bethencourt [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=593FD77A.1070904@codethink.co.uk \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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