cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Kinsella <...@stratosec.co>
Subject Re: [VOTE] Accept a donation of "Documentation for various features" from Citrix
Date Fri, 18 Jan 2013 19:24:51 GMT
+1 (binding)

On Jan 17, 2013, at 9:48 AM, Animesh Chaturvedi <animesh.chaturvedi@citrix.com> wrote:

> Reposting with subject line VOTE.
> 
> Committers have binding votes for this decision.
> 
> Please respond with your vote:
> +1 - Accept the donation and begin the process of bringing this 
> +enhancement to CloudStack
> in via the IP clearance process
> +0 - Don't care
> -1 - Do not accept the donation
> 
> This vote will remain open for ~72 hours.
> 
> Content Location: http://people.apache.org/~jtomechak
> 
> 	
>> -----Original Message-----
>> From: Jessica Tomechak [mailto:Jessica.Tomechak@citrix.com]
>> Sent: Tuesday, January 15, 2013 7:05 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: RE: [IP Clearance] Potential issues
>> 
>> On people.apache.org/~jtomechak, I have posted all my docs related to the bug
>> items in the IP Clearance list which Animesh provided.
>> 
>> I have made notations in the Doc sub-task of each bug, so that anyone
>> reviewing the proposed feature can easily find the documentation.
>> 
>> In addition, I made a note for myself of the doc status of each bug in that list,
>> and here it is for anyone who is interested!
>> 
>> CLOUDSTACK-774 :
>> Code in ACS repo: No
>> Functional Spec Posted: Yes
>> Community Discussion Done: Yes
>> Contribution Size Approx: 5000 lines
>> Contributor : Frank
>> IP Clearance needed initial recommendation: Yes
>> Docs: None exist. This was not announced or supported as a Citrix CP 3.0.6
>> feature.
>> 
>> 
>> CLOUDSTACK-306 :
>> Code in ACS repo: Yes
>> Functional Spec Posted: Yes
>> Community Discussion Done: Yes in October Contribution Size Approx: 1500
>> lines Contributor : Sheng IP Clearance needed initial recommendation: Yes
>> Docs: Already submitted via reviewboard. Link and info in doc subtask.
>> 
>> 
>> CLOUDSTACK-777/700 :
>> Code in ACS repo: Yes
>> Functional Spec Posted: No
>> Community Discussion Done: Yes
>> Contribution Size Approx: 500 lines
>> Contributor : Kishan/Jayapal/Rajesh/Murali IP Clearance needed initial
>> recommendation: Yes
>> Docs: Pending on reviewboard. URL and notations in the doc subtask of the bug.
>> 
>> CLOUDSTACK-778/319 :
>> Code in ACS repo: No
>> Functional Spec Posted: No
>> Community Discussion Done: Yes
>> Contribution Size Approx: should be small Contributor : Vijayendra IP Clearance
>> needed initial recommendation: This is a trivial issue so may be no
>> Docs: Pending on reviewboard. Info is in the doc subtask of the bug.
>> 
>> CLOUDSTACK-299 :
>> Code in ACS repo: UI code is there but backend is not Functional Spec Posted:
>> Yes Community Discussion Done: Yes Contribution Size Approx: 1400 lines
>> Contributor : Jayapal IP Clearance needed initial recommendation: Yes
>> Docs: Pending on reviewboard. Link is provided in the description of the bug.
>> 
>> CLOUDSTACK-297 :
>> Code in ACS repo: No, but posted on review board Functional Spec Posted: Yes
>> Community Discussion Done: Yes Contribution Size Approx: 350 lines
>> Contributor : Hari IP Clearance needed initial recommendation:
>> Docs: One paragraph of new docs on people.a.o. The URL is noted in the doc
>> subtask of the bug. http://people.apache.org/~jtomechak/CLOUDSTACK-297/
>> 
>> 
>> CLOUDSTACK-197 :
>> Code in ACS repo: Multiple patches posted on review board Functional Spec
>> Posted: Yes Community Discussion Done: Yes Contribution Size Approx: 3000
>> lines Contributor : Likitha IP Clearance needed initial recommendation: No,
>> since incremental patches were posted over a period
>> Docs: Believe docs already exist, authored on the community side by Sebastien
>> G.
>> 
>> CLOUDSTACK-192 :
>> Code in ACS repo: No
>> Functional Spec Posted: Yes
>> Community Discussion Done: Yes, but no consensus reached Contribution Size
>> Approx: 1000 lines Contributor : Sanjay IP Clearance needed initial
>> recommendation: Yes, if community agrees to feature inclusion
>> Docs: On people.a.o. The URL is noted in the doc subtask of the bug.
>> http://people.apache.org/~jtomechak/CLOUDSTACK-192/
>> 
>> 
>> CLOUDSTACK-304 / 784 :
>> Code in ACS repo: Yes
>> Functional Spec Posted: Yes
>> Community Discussion Done: Yes
>> Contribution Size Approx: 600
>> Contributor : Alena
>> IP Clearance needed initial recommendation: No, since commits were done
>> way back in October over a period of 1 week
>> Docs: On people.a.o. The URL is noted in the doc subtask of the bug.
>> http://people.apache.org/~jtomechak/CLOUDSTACK-737/
>> 
>> CLOUDSTACK-265 :
>> Code in ACS repo: Yes
>> Functional Spec Posted: Yes
>> Community Discussion Done: Yes
>> Contribution Size Approx: 450
>> Contributor : Murali
>> IP Clearance needed initial recommendation: Yes
>> Docs: Pending on reviewboard. URL is noted in the doc subtask of the bug.
>> 
>> CLOUDSTACK-737 :
>> Code in ACS repo: No
>> Functional Spec Posted: Yes
>> Community Discussion Done: Yes
>> Contribution Size Approx: 2000
>> Contributor : Anthony
>> IP Clearance needed initial recommendation: Yes
>> Docs: On people.a.o. The URL is noted in the doc subtask of the bug.
>> http://people.apache.org/~jtomechak/CLOUDSTACK-737/
>> 
>> 
>> CLOUDSTACK-177 :
>> Code in ACS repo: Yes
>> Functional Spec Posted: Yes
>> Community Discussion Done: Yes
>> Contribution Size Approx: 300
>> Contributor : Brian
>> IP Clearance needed initial recommendation: No, multiple commits over
>> several days
>> Docs: None were written, probably none needed
>> 
>> CLOUDSTACK-662 :
>> Code in ACS repo: Yes
>> Functional Spec Posted: Yes
>> Community Discussion Done: Yes
>> Contribution Size Approx: 500
>> Contributor : Brian
>> IP Clearance needed initial recommendation: No, multiple commits over
>> several days
>> Docs: None were written, probably none needed
>> 
>> CLOUDSTACK-176 :
>> Code in ACS repo: Yes
>> Functional Spec Posted: Yes
>> Community Discussion Done: Yes
>> Contribution Size Approx: 200
>> Contributor : Pranav
>> IP Clearance needed initial recommendation: No, multiple commits over
>> several days
>> Docs: None needed
>> 
>> 
>> CLOUDSTACK-312 :
>> Code in ACS repo: Yes
>> Functional Spec Posted: Yes
>> Community Discussion Done: Yes
>> Contribution Size Approx:
>> Contributor : Murali
>> IP Clearance needed initial recommendation: Potentially yes, multiple commits
>> in one day
>> Docs: Pending on reviewboard. The URL is noted in the Doc subtask of the bug.
>> 
>> 
>> CLOUDSTACK-873 :
>> Code in ACS repo: No
>> Functional Spec Posted: No
>> Community Discussion Done: No
>> Contribution Size Approx: Work not started Contributor : Vijayendra/ Kelven IP
>> Clearance needed initial recommendation: No as work has not started on it yet.
>> Preliminary investigation done, running into issues with vmware.
>> Docs: No existing docs.
>> 
>> 
>> Jessica Tomechak
>> 
>> -----Original Message-----
>> From: Animesh Chaturvedi [mailto:animesh.chaturvedi@citrix.com]
>> Sent: Tuesday, January 15, 2013 12:25 PM
>> To: cloudstack-dev@incubator.apache.org
>> Subject: RE: [IP Clearance] Potential issues
>> 
>> I am waiting for code to be posted to start the IP clearance process for the ones
>> identified in my email. Let me send reminders.
>> 
>>> -----Original Message-----
>>> From: Chip Childers [mailto:chip.childers@sungard.com]
>>> Sent: Tuesday, January 15, 2013 12:19 PM
>>> To: cloudstack-dev@incubator.apache.org
>>> Subject: Re: [IP Clearance] Potential issues
>>> 
>>> On Mon, Jan 14, 2013 at 6:53 PM, Animesh Chaturvedi
>>> <animesh.chaturvedi@citrix.com> wrote:
>>>> To keep the community posted on status on IP clearance. I have
>>>> followed up
>>> with the contributors of the issues mentioned, as soon as the code is
>>> posted publicly, we will start the IP clearance review process.
>>>> 
>>>> Thanks
>>>> Animesh
>>> 
>>> Animesh (others) - are there any challenges that you need help with in
>>> getting this done?
> 

Stratosec - Secure Infrastructure as a Service
o: 415.315.9385
@johnlkinsella


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message