[GitHub] cloudstack issue #1741: Updated StrongSwan VPN Implementation

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1741
  
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-474


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: PRs for 4.10

[Daan Hoogland]

About 1741, I started the packaging, Will but saw Boris making a
remark about the system VMs. I'll look into that and start the tests.

On Tue, Feb 7, 2017 at 8:19 PM, Will Stevens  wrote:
> I would like to get 1741(strongswan) in, but I need to get Trillian to run
> against it with a system vm built from my pr. I have done a CI in bubble
> and it came back clean, but would like confirmation through Trillian as
> well.
>
> On Feb 7, 2017 2:17 PM, "Milamber"  wrote:
>
>>
>> And this PR for 4.9 but need to be foward to 4.10 too.
>>
>> https://github.com/apache/cloudstack/pull/1929
>>
>> 2 LGTM
>> CI green
>>
>>
>> On 07/02/2017 13:07, Rajani Karuturi wrote:
>>
>>> Hi all,
>>> If you know of any PRs which meet the below criteria, please mail them to
>>> me.
>>> 1. No open questions.
>>> 2. Has two LGTMs
>>> 3. Has CI test results.
>>>
>>> ~Rajani
>>> http://cloudplatform.accelerite.com
>>>
>>>
>>



-- 
Daan

Re:PRs for 4.10

[Haijiao]

Expect the following PRs to be merged into 4.10,  thanks !


PR #1929CLOUDSTACK-9770: fix missing ip routes in VR,   
  2 LGTM ready
PR #1915CLOUDSTACK-9746 system-vm: logrotate config causes critical 
failures1 LGTM ready, just need CI test
PR #1727CLOUDSTACK-9539: Support changing Service offering for instance 
with VM Snapshots   2 LGTM ready
PR #1903CLOUDSTACK-9356: FIX Cannot add users in VPC VPN
  waiting for review
PR #1829CLOUDSTACK-9363: Fix HVM VM restart bug in XenServer
 waiting for review
PR #1849CLOUDSTACK-9690: Scale CentOS7 VM fails with error  
  waiting for review


Regards,


在2017年02月07 21时07分, "Rajani Karuturi"写道:

Hi all,
If you know of any PRs which meet the below criteria, please mail them to
me.
1. No open questions.
2. Has two LGTMs
3. Has CI test results.

~Rajani
http://cloudplatform.accelerite.com

[GitHub] cloudstack issue #1741: Updated StrongSwan VPN Implementation

[blueorangutan]

Github user blueorangutan commented on the issue:

https://github.com/apache/cloudstack/pull/1741
  
@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep 
you posted as I make progress.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1741: Updated StrongSwan VPN Implementation

[DaanHoogland]

Github user DaanHoogland commented on the issue:

https://github.com/apache/cloudstack/pull/1741
  
@blueorangutan package


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1697: CLOUDSTACK-4858 Honors the snapshot.backup.rightafte...

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1697
  
merging this to 4.9+ branches


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1644: Honors the snapshot.backup.rightafter configuration ...

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1644
  
A separate PR for master is not required. #1697 will be forward merged.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1905: CLOUDSTACK-9738: [Vmware] Optimize vm expunge...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/1905


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1905: CLOUDSTACK-9738: [Vmware] Optimize vm expunge proces...

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1905
  
Thanks for the clarification. Its a nice enhancement. LGTM for the changes.
Marvin tests are always welcome :) 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1767: CLOUDSTACK-9457: Allow retrieval and modifica...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/1767


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1892: CLOUDSTACK-9731: Hardcoded label appears on t...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack/pull/1892


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1892: CLOUDSTACK-9731: Hardcoded label appears on the Add ...

[karuturi]

Github user karuturi commented on the issue:

https://github.com/apache/cloudstack/pull/1892
  
trivial. merged


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: PRs for 4.10

[Wido den Hollander]

A small bugfix for IPv6 in Basic Networking: 
https://github.com/apache/cloudstack/pull/1927

Would be great!

Wido

> Op 7 feb. 2017 om 14:08 heeft Rajani Karuturi  het 
> volgende geschreven:
> 
> Hi all,
> If you know of any PRs which meet the below criteria, please mail them to
> me.
> 1. No open questions.
> 2. Has two LGTMs
> 3. Has CI test results.
> 
> ~Rajani
> http://cloudplatform.accelerite.com

[GitHub] cloudstack issue #1892: CLOUDSTACK-9731: Hardcoded label appears on the Add ...

[sureshanaparti]

Github user sureshanaparti commented on the issue:

https://github.com/apache/cloudstack/pull/1892
  
@koushik-das, UI screenshots of hardcoded label on the Add zone wizard and 
the UI fix for it are attached. Please check.


![hardcoded_label](https://cloud.githubusercontent.com/assets/12028987/22725141/4aefc006-edf1-11e6-9ea2-69b254dda030.jpg)


![fixed_hardcoded_label](https://cloud.githubusercontent.com/assets/12028987/22725179/bd234c42-edf1-11e6-8a9c-3aa4f4c44b2a.jpg)



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1900: CLOUDSTACK-8862: Introduced new state attachi...

[anshul1886]

GitHub user anshul1886 reopened a pull request:

https://github.com/apache/cloudstack/pull/1900

CLOUDSTACK-8862: Introduced new state attaching for volume. This will…

… make sure that other attach operation on same volume will fail 
gracefully without calling access calls for managed storage like SolidFire

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/anshul1886/cloudstack-1 CLOUDSTACK-8862

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/cloudstack/pull/1900.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1900


commit 40d1a82bd9b7e799f269fcfbdfc4ec5923c189b2
Author: Anshul Gangwar 
Date:   2017-01-10T11:40:28Z

CLOUDSTACK-8862: Introduced new state attaching for volume. This will make 
sure that other attach operation on same volume will fail gracefully without 
calling access calls for managed storage like SolidFire




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack pull request #1900: CLOUDSTACK-8862: Introduced new state attachi...

[anshul1886]

Github user anshul1886 closed the pull request at:

https://github.com/apache/cloudstack/pull/1900


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack-docs-admin pull request #41: 50% of the doc strings are translate...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack-docs-admin/pull/41


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: PRs for 4.10

[Will Stevens]

I got my Jenkins fixed today. I will run tests against my bubble env
tonight and we can go with that if Trillian can not do a systemvm template
from the PR for this one.

On Feb 7, 2017 7:16 PM, "Rajani Karuturi"  wrote:

> @milamber I will soon merge the localization PRs
>
> @will Yes. that would be great addition to 4.10. Its pending from
> a long time.
>
> @sergey 1913 has open questions. Can you answer them please? rest
> I will take a look.
>
> PS: based on the pattern(17*[0,2,4,8,]7) I also checked 1707. I
> will add it to my PR list :)
>
> Thanks,
>
> ~ Rajani
>
> http://cloudplatform.accelerite.com/
>
> On February 8, 2017 at 2:23 AM, Sergey Levitskiy
> (sergey.levits...@autodesk.com) wrote:
>
> I would like to include :
> PR1727 CLOUDSTACK-9539: Support changing Service offering for
> instance with VM Snapshots
> PR1747 CLOUDSTACK-9574: Redesign storage views
> PR1767 CLOUDSTACK-9457: Allow retrieval and modification of VM
> and template details via API and UI
> They have all tests green and just need another LGTM
>
> 2 optimization PRs will be nice to add as well:
> PR1905 CLOUDSTACK-9738: [Vmware] Optimize vm expunge process for
> instances with vm snapshots
> PR1913 CLOUDSTACK-9752: [Vmware] Optimization of volume
> attachment to vm

Re: PRs for 4.10

[Rajani Karuturi]

@milamber I will soon merge the localization PRs

@will Yes. that would be great addition to 4.10. Its pending from
a long time.

@sergey 1913 has open questions. Can you answer them please? rest
I will take a look.

PS: based on the pattern(17*[0,2,4,8,]7) I also checked 1707. I
will add it to my PR list :)

Thanks,

~ Rajani

http://cloudplatform.accelerite.com/

On February 8, 2017 at 2:23 AM, Sergey Levitskiy
(sergey.levits...@autodesk.com) wrote:

I would like to include :
PR1727 CLOUDSTACK-9539: Support changing Service offering for
instance with VM Snapshots
PR1747 CLOUDSTACK-9574: Redesign storage views
PR1767 CLOUDSTACK-9457: Allow retrieval and modification of VM
and template details via API and UI
They have all tests green and just need another LGTM

2 optimization PRs will be nice to add as well:
PR1905 CLOUDSTACK-9738: [Vmware] Optimize vm expunge process for
instances with vm snapshots
PR1913 CLOUDSTACK-9752: [Vmware] Optimization of volume
attachment to vm

[GitHub] cloudstack issue #1747: CLOUDSTACK-9574: Redesign storage views

[rafaelweingartner]

Github user rafaelweingartner commented on the issue:

https://github.com/apache/cloudstack/pull/1747
  
@serg38 got it. 
Thanks for the explanation


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1747: CLOUDSTACK-9574: Redesign storage views

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1747
  
@rafaelweingartner This PR is two fold.
1. This is something that was done a long ago for hosts and was never 
implemented for storage. It  transitions location of  of storage tags over to 
dedicated tables (storage_pool_tags) and converts current storage_tags to the 
new location so there should be no impact on current installation
2. For secondary storage there is no need to show details since they are 
coming from configurations  that now support ImageStore as Scope via PR1615. 
With that Details tag becomes obsolete.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1747: CLOUDSTACK-9574: Redesign storage views

[rafaelweingartner]

Github user rafaelweingartner commented on the issue:

https://github.com/apache/cloudstack/pull/1747
  
@nvazquez, @serg38, before checking code any deeper a have a more 
high-level question.

This PR will change the response of an API method, right? It will remove 
some data that today is being delivered to users. 

If I understood it properly, this data (storage tags) will be 
delivered/retrieved using another method. This may break compatibility with 
current clients that may use this information. If so, this break in 
compatibility has to be properly documented. Do you guys know how we could do 
this? Is there a protocol for this? Some alert on the release notes? Or maybe 
something on documentation pages?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1767: CLOUDSTACK-9457: Allow retrieval and modification of...

[rafaelweingartner]

Github user rafaelweingartner commented on the issue:

https://github.com/apache/cloudstack/pull/1767
  
I have just reviewed the PR. There are only small suggestions I made.

BTW: from the Jira ticket 
https://issues.apache.org/jira/browse/CLOUDSTACK-9457, I ended up at 
https://issues.apache.org/jira/browse/CLOUDSTACK-9379, which is already done. I 
do not have permission to mark it as done. I believe @nvazquez might have.



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1727: CLOUDSTACK-9539: Support changing Service offering f...

[rafaelweingartner]

Github user rafaelweingartner commented on the issue:

https://github.com/apache/cloudstack/pull/1727
  
Long time I do not review a PR here. I have to say, @nvazquez , great job!!
@serg38 you read my mind!! I had just started reading @nvazquez PR 
description when you called me.

Well documented methods. The methods are short and concise. The code is 
clear and looks nice (at least for me).

I jumped over the 70+ messages here. So, excuse me if I ask something that 
has already been clarified before.

However, as always I have something to complain; I might be getting old, 
that is probably why :) . Just teasing; it is more like a set of suggestion;

* On VMSnapshotVO, what about declaring the instance attribute you create 
as private? I know the others are not, and at the end of the day, it does not 
change much. However, as long as we are using Java and if we consider 
“VMSnapshotVO” as a POJO, then it feels a good idea to use private 
attributes that are only accessible to their gets/sets.
* On VMSnapshotManagerImpl, here we have a “service” layer 
object/component. I would have the same suggestion regarding the use of 
private/protected attributes here (this is cosmetics).
* Still on VMSnapshotManagerImpl, what about extracting the code from lines 
358-373 to a method? This may enable you to write unit test cases for these 
lines.
* Also on VMSnapshotManagerImpl, methods 
“addSupportForCustomServiceOffering”, “updateUserVmServiceOffering”, 
“getVmMapDetails”, “changeUserVmServiceOffering”, 
revertUserVmDetailsFromVmSnapshot, and “ugradeUserVmServiceOffering” are 
clean and well documented. However, I am missing their test cases. What about 
some test cases here, then it would be awesome.
* on VMSnapshotManagerImpl, the method “ugradeUserVmServiceOffering” 
seems to have a typo mistake ;)
* the method “revertUserVmDetailsFromVmSnapshot” receives a parameter 
“userVm”, but it does not seem to be used.

I am assuming you have executed the functional test 
“test_vm_snapshots.py” and it passed successfully, right?

Very good feature to be added. Thanks for the valuable contribution to ACS 
👍 





---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: PRs for 4.10

[Sergey Levitskiy]

I would like to include :   
PR1727 CLOUDSTACK-9539: Support changing Service offering for instance with VM 
Snapshots
PR1747 CLOUDSTACK-9574: Redesign storage views
PR1767 CLOUDSTACK-9457: Allow retrieval and modification of VM and template 
details via API and UI
They have all tests green and just need  another LGTM

2 optimization PRs will be nice to add as well:
PR1905 CLOUDSTACK-9738: [Vmware] Optimize vm expunge process for instances with 
vm snapshots
PR1913 CLOUDSTACK-9752: [Vmware] Optimization of volume attachment to vm

[GitHub] cloudstack issue #1767: CLOUDSTACK-9457: Allow retrieval and modification of...

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1767
  
LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1747: CLOUDSTACK-9574: Redesign storage views

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1747
  
@rafaelweingartner  Can you review this PR? 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1727: CLOUDSTACK-9539: Support changing Service offering f...

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1727
  
@koushik-das @rhtyd @rafaelweingartner  Can you review changes @nvazquez 
put in place? CI tests are good.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack issue #1727: CLOUDSTACK-9539: Support changing Service offering f...

[serg38]

Github user serg38 commented on the issue:

https://github.com/apache/cloudstack/pull/1727
  
LGTM


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: PRs for 4.10

[Will Stevens]

I would like to get 1741(strongswan) in, but I need to get Trillian to run
against it with a system vm built from my pr. I have done a CI in bubble
and it came back clean, but would like confirmation through Trillian as
well.

On Feb 7, 2017 2:17 PM, "Milamber"  wrote:

>
> And this PR for 4.9 but need to be foward to 4.10 too.
>
> https://github.com/apache/cloudstack/pull/1929
>
> 2 LGTM
> CI green
>
>
> On 07/02/2017 13:07, Rajani Karuturi wrote:
>
>> Hi all,
>> If you know of any PRs which meet the below criteria, please mail them to
>> me.
>> 1. No open questions.
>> 2. Has two LGTMs
>> 3. Has CI test results.
>>
>> ~Rajani
>> http://cloudplatform.accelerite.com
>>
>>
>

Re: PRs for 4.10

[Milamber]

And this PR for 4.9 but need to be foward to 4.10 too.

https://github.com/apache/cloudstack/pull/1929

2 LGTM
CI green


On 07/02/2017 13:07, Rajani Karuturi wrote:

Hi all,
If you know of any PRs which meet the below criteria, please mail them to
me.
1. No open questions.
2. Has two LGTMs
3. Has CI test results.

~Rajani
http://cloudplatform.accelerite.com

Re: PRs for 4.10

[Milamber]

No 2 LGTMs, but this PR only updated the localization files for 4.10 
(green on CI)


https://github.com/apache/cloudstack/pull/1914



On 07/02/2017 13:07, Rajani Karuturi wrote:

Hi all,
If you know of any PRs which meet the below criteria, please mail them to
me.
1. No open questions.
2. Has two LGTMs
3. Has CI test results.

~Rajani
http://cloudplatform.accelerite.com

[GitHub] cloudstack-www issue #34: Remove link to “planet.apache.org” and update ...

[rafaelweingartner]

Github user rafaelweingartner commented on the issue:

https://github.com/apache/cloudstack-www/pull/34
  
Changes suggested by @swill applied.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack-www pull request #34: Remove link to “planet.apache.org” and ...

[swill]

Github user swill commented on a diff in the pull request:

https://github.com/apache/cloudstack-www/pull/34#discussion_r99876345
  
--- Diff: README.md ---
@@ -15,14 +15,42 @@ Build the site with:
 To serve it locally:
 
 $ middleman server
-
-IMPORTANT: To publish your changes, commit the build into the asf-site * 
branch *
-
-GOTCHA, *TODO*, the `build` directory needs to be renamed `content` in the 
asf-site branch for the site to be served properly.
-
-*TODO* check the `build.sh` script and make it better, simple build that 
stages all changes to `/content`
-
-Use GitHub PR to make changes.
-
-*TODO* Add gitHUB PR contribution instructions and better build 
instructions for committers
-
+   
+#Building
+To build the HTML files, you just need to execute the `build.sh`. The 
script will automatically generate the HTML files and then move them to the 
`content` folder.
+
+# Commiting 
+Use GitHub PR to make changes. **No one should commit directly to Apache 
remote repositories without opening a PR and waiting for proper review**.
+If you got the feedback and have amended the changes (if needed), it is 
time to **commit** the changes to **Apache Software Foundation (AFS) remote 
repository**. The ASF remote repository for this project is: 
`https://git-wip-us.apache.org/repos/asf/cloudstack-www.git`
+
+**IMPORTANT:** To publish your changes, you should commit into the 
**asf-site** branch (pay attention, this is the name of the branch in the 
remote repository). **Do not forget**, you also have to commit the same changes 
to the master; so, **master** and **asf-site** branches are synchronized.
+
+The **asf-site** branch is synchronized with a web server that delivers 
the Apache CloudStack web pages.
+
+GOTCHA, the `build` directory needs to be renamed to `content` in the 
asf-site branch for the site to be served properly; If you use the `build.sh` 
script, this steep is already taken care of.
+
+## Step by step
+* Fork the repo to your own Github: ``. To do that, you 
can access `https://github.com/apache/cloudstack-www` and click on `fork` on 
the right upper corner of the page.
+* Then, you can clone to you local git repo using: `git clone`; e.g. `git 
clone https://github.com/apache/cloudstack-www.git` or `git clone 
https://github.com//cloudstack-www.git`
+* `cd cloudstack-www`
+* __This step is only required for committers:__ (add the ASF remote repo) 
`git remote add upstream 
https://git-wip-us.apache.org/repos/asf/cloudstack-www.git`
+* if you have cloned  directly from Apache namespace on Github, then you 
need to add your namespace on Github as well, `git remote add 
 https://github.com//cloudstack-www.git`
+* (get the master branch): `git checkout -b master origin/master` or `git 
checkout -b master /master`
+* Now, it is your turn to make the changes you want
+* `middleman build` will build/"compile" the HTML files from the sources
+* ` middleman server [-p ]`. This will serve/deliver your HTML 
files over HTTP. You just gotta access them using a browser; e.g. 
`http://localhost:[port_configured]`. **Check your changes!!**
+* Execute `./build.sh`
+* `git add -A`
+* git commit -am "your commit message"
--- End diff --

`git commit -am "your commit message"` (put in backticks so it shows as a 
command)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack-www pull request #34: Remove link to “planet.apache.org” and ...

[swill]

Github user swill commented on a diff in the pull request:

https://github.com/apache/cloudstack-www/pull/34#discussion_r99876616
  
--- Diff: README.md ---
@@ -15,14 +15,42 @@ Build the site with:
 To serve it locally:
 
 $ middleman server
-
-IMPORTANT: To publish your changes, commit the build into the asf-site * 
branch *
-
-GOTCHA, *TODO*, the `build` directory needs to be renamed `content` in the 
asf-site branch for the site to be served properly.
-
-*TODO* check the `build.sh` script and make it better, simple build that 
stages all changes to `/content`
-
-Use GitHub PR to make changes.
-
-*TODO* Add gitHUB PR contribution instructions and better build 
instructions for committers
-
+   
+#Building
+To build the HTML files, you just need to execute the `build.sh`. The 
script will automatically generate the HTML files and then move them to the 
`content` folder.
+
+# Commiting 
+Use GitHub PR to make changes. **No one should commit directly to Apache 
remote repositories without opening a PR and waiting for proper review**.
+If you got the feedback and have amended the changes (if needed), it is 
time to **commit** the changes to **Apache Software Foundation (AFS) remote 
repository**. The ASF remote repository for this project is: 
`https://git-wip-us.apache.org/repos/asf/cloudstack-www.git`
+
+**IMPORTANT:** To publish your changes, you should commit into the 
**asf-site** branch (pay attention, this is the name of the branch in the 
remote repository). **Do not forget**, you also have to commit the same changes 
to the master; so, **master** and **asf-site** branches are synchronized.
+
+The **asf-site** branch is synchronized with a web server that delivers 
the Apache CloudStack web pages.
+
+GOTCHA, the `build` directory needs to be renamed to `content` in the 
asf-site branch for the site to be served properly; If you use the `build.sh` 
script, this steep is already taken care of.
+
+## Step by step
+* Fork the repo to your own Github: ``. To do that, you 
can access `https://github.com/apache/cloudstack-www` and click on `fork` on 
the right upper corner of the page.
+* Then, you can clone to you local git repo using: `git clone`; e.g. `git 
clone https://github.com/apache/cloudstack-www.git` or `git clone 
https://github.com//cloudstack-www.git`
+* `cd cloudstack-www`
+* __This step is only required for committers:__ (add the ASF remote repo) 
`git remote add upstream 
https://git-wip-us.apache.org/repos/asf/cloudstack-www.git`
+* if you have cloned  directly from Apache namespace on Github, then you 
need to add your namespace on Github as well, `git remote add 
 https://github.com//cloudstack-www.git`
+* (get the master branch): `git checkout -b master origin/master` or `git 
checkout -b master /master`
+* Now, it is your turn to make the changes you want
+* `middleman build` will build/"compile" the HTML files from the sources
+* ` middleman server [-p ]`. This will serve/deliver your HTML 
files over HTTP. You just gotta access them using a browser; e.g. 
`http://localhost:[port_configured]`. **Check your changes!!**
+* Execute `./build.sh`
+* `git add -A`
+* git commit -am "your commit message"
+* git push `` master
--- End diff --

`git push  master` (again in backticks so it formats 
nicely in readme)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack-www pull request #34: Remove link to “planet.apache.org” and ...

[swill]

Github user swill commented on a diff in the pull request:

https://github.com/apache/cloudstack-www/pull/34#discussion_r99875679
  
--- Diff: README.md ---
@@ -15,14 +15,42 @@ Build the site with:
 To serve it locally:
 
 $ middleman server
-
-IMPORTANT: To publish your changes, commit the build into the asf-site * 
branch *
-
-GOTCHA, *TODO*, the `build` directory needs to be renamed `content` in the 
asf-site branch for the site to be served properly.
-
-*TODO* check the `build.sh` script and make it better, simple build that 
stages all changes to `/content`
-
-Use GitHub PR to make changes.
-
-*TODO* Add gitHUB PR contribution instructions and better build 
instructions for committers
-
+   
+#Building
+To build the HTML files, you just need to execute the `build.sh`. The 
script will automatically generate the HTML files and then move them to the 
`content` folder.
+
+# Commiting 
+Use GitHub PR to make changes. **No one should commit directly to Apache 
remote repositories without opening a PR and waiting for proper review**.
+If you got the feedback and have amended the changes (if needed), it is 
time to **commit** the changes to **Apache Software Foundation (AFS) remote 
repository**. The ASF remote repository for this project is: 
`https://git-wip-us.apache.org/repos/asf/cloudstack-www.git`
+
+**IMPORTANT:** To publish your changes, you should commit into the 
**asf-site** branch (pay attention, this is the name of the branch in the 
remote repository). **Do not forget**, you also have to commit the same changes 
to the master; so, **master** and **asf-site** branches are synchronized.
+
+The **asf-site** branch is synchronized with a web server that delivers 
the Apache CloudStack web pages.
+
+GOTCHA, the `build` directory needs to be renamed to `content` in the 
asf-site branch for the site to be served properly; If you use the `build.sh` 
script, this steep is already taken care of.
--- End diff --

s/steep/step/


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack-www pull request #34: Remove link to “planet.apache.org” and ...

[swill]

Github user swill commented on a diff in the pull request:

https://github.com/apache/cloudstack-www/pull/34#discussion_r99877060
  
--- Diff: README.md ---
@@ -15,14 +15,42 @@ Build the site with:
 To serve it locally:
 
 $ middleman server
-
-IMPORTANT: To publish your changes, commit the build into the asf-site * 
branch *
-
-GOTCHA, *TODO*, the `build` directory needs to be renamed `content` in the 
asf-site branch for the site to be served properly.
-
-*TODO* check the `build.sh` script and make it better, simple build that 
stages all changes to `/content`
-
-Use GitHub PR to make changes.
-
-*TODO* Add gitHUB PR contribution instructions and better build 
instructions for committers
-
+   
+#Building
+To build the HTML files, you just need to execute the `build.sh`. The 
script will automatically generate the HTML files and then move them to the 
`content` folder.
+
+# Commiting 
+Use GitHub PR to make changes. **No one should commit directly to Apache 
remote repositories without opening a PR and waiting for proper review**.
+If you got the feedback and have amended the changes (if needed), it is 
time to **commit** the changes to **Apache Software Foundation (AFS) remote 
repository**. The ASF remote repository for this project is: 
`https://git-wip-us.apache.org/repos/asf/cloudstack-www.git`
+
+**IMPORTANT:** To publish your changes, you should commit into the 
**asf-site** branch (pay attention, this is the name of the branch in the 
remote repository). **Do not forget**, you also have to commit the same changes 
to the master; so, **master** and **asf-site** branches are synchronized.
+
+The **asf-site** branch is synchronized with a web server that delivers 
the Apache CloudStack web pages.
+
+GOTCHA, the `build` directory needs to be renamed to `content` in the 
asf-site branch for the site to be served properly; If you use the `build.sh` 
script, this steep is already taken care of.
+
+## Step by step
+* Fork the repo to your own Github: ``. To do that, you 
can access `https://github.com/apache/cloudstack-www` and click on `fork` on 
the right upper corner of the page.
+* Then, you can clone to you local git repo using: `git clone`; e.g. `git 
clone https://github.com/apache/cloudstack-www.git` or `git clone 
https://github.com//cloudstack-www.git`
+* `cd cloudstack-www`
+* __This step is only required for committers:__ (add the ASF remote repo) 
`git remote add upstream 
https://git-wip-us.apache.org/repos/asf/cloudstack-www.git`
+* if you have cloned  directly from Apache namespace on Github, then you 
need to add your namespace on Github as well, `git remote add 
 https://github.com//cloudstack-www.git`
+* (get the master branch): `git checkout -b master origin/master` or `git 
checkout -b master /master`
+* Now, it is your turn to make the changes you want
+* `middleman build` will build/"compile" the HTML files from the sources
+* ` middleman server [-p ]`. This will serve/deliver your HTML 
files over HTTP. You just gotta access them using a browser; e.g. 
`http://localhost:[port_configured]`. **Check your changes!!**
+* Execute `./build.sh`
+* `git add -A`
+* git commit -am "your commit message"
+* git push `` master
+* Check if the changes appear properly on your Github project, and then 
create a PR against the Apache `cloudstack-www` repo.
+* Get feedback on the PR and proceed once PR review is accepted
+* If you are not a committer, your job finishes here. Congratulations you 
have made the Apache CloudStack website better  :thumbsup:
+* Continuing, for committers. Clone or add the repo of our contributor on 
Github using `git remote add  
https://github.com//cloudstack-www.git`
+* git checkout asf-site
+* `git merge /master`; e.g. `git merge 
/master` or `git merge /master`
+* `git log -p`. Check if the changes were properly merged.
+* git push upstream asf-site
+* git push upstream master
--- End diff --

`git push upstream master` (added backticks)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack-www pull request #34: Remove link to “planet.apache.org” and ...

[swill]

Github user swill commented on a diff in the pull request:

https://github.com/apache/cloudstack-www/pull/34#discussion_r99876892
  
--- Diff: README.md ---
@@ -15,14 +15,42 @@ Build the site with:
 To serve it locally:
 
 $ middleman server
-
-IMPORTANT: To publish your changes, commit the build into the asf-site * 
branch *
-
-GOTCHA, *TODO*, the `build` directory needs to be renamed `content` in the 
asf-site branch for the site to be served properly.
-
-*TODO* check the `build.sh` script and make it better, simple build that 
stages all changes to `/content`
-
-Use GitHub PR to make changes.
-
-*TODO* Add gitHUB PR contribution instructions and better build 
instructions for committers
-
+   
+#Building
+To build the HTML files, you just need to execute the `build.sh`. The 
script will automatically generate the HTML files and then move them to the 
`content` folder.
+
+# Commiting 
+Use GitHub PR to make changes. **No one should commit directly to Apache 
remote repositories without opening a PR and waiting for proper review**.
+If you got the feedback and have amended the changes (if needed), it is 
time to **commit** the changes to **Apache Software Foundation (AFS) remote 
repository**. The ASF remote repository for this project is: 
`https://git-wip-us.apache.org/repos/asf/cloudstack-www.git`
+
+**IMPORTANT:** To publish your changes, you should commit into the 
**asf-site** branch (pay attention, this is the name of the branch in the 
remote repository). **Do not forget**, you also have to commit the same changes 
to the master; so, **master** and **asf-site** branches are synchronized.
+
+The **asf-site** branch is synchronized with a web server that delivers 
the Apache CloudStack web pages.
+
+GOTCHA, the `build` directory needs to be renamed to `content` in the 
asf-site branch for the site to be served properly; If you use the `build.sh` 
script, this steep is already taken care of.
+
+## Step by step
+* Fork the repo to your own Github: ``. To do that, you 
can access `https://github.com/apache/cloudstack-www` and click on `fork` on 
the right upper corner of the page.
+* Then, you can clone to you local git repo using: `git clone`; e.g. `git 
clone https://github.com/apache/cloudstack-www.git` or `git clone 
https://github.com//cloudstack-www.git`
+* `cd cloudstack-www`
+* __This step is only required for committers:__ (add the ASF remote repo) 
`git remote add upstream 
https://git-wip-us.apache.org/repos/asf/cloudstack-www.git`
+* if you have cloned  directly from Apache namespace on Github, then you 
need to add your namespace on Github as well, `git remote add 
 https://github.com//cloudstack-www.git`
+* (get the master branch): `git checkout -b master origin/master` or `git 
checkout -b master /master`
+* Now, it is your turn to make the changes you want
+* `middleman build` will build/"compile" the HTML files from the sources
+* ` middleman server [-p ]`. This will serve/deliver your HTML 
files over HTTP. You just gotta access them using a browser; e.g. 
`http://localhost:[port_configured]`. **Check your changes!!**
+* Execute `./build.sh`
+* `git add -A`
+* git commit -am "your commit message"
+* git push `` master
+* Check if the changes appear properly on your Github project, and then 
create a PR against the Apache `cloudstack-www` repo.
+* Get feedback on the PR and proceed once PR review is accepted
+* If you are not a committer, your job finishes here. Congratulations you 
have made the Apache CloudStack website better  :thumbsup:
+* Continuing, for committers. Clone or add the repo of our contributor on 
Github using `git remote add  
https://github.com//cloudstack-www.git`
+* git checkout asf-site
--- End diff --

`git checkout asf-site`  (added backticks)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack-www pull request #34: Remove link to “planet.apache.org” and ...

[swill]

Github user swill commented on a diff in the pull request:

https://github.com/apache/cloudstack-www/pull/34#discussion_r99876990
  
--- Diff: README.md ---
@@ -15,14 +15,42 @@ Build the site with:
 To serve it locally:
 
 $ middleman server
-
-IMPORTANT: To publish your changes, commit the build into the asf-site * 
branch *
-
-GOTCHA, *TODO*, the `build` directory needs to be renamed `content` in the 
asf-site branch for the site to be served properly.
-
-*TODO* check the `build.sh` script and make it better, simple build that 
stages all changes to `/content`
-
-Use GitHub PR to make changes.
-
-*TODO* Add gitHUB PR contribution instructions and better build 
instructions for committers
-
+   
+#Building
+To build the HTML files, you just need to execute the `build.sh`. The 
script will automatically generate the HTML files and then move them to the 
`content` folder.
+
+# Commiting 
+Use GitHub PR to make changes. **No one should commit directly to Apache 
remote repositories without opening a PR and waiting for proper review**.
+If you got the feedback and have amended the changes (if needed), it is 
time to **commit** the changes to **Apache Software Foundation (AFS) remote 
repository**. The ASF remote repository for this project is: 
`https://git-wip-us.apache.org/repos/asf/cloudstack-www.git`
+
+**IMPORTANT:** To publish your changes, you should commit into the 
**asf-site** branch (pay attention, this is the name of the branch in the 
remote repository). **Do not forget**, you also have to commit the same changes 
to the master; so, **master** and **asf-site** branches are synchronized.
+
+The **asf-site** branch is synchronized with a web server that delivers 
the Apache CloudStack web pages.
+
+GOTCHA, the `build` directory needs to be renamed to `content` in the 
asf-site branch for the site to be served properly; If you use the `build.sh` 
script, this steep is already taken care of.
+
+## Step by step
+* Fork the repo to your own Github: ``. To do that, you 
can access `https://github.com/apache/cloudstack-www` and click on `fork` on 
the right upper corner of the page.
+* Then, you can clone to you local git repo using: `git clone`; e.g. `git 
clone https://github.com/apache/cloudstack-www.git` or `git clone 
https://github.com//cloudstack-www.git`
+* `cd cloudstack-www`
+* __This step is only required for committers:__ (add the ASF remote repo) 
`git remote add upstream 
https://git-wip-us.apache.org/repos/asf/cloudstack-www.git`
+* if you have cloned  directly from Apache namespace on Github, then you 
need to add your namespace on Github as well, `git remote add 
 https://github.com//cloudstack-www.git`
+* (get the master branch): `git checkout -b master origin/master` or `git 
checkout -b master /master`
+* Now, it is your turn to make the changes you want
+* `middleman build` will build/"compile" the HTML files from the sources
+* ` middleman server [-p ]`. This will serve/deliver your HTML 
files over HTTP. You just gotta access them using a browser; e.g. 
`http://localhost:[port_configured]`. **Check your changes!!**
+* Execute `./build.sh`
+* `git add -A`
+* git commit -am "your commit message"
+* git push `` master
+* Check if the changes appear properly on your Github project, and then 
create a PR against the Apache `cloudstack-www` repo.
+* Get feedback on the PR and proceed once PR review is accepted
+* If you are not a committer, your job finishes here. Congratulations you 
have made the Apache CloudStack website better  :thumbsup:
+* Continuing, for committers. Clone or add the repo of our contributor on 
Github using `git remote add  
https://github.com//cloudstack-www.git`
+* git checkout asf-site
+* `git merge /master`; e.g. `git merge 
/master` or `git merge /master`
+* `git log -p`. Check if the changes were properly merged.
+* git push upstream asf-site
--- End diff --

`git push upstream asf-site` (added backticks)


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] cloudstack-www issue #34: Remove link to “planet.apache.org” and update ...

[rafaelweingartner]

Github user rafaelweingartner commented on the issue:

https://github.com/apache/cloudstack-www/pull/34
  
Any further thoughts here guys?
@terbolous, @swill, @pdion891 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

PRs for 4.10

[Rajani Karuturi]

Hi all,
If you know of any PRs which meet the below criteria, please mail them to
me.
1. No open questions.
2. Has two LGTMs
3. Has CI test results.

~Rajani
http://cloudplatform.accelerite.com

Re: FW: Google Summer of Code 2017 is coming

[Daan Hoogland]

I have only just started to shift through the list of old wishes, Sachin. I am 
sure there are a lot there that , when not valid as such will provide plenty 
inspiration to think of new ones, Feel free to address Wido and Wei, though 
they are probably very busy. If you have an idea and want to validate it feel 
free to contact me on- or off-list


From: sachin patil 
Sent: 07 February 2017 10:31:13
To: Daan Hoogland
Cc: dev; Giles Sirett
Subject: Re: FW: Google Summer of Code 2017 is coming

Hello Daan,

 I had two particular projects in mind and there are pleny
others as well.

-- One is the ceph project @wido had posted here.

-- The other is Ability to move VM to other project CLOUDSTACK-9737
 ,this issue it
still open ,Wei Zhou did some work on this I guess. I would like to know
its status and if possible work for it.

If you have any other ideas Daan, I would like to discuss them as well.

On Tue, Feb 7, 2017 at 2:46 PM, Daan Hoogland 
wrote:

> Great Sachin,
>
> Do you have a subject in mind? I want to mentor but we may just find
> you an even better mentor based on your preferred subject ;)
>
> On Mon, Feb 6, 2017 at 3:00 PM, Ian Duffy  wrote:
> > I believe Sachin (CCed) was showed interest in becoming a student a
> couple
> > of months back. Might be good to get him and a potential mentor talking.
> >
> > On 6 February 2017 at 10:19, Daan Hoogland 
> > wrote:
> >
> >> I think we should be able to muster some quickly:
> >>
> >> project = CLOUDSTACK AND issuetype in (Improvement, "New Feature", Wish)
> >> AND status = Open AND assignee in (EMPTY)
> >>
> >> leads me to 321 open, unassigned, wishes, improvements and new features
> [image:
> >> ]
> >>
> >>
> >> I'll do some filtering and maybe we can group ideas in this thread
> quickly
> >>
> >> daan.hoogl...@shapeblue.com
> >> www.shapeblue.com
> >> @shapeblue
> >>
> >>
> >>
> >> --
> >> *From:* Daan Hoogland
> >> *Sent:* 06 February 2017 11:02:29
> >> *To:* Giles Sirett; dev@cloudstack.apache.org
> >> *Subject:* Re: FW: Google Summer of Code 2017 is coming
> >>
> >>
> >> I'll do some jira grooming the next couple of days, maybe we find some.
> >> --
> >> *From:* Wido den Hollander 
> >> *Sent:* 06 February 2017 10:59:07
> >> *To:* Giles Sirett; dev@cloudstack.apache.org
> >> *Subject:* Re: FW: Google Summer of Code 2017 is coming
> >>
> >>
> >> > Op 6 februari 2017 om 9:51 schreef Giles Sirett <
> >> giles.sir...@shapeblue.com>:
> >> >
> >> >
> >> > All
> >> > See below - Google Summer of code 2017 isn't far away.
> >> > Previously, we've had a number of project committers who have come to
> us
> >> through a GSOC project
> >> >
> >>
> >> Do we have small sized projects / ideas ready to be submitted for GSOC?
> >>
> >> > Become a mentor isn't something to be taken lightly but I would
> >> encourage as many of our community as possible to consider it - it will
> >> hopefully help wth the next generation of people excited to work on
> >> cloudstack
> >>
> >> Did this for the Ceph project. It is a lot of work.
> >>
> >> Wido
> >>
> >> >
> >> >
> >> >
> >> >
> >> > Kind Regards
> >> > Giles
> >> >
> >> >
> >> > giles.sir...@shapeblue.com
> >> > www.shapeblue.com
> >> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> >> > @shapeblue
> >> >
> >> >
> >> >
> >> >
> >> > -Original Message-
> >> > From: Ulrich Stärk [mailto:u...@apache.org ]
> >> > Sent: 03 February 2017 19:51
> >> > To: ment...@community.apache.org
> >> > Subject: Google Summer of Code 2017 is coming
> >> >
> >> > Hello PMCs (incubator Mentors, please forward this email to your
> >> podlings),
> >> >
> >> > Google Summer of Code [1] is a program sponsored by Google allowing
> >> students to spend their summer working on open source software. Students
> >> will receive stipends for developing open source software full-time for
> >> three months. Projects will provide mentoring and project ideas, and in
> >> return have the chance to get new code developed and - most importantly
> -
> >> to identify and bring in new committers.
> >> >
> >> > The ASF will apply as a participating organization meaning individual
> >> projects don't have to apply separately.
> >> >
> >> > If you want to participate with your project we ask you to do the
> >> following things as soon as possible but by no later than 2017-02-09:
> >> >
> >> > 1. understand what it means to be a mentor [2].
> >> >
> >> > 2. record your project ideas.
> >> >
> >> > Just create issues in JIRA, label them with gsoc2017, and they will
> show
> >> up at [3]. Please be as specific as possible when describing your idea.
> >> Include the programming language, the tools and skills required, but 

Re: FW: Google Summer of Code 2017 is coming

[sachin patil]

Hello Daan,

 I had two particular projects in mind and there are pleny
others as well.

-- One is the ceph project @wido had posted here.

-- The other is Ability to move VM to other project CLOUDSTACK-9737
 ,this issue it
still open ,Wei Zhou did some work on this I guess. I would like to know
its status and if possible work for it.

If you have any other ideas Daan, I would like to discuss them as well.

On Tue, Feb 7, 2017 at 2:46 PM, Daan Hoogland 
wrote:

> Great Sachin,
>
> Do you have a subject in mind? I want to mentor but we may just find
> you an even better mentor based on your preferred subject ;)
>
> On Mon, Feb 6, 2017 at 3:00 PM, Ian Duffy  wrote:
> > I believe Sachin (CCed) was showed interest in becoming a student a
> couple
> > of months back. Might be good to get him and a potential mentor talking.
> >
> > On 6 February 2017 at 10:19, Daan Hoogland 
> > wrote:
> >
> >> I think we should be able to muster some quickly:
> >>
> >> project = CLOUDSTACK AND issuetype in (Improvement, "New Feature", Wish)
> >> AND status = Open AND assignee in (EMPTY)
> >>
> >> leads me to 321 open, unassigned, wishes, improvements and new features
> [image:
> >> ]
> >>
> >>
> >> I'll do some filtering and maybe we can group ideas in this thread
> quickly
> >>
> >> daan.hoogl...@shapeblue.com
> >> www.shapeblue.com
> >> @shapeblue
> >>
> >>
> >>
> >> --
> >> *From:* Daan Hoogland
> >> *Sent:* 06 February 2017 11:02:29
> >> *To:* Giles Sirett; dev@cloudstack.apache.org
> >> *Subject:* Re: FW: Google Summer of Code 2017 is coming
> >>
> >>
> >> I'll do some jira grooming the next couple of days, maybe we find some.
> >> --
> >> *From:* Wido den Hollander 
> >> *Sent:* 06 February 2017 10:59:07
> >> *To:* Giles Sirett; dev@cloudstack.apache.org
> >> *Subject:* Re: FW: Google Summer of Code 2017 is coming
> >>
> >>
> >> > Op 6 februari 2017 om 9:51 schreef Giles Sirett <
> >> giles.sir...@shapeblue.com>:
> >> >
> >> >
> >> > All
> >> > See below - Google Summer of code 2017 isn't far away.
> >> > Previously, we've had a number of project committers who have come to
> us
> >> through a GSOC project
> >> >
> >>
> >> Do we have small sized projects / ideas ready to be submitted for GSOC?
> >>
> >> > Become a mentor isn't something to be taken lightly but I would
> >> encourage as many of our community as possible to consider it - it will
> >> hopefully help wth the next generation of people excited to work on
> >> cloudstack
> >>
> >> Did this for the Ceph project. It is a lot of work.
> >>
> >> Wido
> >>
> >> >
> >> >
> >> >
> >> >
> >> > Kind Regards
> >> > Giles
> >> >
> >> >
> >> > giles.sir...@shapeblue.com
> >> > www.shapeblue.com
> >> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> >> > @shapeblue
> >> >
> >> >
> >> >
> >> >
> >> > -Original Message-
> >> > From: Ulrich Stärk [mailto:u...@apache.org ]
> >> > Sent: 03 February 2017 19:51
> >> > To: ment...@community.apache.org
> >> > Subject: Google Summer of Code 2017 is coming
> >> >
> >> > Hello PMCs (incubator Mentors, please forward this email to your
> >> podlings),
> >> >
> >> > Google Summer of Code [1] is a program sponsored by Google allowing
> >> students to spend their summer working on open source software. Students
> >> will receive stipends for developing open source software full-time for
> >> three months. Projects will provide mentoring and project ideas, and in
> >> return have the chance to get new code developed and - most importantly
> -
> >> to identify and bring in new committers.
> >> >
> >> > The ASF will apply as a participating organization meaning individual
> >> projects don't have to apply separately.
> >> >
> >> > If you want to participate with your project we ask you to do the
> >> following things as soon as possible but by no later than 2017-02-09:
> >> >
> >> > 1. understand what it means to be a mentor [2].
> >> >
> >> > 2. record your project ideas.
> >> >
> >> > Just create issues in JIRA, label them with gsoc2017, and they will
> show
> >> up at [3]. Please be as specific as possible when describing your idea.
> >> Include the programming language, the tools and skills required, but try
> >> not to scare potential students away. They are supposed to learn what's
> >> required before the program starts.
> >> >
> >> > Use labels, e.g. for the programming language (java, c, c++, erlang,
> >> python, brainfuck, ...) or technology area (cloud, xml, web, foo, bar,
> ...)
> >> and record them at [5].
> >> >
> >> > Please use the COMDEV JIRA project for recording your ideas if your
> >> project doesn't use JIRA (e.g.
> >> > httpd, ooo). Contact d...@community.apache.org if you need assistance.
> >> >
> >> > [4] contains some additional information (will be updated for 2017
> >> 

Re: FW: Google Summer of Code 2017 is coming

[Daan Hoogland]

Great Sachin,

Do you have a subject in mind? I want to mentor but we may just find
you an even better mentor based on your preferred subject ;)

On Mon, Feb 6, 2017 at 3:00 PM, Ian Duffy  wrote:
> I believe Sachin (CCed) was showed interest in becoming a student a couple
> of months back. Might be good to get him and a potential mentor talking.
>
> On 6 February 2017 at 10:19, Daan Hoogland 
> wrote:
>
>> I think we should be able to muster some quickly:
>>
>> project = CLOUDSTACK AND issuetype in (Improvement, "New Feature", Wish)
>> AND status = Open AND assignee in (EMPTY)
>>
>> leads me to 321 open, unassigned, wishes, improvements and new features 
>> [image:
>> ]
>>
>>
>> I'll do some filtering and maybe we can group ideas in this thread quickly
>>
>> daan.hoogl...@shapeblue.com
>> www.shapeblue.com
>> @shapeblue
>>
>>
>>
>> --
>> *From:* Daan Hoogland
>> *Sent:* 06 February 2017 11:02:29
>> *To:* Giles Sirett; dev@cloudstack.apache.org
>> *Subject:* Re: FW: Google Summer of Code 2017 is coming
>>
>>
>> I'll do some jira grooming the next couple of days, maybe we find some.
>> --
>> *From:* Wido den Hollander 
>> *Sent:* 06 February 2017 10:59:07
>> *To:* Giles Sirett; dev@cloudstack.apache.org
>> *Subject:* Re: FW: Google Summer of Code 2017 is coming
>>
>>
>> > Op 6 februari 2017 om 9:51 schreef Giles Sirett <
>> giles.sir...@shapeblue.com>:
>> >
>> >
>> > All
>> > See below - Google Summer of code 2017 isn't far away.
>> > Previously, we've had a number of project committers who have come to us
>> through a GSOC project
>> >
>>
>> Do we have small sized projects / ideas ready to be submitted for GSOC?
>>
>> > Become a mentor isn't something to be taken lightly but I would
>> encourage as many of our community as possible to consider it - it will
>> hopefully help wth the next generation of people excited to work on
>> cloudstack
>>
>> Did this for the Ceph project. It is a lot of work.
>>
>> Wido
>>
>> >
>> >
>> >
>> >
>> > Kind Regards
>> > Giles
>> >
>> >
>> > giles.sir...@shapeblue.com
>> > www.shapeblue.com
>> > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
>> > @shapeblue
>> >
>> >
>> >
>> >
>> > -Original Message-
>> > From: Ulrich Stärk [mailto:u...@apache.org ]
>> > Sent: 03 February 2017 19:51
>> > To: ment...@community.apache.org
>> > Subject: Google Summer of Code 2017 is coming
>> >
>> > Hello PMCs (incubator Mentors, please forward this email to your
>> podlings),
>> >
>> > Google Summer of Code [1] is a program sponsored by Google allowing
>> students to spend their summer working on open source software. Students
>> will receive stipends for developing open source software full-time for
>> three months. Projects will provide mentoring and project ideas, and in
>> return have the chance to get new code developed and - most importantly -
>> to identify and bring in new committers.
>> >
>> > The ASF will apply as a participating organization meaning individual
>> projects don't have to apply separately.
>> >
>> > If you want to participate with your project we ask you to do the
>> following things as soon as possible but by no later than 2017-02-09:
>> >
>> > 1. understand what it means to be a mentor [2].
>> >
>> > 2. record your project ideas.
>> >
>> > Just create issues in JIRA, label them with gsoc2017, and they will show
>> up at [3]. Please be as specific as possible when describing your idea.
>> Include the programming language, the tools and skills required, but try
>> not to scare potential students away. They are supposed to learn what's
>> required before the program starts.
>> >
>> > Use labels, e.g. for the programming language (java, c, c++, erlang,
>> python, brainfuck, ...) or technology area (cloud, xml, web, foo, bar, ...)
>> and record them at [5].
>> >
>> > Please use the COMDEV JIRA project for recording your ideas if your
>> project doesn't use JIRA (e.g.
>> > httpd, ooo). Contact d...@community.apache.org if you need assistance.
>> >
>> > [4] contains some additional information (will be updated for 2017
>> shortly).
>> >
>> > 3. subscribe to ment...@community.apache.org; restricted to potential
>> mentors, meant to be used as a private list - general discussions on the
>> public d...@community.apache.org list as much as possible please). Use a
>> recognized address when subscribing (@apache.org or one of your alias
>> addresses on record).
>> >
>> > Note that the ASF isn't accepted as a participating organization yet,
>> nevertheless you *have to* start recording your ideas now or we will not
>> get accepted.
>> >
>> > Over the years we were able to complete hundreds of projects
>> successfully. Some of our prior students are active contributors now! Let's
>> make this year a success again!
>> >
>> > Cheers,
>> >
>> > Uli
>> >
>> > P.S.: Except for the private parts (label spreadsheet mostly), this
>> email is 

[GitHub] cloudstack issue #1888: CLOUDSTACK-9710: Switch to JRE1.8

[wido]

Github user wido commented on the issue:

https://github.com/apache/cloudstack/pull/1888
  
@swill: Yes we should! I think that was an oversight. Can you send a PR for 
this against master?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---