On 2017-03-17 12:33 (-0700), Stefan Podkowinski <s...@apache.org> wrote:
> As you can see there's a large part about using GitHub for editing on > the page. I'd like to know what you think about that and if you'd agree > to accept PRs for such purposes. > The challenge of github PRs isn't that we don't want them, it's that we can't merge them - the apache github repo is a read only mirror (the master is on ASF infrastructure). Personally, I'd rather have a Github PR than no patch, but I'd much rather have a JIRA patch than a Github PR, because ultimately the committer is going to have to manually transform the Github PR into a .patch file and commit it with a special commit message to close the Github PR (or hope that the contributor closes it for us, because committers can't even close PRs at this point). > I'd also like to add another section for committers that describes the > required steps to actually publish the latest trunk to our website. I > know that svn has been mentioned somewhere, but I would appreciate if > someone either adds that section or just shares some details in this thread. The repo is at https://svn.apache.org/repos/asf/cassandra/ - there's a doc at https://svn.apache.org/repos/asf/cassandra/site/src/README that describes it.
