I should have included a link:
https://gitbox.apache.org/setup/


paul.an...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 


-----Original Message-----
From: Paul Angus <paul.an...@shapeblue.com> 
Sent: 10 April 2019 16:57
To: users@cloudstack.apache.org
Subject: RE: committer with merge rights on cloudstack-www

Have you gone through the Apache GitBox account linking + 2FA malarkey?


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 16:45
To: users@cloudstack.apache.org
Subject: AW: committer with merge rights on cloudstack-www

Hi Paul,

as far as I understand I am unable to provide the whole workflow after creating 
a PR. After opening a PR which then get approved I cannot do the merge, the 
build and the upload to the asf-site branch (as mentioned in the README) 
because of missing privileges. To do that I need someone else's help with the 
right ones. So this ends up in a situation that a PR (#56) that I opened 5 days 
ago for updating only events on the main site has been approved, closed and 
merged, but not build and uploaded to the live page. Please tell me if there is 
something wrong in my workflow and how I get the new events on the live page.

cu Swen

-----Ursprüngliche Nachricht-----
Von: Paul Angus <paul.an...@shapeblue.com>
Gesendet: Mittwoch, 10. April 2019 16:13
An: users@cloudstack.apache.org; d...@cloudstack.apache.org
Betreff: RE: committer with merge rights on cloudstack-www

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: users@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




Reply via email to