You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by Stig Rohde Døssing <st...@gmail.com> on 2018/05/12 09:45:32 UTC
Updating the website
Hi,
I'd like to update the 2.0.0-SNAPSHOT documentation on the website, it's
been a while since it was last sync'ed with the docs in the main
repository. Can I just do this, or does it require a vote? I figure it
falls under non-code change in the bylaws.
Re: Updating the website
Posted by Stig Rohde Døssing <st...@gmail.com>.
It worked, the site also updated :)
2018-05-12 23:41 GMT+02:00 Stig Rohde Døssing <st...@gmail.com>:
> Thanks, I'll try that.
>
> 2018-05-12 22:52 GMT+02:00 P. Taylor Goetz <pt...@gmail.com>:
>
>> Sometimes the gitpubsub process gets stuck. Pushing an empty or white
>> space change usually helps.
>>
>> -Taylor
>>
>> > On May 12, 2018, at 2:06 PM, Stig Rohde Døssing <st...@gmail.com>
>> wrote:
>> >
>> > Isn't the site content based on the asf-site branch at
>> > https://git-wip-us.apache.org/repos/asf?p=storm-site.git;a=
>> > log;h=refs/heads/asf-site? The site doesn't seem to update after I
>> pushed
>> > changes. Maybe related(?) the latest commit I pushed seems to have made
>> it
>> > to the ASF repo, but not to the Github mirror.
>> >
>> > 2018-05-12 17:57 GMT+02:00 Stig Rohde Døssing <st...@gmail.com>:
>> >
>> >> Will do, thanks.
>> >>
>> >> 2018-05-12 16:00 GMT+02:00 P. Taylor Goetz <pt...@gmail.com>:
>> >>
>> >>> Go for it.
>> >>>
>> >>> -Taylor
>> >>>
>> >>>> On May 12, 2018, at 5:45 AM, Stig Rohde Døssing <
>> stigdoessing@gmail.com>
>> >>> wrote:
>> >>>>
>> >>>> Hi,
>> >>>>
>> >>>> I'd like to update the 2.0.0-SNAPSHOT documentation on the website,
>> it's
>> >>>> been a while since it was last sync'ed with the docs in the main
>> >>>> repository. Can I just do this, or does it require a vote? I figure
>> it
>> >>>> falls under non-code change in the bylaws.
>> >>>
>> >>
>> >>
>>
>
>
Re: Updating the website
Posted by Stig Rohde Døssing <st...@gmail.com>.
Thanks, I'll try that.
2018-05-12 22:52 GMT+02:00 P. Taylor Goetz <pt...@gmail.com>:
> Sometimes the gitpubsub process gets stuck. Pushing an empty or white
> space change usually helps.
>
> -Taylor
>
> > On May 12, 2018, at 2:06 PM, Stig Rohde Døssing <st...@gmail.com>
> wrote:
> >
> > Isn't the site content based on the asf-site branch at
> > https://git-wip-us.apache.org/repos/asf?p=storm-site.git;a=
> > log;h=refs/heads/asf-site? The site doesn't seem to update after I pushed
> > changes. Maybe related(?) the latest commit I pushed seems to have made
> it
> > to the ASF repo, but not to the Github mirror.
> >
> > 2018-05-12 17:57 GMT+02:00 Stig Rohde Døssing <st...@gmail.com>:
> >
> >> Will do, thanks.
> >>
> >> 2018-05-12 16:00 GMT+02:00 P. Taylor Goetz <pt...@gmail.com>:
> >>
> >>> Go for it.
> >>>
> >>> -Taylor
> >>>
> >>>> On May 12, 2018, at 5:45 AM, Stig Rohde Døssing <
> stigdoessing@gmail.com>
> >>> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> I'd like to update the 2.0.0-SNAPSHOT documentation on the website,
> it's
> >>>> been a while since it was last sync'ed with the docs in the main
> >>>> repository. Can I just do this, or does it require a vote? I figure it
> >>>> falls under non-code change in the bylaws.
> >>>
> >>
> >>
>
Re: Updating the website
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
Sometimes the gitpubsub process gets stuck. Pushing an empty or white space change usually helps.
-Taylor
> On May 12, 2018, at 2:06 PM, Stig Rohde Døssing <st...@gmail.com> wrote:
>
> Isn't the site content based on the asf-site branch at
> https://git-wip-us.apache.org/repos/asf?p=storm-site.git;a=
> log;h=refs/heads/asf-site? The site doesn't seem to update after I pushed
> changes. Maybe related(?) the latest commit I pushed seems to have made it
> to the ASF repo, but not to the Github mirror.
>
> 2018-05-12 17:57 GMT+02:00 Stig Rohde Døssing <st...@gmail.com>:
>
>> Will do, thanks.
>>
>> 2018-05-12 16:00 GMT+02:00 P. Taylor Goetz <pt...@gmail.com>:
>>
>>> Go for it.
>>>
>>> -Taylor
>>>
>>>> On May 12, 2018, at 5:45 AM, Stig Rohde Døssing <st...@gmail.com>
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I'd like to update the 2.0.0-SNAPSHOT documentation on the website, it's
>>>> been a while since it was last sync'ed with the docs in the main
>>>> repository. Can I just do this, or does it require a vote? I figure it
>>>> falls under non-code change in the bylaws.
>>>
>>
>>
Re: Updating the website
Posted by Stig Rohde Døssing <st...@gmail.com>.
Isn't the site content based on the asf-site branch at
https://git-wip-us.apache.org/repos/asf?p=storm-site.git;a=
log;h=refs/heads/asf-site? The site doesn't seem to update after I pushed
changes. Maybe related(?) the latest commit I pushed seems to have made it
to the ASF repo, but not to the Github mirror.
2018-05-12 17:57 GMT+02:00 Stig Rohde Døssing <st...@gmail.com>:
> Will do, thanks.
>
> 2018-05-12 16:00 GMT+02:00 P. Taylor Goetz <pt...@gmail.com>:
>
>> Go for it.
>>
>> -Taylor
>>
>> > On May 12, 2018, at 5:45 AM, Stig Rohde Døssing <st...@gmail.com>
>> wrote:
>> >
>> > Hi,
>> >
>> > I'd like to update the 2.0.0-SNAPSHOT documentation on the website, it's
>> > been a while since it was last sync'ed with the docs in the main
>> > repository. Can I just do this, or does it require a vote? I figure it
>> > falls under non-code change in the bylaws.
>>
>
>
Re: Updating the website
Posted by Stig Rohde Døssing <st...@gmail.com>.
Will do, thanks.
2018-05-12 16:00 GMT+02:00 P. Taylor Goetz <pt...@gmail.com>:
> Go for it.
>
> -Taylor
>
> > On May 12, 2018, at 5:45 AM, Stig Rohde Døssing <st...@gmail.com>
> wrote:
> >
> > Hi,
> >
> > I'd like to update the 2.0.0-SNAPSHOT documentation on the website, it's
> > been a while since it was last sync'ed with the docs in the main
> > repository. Can I just do this, or does it require a vote? I figure it
> > falls under non-code change in the bylaws.
>
Re: Updating the website
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
Go for it.
-Taylor
> On May 12, 2018, at 5:45 AM, Stig Rohde Døssing <st...@gmail.com> wrote:
>
> Hi,
>
> I'd like to update the 2.0.0-SNAPSHOT documentation on the website, it's
> been a while since it was last sync'ed with the docs in the main
> repository. Can I just do this, or does it require a vote? I figure it
> falls under non-code change in the bylaws.