Auto-publish events page (was: Apache MXNet (incubating) meetup in Seattle on 4/24)

[sebb <se...@gmail.com>]

On 12 April 2018 at 10:27, Daniel Gruno <hu...@apache.org> wrote:
> On 04/12/2018 11:17 AM, sebb wrote:
>>
>> On 12 April 2018 at 08:04, Isabel Drost-Fromm <is...@apache.org> wrote:
>>>
>>> On 10/04/18 18:21, sebb wrote:
>>>>
>>>>
>>>> It won't automatically show up until someone publishes the main ASF
>>>> site.
>>>>
>>>> AFAICT there is a cron job that publishes part of the site, but it
>>>> does not include the events page.
>>>
>>>
>>>
>>> What needs to be done to make that happen?
>>
>>
>> Either:
>> Move script to a Comdev host (and redirect the ASF page)
>> Fix it so the page is published directly, rather than via pubsub
>> (which involves updating SVN/Git first).
>
>
> I would be in favor of a json object somewhere with the dates/events in it,
> that gets grabbed by the site. This object could just be in a git repo
> somewhere and be pushed directly on change.

AFAICT that would still require credentials to be stored somewhere to
update the repo.

The data changes regularly, and does not need to be kept in a repo.

>
>>
>> Or:
>> Ask Infra to add it to a cron job.
>> The initial SVN commit has to be done by someone/thing with ASF-site
>> karma (currently Rich).
>>
>>>
>>> Isabel
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>> For additional commands, e-mail: dev-help@community.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org

Re: Auto-publish events page (was: Apache MXNet (incubating) meetup in Seattle on 4/24)

[sebb <se...@gmail.com>]

On 12 April 2018 at 11:33, Daniel Gruno <hu...@apache.org> wrote:
> On 04/12/2018 12:23 PM, sebb wrote:
>>
>> On 12 April 2018 at 10:27, Daniel Gruno <hu...@apache.org> wrote:
>>>
>>> On 04/12/2018 11:17 AM, sebb wrote:
>>>>
>>>>
>>>> On 12 April 2018 at 08:04, Isabel Drost-Fromm <is...@apache.org> wrote:
>>>>>
>>>>>
>>>>> On 10/04/18 18:21, sebb wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>> It won't automatically show up until someone publishes the main ASF
>>>>>> site.
>>>>>>
>>>>>> AFAICT there is a cron job that publishes part of the site, but it
>>>>>> does not include the events page.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> What needs to be done to make that happen?
>>>>
>>>>
>>>>
>>>> Either:
>>>> Move script to a Comdev host (and redirect the ASF page)
>>>> Fix it so the page is published directly, rather than via pubsub
>>>> (which involves updating SVN/Git first).
>>>
>>>
>>>
>>> I would be in favor of a json object somewhere with the dates/events in
>>> it,
>>> that gets grabbed by the site. This object could just be in a git repo
>>> somewhere and be pushed directly on change.
>>
>>
>> AFAICT that would still require credentials to be stored somewhere to
>> update the repo.
>
>
> buildbot/jenkins has that.
>
>>
>> The data changes regularly, and does not need to be kept in a repo.
>
>
> Where would you suggest it be kept? a database of sorts?

The data does not need to be kept for any length of time, so it can
just be in a file.

EIther an HTML file that is directly published, or in a data source
(e.g. JSON) that is used to generate the HTML.

C.f. the projects.a.o, reporter.a.o and mod_mbox hosts which all
create site content without needing to use repos/databases.

Note that the data extraction phase needs additional credentials to
access the event listing.

>
>>
>>>
>>>>
>>>> Or:
>>>> Ask Infra to add it to a cron job.
>>>> The initial SVN commit has to be done by someone/thing with ASF-site
>>>> karma (currently Rich).
>>>>
>>>>>
>>>>> Isabel
>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>> For additional commands, e-mail: dev-help@community.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org

Re: Auto-publish events page (was: Apache MXNet (incubating) meetup in Seattle on 4/24)

[Daniel Gruno <hu...@apache.org>]

On 04/12/2018 12:23 PM, sebb wrote:
> On 12 April 2018 at 10:27, Daniel Gruno <hu...@apache.org> wrote:
>> On 04/12/2018 11:17 AM, sebb wrote:
>>>
>>> On 12 April 2018 at 08:04, Isabel Drost-Fromm <is...@apache.org> wrote:
>>>>
>>>> On 10/04/18 18:21, sebb wrote:
>>>>>
>>>>>
>>>>> It won't automatically show up until someone publishes the main ASF
>>>>> site.
>>>>>
>>>>> AFAICT there is a cron job that publishes part of the site, but it
>>>>> does not include the events page.
>>>>
>>>>
>>>>
>>>> What needs to be done to make that happen?
>>>
>>>
>>> Either:
>>> Move script to a Comdev host (and redirect the ASF page)
>>> Fix it so the page is published directly, rather than via pubsub
>>> (which involves updating SVN/Git first).
>>
>>
>> I would be in favor of a json object somewhere with the dates/events in it,
>> that gets grabbed by the site. This object could just be in a git repo
>> somewhere and be pushed directly on change.
> 
> AFAICT that would still require credentials to be stored somewhere to
> update the repo.

buildbot/jenkins has that.

> 
> The data changes regularly, and does not need to be kept in a repo.

Where would you suggest it be kept? a database of sorts?

> 
>>
>>>
>>> Or:
>>> Ask Infra to add it to a cron job.
>>> The initial SVN commit has to be done by someone/thing with ASF-site
>>> karma (currently Rich).
>>>
>>>>
>>>> Isabel
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>>> For additional commands, e-mail: dev-help@community.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>>> For additional commands, e-mail: dev-help@community.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
>> For additional commands, e-mail: dev-help@community.apache.org
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
> For additional commands, e-mail: dev-help@community.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org