Re: [legal-discuss] Tracking Openstack Contributions
Thank you Stefano. I am adding the legal team. Gregg Nardozza [alu-logo-20x20] DMTS - IP Business Development Senior Patent Segment Manager Intellectual Property Business Group Bell Laboratories / Alcatel-Lucent • gregg.nardozza@alcatel-lucent.com<mailto:gregg.nardozza@alcatel-lucent.com> This message, intended only for the designated recipient(s), is privileged and confidential. It is intended only for the review of the party to whom it is addressed. If you are not a designated recipient, you may not review, copy or distribute this message. If you receive this in error, please notify the sender by reply e-mail and delete this message. Unintended transmission shall not constitute waiver of the attorney-client privilege or any other privileges. -----Original Message----- From: Stefano Maffulli [mailto:stefano@openstack.org] Sent: Thursday, April 30, 2015 2:25 PM To: Nardozza, Gregg (Gregg) Subject: Re: Tracking Openstack Contributions Hi Gregg, just a clarification: the website stackalytics.com is not managed by OpenStack Foundation nor it's managed by the OpenStack project. Formally the domain is owned by Mirantis and the development is sponsored mostly by the same company. There is an intention to move all the code and data under the wider openstack community umbrella but no plans nor deadlines have been defined. The Foundation extracts records of contributions from the tools used for openstack development (gerrit, launchpad, git, storyboard, mailing lists, etc) and provides that data on http://activity.openstack.org. Regarding the retention policy, I'm not aware of one formal policy for data retention. I would ask the question on legal-discuss@lists.openstack.org<mailto:legal-discuss@lists.openstack.org> to get the ball moving towards creating one. Cheers, stef On Thu, 2015-04-30 at 12:07 +0000, Nardozza, Gregg (Gregg) wrote:
Hello Stefano!
I need to know the record retention policy for OpenStack.
We (Alcatel-Lucent) rely on being able to retrieve the information as
shown below from the OpenStack website and need to know the number of
years these records will be publically available and retrievable.
Please let me know who would have this information in the OpenStack
organization or pass this on to whom ever can answer these questions
for me.
Much appreciated.
Gregg Nardozza alu-logo-20x20
DMTS - IP Business Development
Senior Patent Segment Manager
Intellectual Property Business Group
Bell Laboratories / Alcatel-Lucent
*gregg.nardozza@alcatel-lucent.com<mailto:*gregg.nardozza@alcatel-lucent.com>
This message, intended only for the designated recipient(s), is
privileged and confidential. It is intended only for the review of the
party to whom it is addressed. If you are not a designated recipient,
you may not review, copy or distribute this message. If you receive
this in error, please notify the sender by reply e-mail and delete
this message. Unintended transmission shall not constitute waiver of
the attorney-client privilege or any other privileges.
From: MARGOLIN, Udi (Udi)
Sent: Thursday, April 30, 2015 7:53 AM
To: Nardozza, Gregg (Gregg)
Subject: RE: Tracking Openstack Contributions
You have it all – take for example ‘lbortman’ – follow the link:
Now you get :
If you follow a specific change ID you get all the details:
Hi Gregg, I think this is outside the de facto remit of this mailing list but I would suggest contacting Jonathan Bryce. Richard On Thu, Apr 30, 2015 at 06:27:58PM +0000, Nardozza, Gregg (Gregg) wrote:
Thank you Stefano.
I am adding the legal team.
Gregg Nardozza alu-logo-20x20
DMTS - IP Business Development
Senior Patent Segment Manager
Intellectual Property Business Group
Bell Laboratories / Alcatel-Lucent
* gregg.nardozza@alcatel-lucent.com
This message, intended only for the designated recipient(s), is privileged and confidential. It is intended only for the review of the party to whom it is addressed. If you are not a designated recipient, you may not review, copy or distribute this message. If you receive this in error, please notify the sender by reply e-mail and delete this message. Unintended transmission shall not constitute waiver of the attorney-client privilege or any other privileges.
-----Original Message----- From: Stefano Maffulli [mailto:stefano@openstack.org] Sent: Thursday, April 30, 2015 2:25 PM To: Nardozza, Gregg (Gregg) Subject: Re: Tracking Openstack Contributions
Hi Gregg,
just a clarification: the website stackalytics.com is not managed by OpenStack Foundation nor it's managed by the OpenStack project. Formally the domain is owned by Mirantis and the development is sponsored mostly by the same company. There is an intention to move all the code and data under the wider openstack community umbrella but no plans nor deadlines have been defined.
The Foundation extracts records of contributions from the tools used for openstack development (gerrit, launchpad, git, storyboard, mailing lists, etc) and provides that data on http://activity.openstack.org.
Regarding the retention policy, I'm not aware of one formal policy for data retention. I would ask the question on legal-discuss@lists.openstack.org to get the ball moving towards creating one.
Cheers,
stef
On Thu, 2015-04-30 at 12:07 +0000, Nardozza, Gregg (Gregg) wrote:
Hello Stefano!
I need to know the record retention policy for OpenStack.
We (Alcatel-Lucent) rely on being able to retrieve the information as
shown below from the OpenStack website and need to know the number of
years these records will be publically available and retrievable.
Please let me know who would have this information in the OpenStack
organization or pass this on to whom ever can answer these questions
for me.
Much appreciated.
Gregg Nardozza alu-logo-20x20
DMTS - IP Business Development
Senior Patent Segment Manager
Intellectual Property Business Group
Bell Laboratories / Alcatel-Lucent
*gregg.nardozza@alcatel-lucent.com
This message, intended only for the designated recipient(s), is
privileged and confidential. It is intended only for the review of the
party to whom it is addressed. If you are not a designated recipient,
you may not review, copy or distribute this message. If you receive
this in error, please notify the sender by reply e-mail and delete
this message. Unintended transmission shall not constitute waiver of
the attorney-client privilege or any other privileges.
From: MARGOLIN, Udi (Udi)
Sent: Thursday, April 30, 2015 7:53 AM
To: Nardozza, Gregg (Gregg)
Subject: RE: Tracking Openstack Contributions
You have it all – take for example ‘lbortman’ – follow the link:
Now you get :
If you follow a specific change ID you get all the details:
_______________________________________________ legal-discuss mailing list legal-discuss@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss
On Thu, 2015-04-30 at 14:42 -0400, Richard Fontana wrote:
I think this is outside the de facto remit of this mailing list but I would suggest contacting Jonathan Bryce.
My bad, I thought the question was interesting for a wider discussion on list. I've always assumed that for community generated content there was no retention policy and there could never be one: repositories come and go, you can't count on some software repository to always be available. So if you need it, you clone it because you can and the license allows you to. For the data I produce I assume the same thing: it's available as-is, no promise made on its quality or availability. If you want it, you clone it and keep the pieces. Does that need to be spelled out in a formal policy? I've contacted Jonathan anyway. thanks, stef
On 04/30/2015 08:58 PM, Stefano Maffulli wrote:
On Thu, 2015-04-30 at 14:42 -0400, Richard Fontana wrote:
I think this is outside the de facto remit of this mailing list but I would suggest contacting Jonathan Bryce.
My bad, I thought the question was interesting for a wider discussion on list.
I agree - I think it's an interesting topic.
I've always assumed that for community generated content there was no retention policy and there could never be one: repositories come and go, you can't count on some software repository to always be available. So if you need it, you clone it because you can and the license allows you to.
Actually - I think it's worthwhile to point out that we do have a formal policy about this. The OpenStack project has never and will never delete a source code repository, nor a commit from a source code repository. Once you have uploaded a change to our system, it will be there for forever. All of the data in stackalytics and activity.o.o is derived from gerrit, and should something happen to either, reconstructing that data from the original source is completely possible. Also, as stef points out, stackalytics is not currently run by the project, although we do have plans to move it under the umbrella. It does, however, host its source code in stackforge. Also, it stores no data locally - it has a memcached server for caching and otherwise re-calculates all of its data on a regular basis directly from gerrit.
For the data I produce I assume the same thing: it's available as-is, no promise made on its quality or availability. If you want it, you clone it and keep the pieces.
Does that need to be spelled out in a formal policy?
I've contacted Jonathan anyway.
thanks, stef
_______________________________________________ legal-discuss mailing list legal-discuss@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/legal-discuss
On Thu, 2015-04-30 at 21:50 +0200, Monty Taylor wrote:
Actually - I think it's worthwhile to point out that we do have a formal policy about this.
The OpenStack project has never and will never delete a source code repository, nor a commit from a source code repository. Once you have uploaded a change to our system, it will be there for forever.
Forever is a strong word. Probably safer to say 'until the legal organization exists and has money to pay for the hosting bills' or something similar :) Do you have a pointer to the promise not to delete repositories?
All of the data in stackalytics and activity.o.o is derived from gerrit, and should something happen to either, reconstructing that data from the original source is completely possible.
Indeed. I guess the legal-ish issue is whether we should put a disclaimer somewhere saying the data on [stackalytics|activity boars] is provided as-is with no promise that it is a) accurate b) will be there forever. We try our best keep the systems running, though. If you need specific SLAs follow the instructions to run the systems yourself. Do we need to spell this out or leaving it implied is enough? /stef
participants (4)
-
Monty Taylor
-
Nardozza, Gregg (Gregg)
-
Richard Fontana
-
Stefano Maffulli