Re: Process for site updates

[Jungtaek Lim <ka...@gmail.com>]

Sorry I should have updated the doc for website update instruction, but
missed to update. Repository for website is moved to git.

https://github.com/apache/storm-site (mirror)
https://git-wip-us.apache.org/repos/asf/storm-site.git (origin)

So you can create a pull request for updating website, or even just commit
and push if you think it's minor.

Please note that 'asf-site' should be used (there's no master branch), and
'content' directory will be used for serving website.

- Jungtaek Lim (HeartSaVioR)

2017년 9월 1일 (금) 오전 5:08, P. Taylor Goetz <pt...@gmail.com>님이 작성:

> I would say for minor changes (like this) it’s okay to go ahead and commit
> them. In the future just send out a quick “I intend to make this change” to
> the def@ list so others have a heads up.
>
> -Taylor
>
> > On Aug 31, 2017, at 1:41 PM, Stig Rohde Døssing <st...@gmail.com>
> wrote:
> >
> > Hi,
> >
> > There are a few minor things I'd like to propose changing in the
> storm-site
> > svn repo (https://issues.apache.org/jira/browse/STORM-2628,
> > https://issues.apache.org/jira/browse/STORM-2629). Posting patches to
> JIRA
> > seems easy to miss. Also do site changes like this require review?
>
>