Github user swill commented on the issue:
https://github.com/apache/cloudstack-www/pull/34
So the flow would be:
- pull from github/asf
- make changes
- build locally to verify the changes, but the resulting markup is not
tracked (removed + ignored)
- push changes to asf (must be an ICLA committer)
- changes get sent to github
- jenkins builds the static site and pushes it to the asf `asf-site` branch
(must be an ICLA committer)
Since we have not removed the ICLA committer from the flow, we are fine.
That is still a manual step. But right now the static site is hosted from the
ASF infra (my understanding), so the content has to be tracked in the ASF repo
for the static site to be served. So that means that even if we don't track
the content in the master branch, we have to in the `asf-site` branch. Jenkins
has to push to that ASF repo to publish the site, so that has to be *someones*
ICLA associated with that commit.
If the site was not hosted on ASF infra, I don't think we would have the
problem because we would still be building and deploying from an ICLA approved
version of the content.
Maybe I am reading too far into this, but I feel like we should understand
the change before we do it.
I think we should go ahead with this commit since this is the flow we have
been using, and take the jenkins discussion (which I think is awesome) to a
different 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.
---
