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

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/cloudstack-www/pull/34


---
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 ...

[rafaelweingartner]

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

https://github.com/apache/cloudstack-www/pull/34#discussion_r100827279
  
--- Diff: content/about.html ---
@@ -79,7 +78,7 @@
 Get 
Involved
 Developers
 Mailing 
Lists
-http://lanyrd.com/topics/apache-cloudstack/; target="_blank">Events  
Meetups 
--- End diff --

I was going to say exactly that. At least for me, it feels something that 
we stopped using and maintaining a long time ago. Could not we use the 
system/website of CCC for spread the word about user group meeting too? Then, 
we centralize information.


---
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_r100826211
  
--- Diff: content/about.html ---
@@ -79,7 +78,7 @@
 Get 
Involved
 Developers
 Mailing 
Lists
-http://lanyrd.com/topics/apache-cloudstack/; target="_blank">Events  
Meetups 
--- End diff --

No one uses it though. It is just empty. Do we even have credentials 
somewhere to add to that? 


---
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 ...

[pdion891]

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

https://github.com/apache/cloudstack-www/pull/34#discussion_r100800298
  
--- Diff: content/about.html ---
@@ -79,7 +78,7 @@
 Get 
Involved
 Developers
 Mailing 
Lists
-http://lanyrd.com/topics/apache-cloudstack/; target="_blank">Events  
Meetups 
--- End diff --

I'm not sure we want to ditch lanyrd link, it's usefull to publish other 
event that collabs, like meetups.


---
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 pull request #34: Remove link to “planet.apache.org” and ...

[rafaelweingartner]

GitHub user rafaelweingartner opened a pull request:

https://github.com/apache/cloudstack-www/pull/34

Remove link to “planet.apache.org” and update conference links.

Remove link to “planet.apache.org” and update conference links and 
update the link for the CCCs hot site

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

$ git pull https://github.com/rafaelweingartner/cloudstack-www 
fixConferenceLinks

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

https://github.com/apache/cloudstack-www/pull/34.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 #34


commit 1f03555d21a289f3d8a266c17ff53555cb94b6d2
Author: Rafael Weingartner 
Date:   2017-02-01T15:23:29Z

Remove link to “planet.apache.org” and update conference links.




---
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.
---