Hi Swen, We generally apply a more relaxed version of our commit into apache/cloudstack procedure for both docs and www. AFAIR the same commit rights apply to cloudstack-www as cloudstack. You should create a PR which at least one other person should review, which can then be merged. Changing anything substantial about the website's look/feel is always going to escalate into a bit of a bike shedding exercise.
If you are planning on making substantial changes, advice would be to create a PR which can be reviewed and let everyone know, anyone interested will go and look. On a linked note, I found this week that middleman v4 isn't compatible with how we have set up our source. Some file extensions need changing, until that's done we wont be able to see what else (if anything) is broken. I haven't gotten round to creating a PR to fix it, but it would be a bit redundant if things are potentially getting changed anyway. Paul. paul.an...@shapeblue.com www.shapeblue.com Amadeus House, Floral Street, London WC2E 9DPUK @shapeblue -----Original Message----- From: Swen - swen.io <m...@swen.io> Sent: 10 April 2019 14:22 To: us...@cloudstack.apache.org Subject: committer with merge rights on cloudstack-www Dear community, I want to get more involved in the great CloudStack community than only by this list. What I am looking for is to get our public page more informative and up-to-date from a content point of view. If you are want to get involved in CloudStack and are hitting the official page it looks kind of outdated and/or not maintained. I want to take care of this. Therefore I need merge privileges on the page repo on github and I ask kindly if this is ok for the community. cu Swen
