Re: Please describe website update procedure for updating Phoenix and Omid

[Istvan Toth <st...@cloudera.com.INVALID>]

I did some digging around in the meantime.

Omid seems to use the mechanism where the site is simply pulled from the
git repo.
We should be able to have it automagically deploy it into a phoenix.a.o
subdirectory by adding an .asf.yaml file in the phoenix-omid-site repo.

The Tephra website also looks like something built by the maven site
plugin, and we seem to have a copy of the built website in the phoenix
website repo, but
I could not find the sources for it anywhere.

Action items:

   - Find the Lost Tephra Website Sources
   - Decide if we are OK with Omid and Tephra living under phoenix.a.o. If
   we are
   - Find out if INFRA can redirect the incubating websites to phoenix.a.o
   URLs
   - Do the transition


On Mon, Nov 30, 2020 at 9:52 PM Josh Elser <el...@apache.org> wrote:

> Should we just incorporate the omid and tephra websites into phoenix.a.o
> going forward?
>
> I'm surprised infra didn't kill the old websites when the IPMC
> "graduated" them.
>
> ASF websites are either updated via svn pub-sub, git pub-sub, or via ASF
> CMS (which might be EOL, I forget).
>
> svn/git pub-sub essentially work the same way: when you commit to a
> certain branch in a repository, magic happens on the infra side to
> update the corresponding website. For SVN pubsub, this is just some
> repo. For Git pubsub, the website branch defaults to "asf-site".
>
> ASF CMS was a home-grown content management system in which you would go
> into your website, click a special bookmark, use a WYSIWYG editor,
> stage, and publish changes.
>
> If we don't know what Omid (and Tephra) are using, we can ask infra.
>
> On 11/25/20 2:35 AM, Istvan Toth wrote:
> > I have documented my unsuccessful attempt to update the Omid website in
> > https://issues.apache.org/jira/browse/OMID-190
> >
> > Still looking for any information on update procedure for both websites.
> >
> > regards
> > Istvan
> >
> > On Mon, Nov 9, 2020 at 1:30 PM Istvan Toth <st...@apache.org> wrote:
> >
> >> Hi!
> >>
> >> We have documented how to update the Phoenix website on the website
> itself.
> >> However, I could not find similar documentation for Omid and Tephra.
> >>
> >> If you have updated either website in the past, or know the procedure to
> >> update either, please describe the procedure, or link the relevant
> >> documentation.
> >>
> >> thanks in advance
> >> Istvan
> >>
> >
>


-- 
*István Tóth* | Staff Software Engineer
stoty@cloudera.com <https://www.cloudera.com>
[image: Cloudera] <https://www.cloudera.com/>
[image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
on LinkedIn] <https://www.linkedin.com/company/cloudera>
<https://www.cloudera.com/>
------------------------------

Re: Please describe website update procedure for updating Phoenix and Omid

[Istvan Toth <st...@apache.org>]

Found the Tephra website sources, and the old instructions to update it.
It's in the site branch of the source repo.

https://tephra.incubator.apache.org/ReleaseGuide.html

On Tue, Dec 1, 2020 at 8:06 AM Istvan Toth <st...@cloudera.com> wrote:

> I did some digging around in the meantime.
>
> Omid seems to use the mechanism where the site is simply pulled from the
> git repo.
> We should be able to have it automagically deploy it into a phoenix.a.o
> subdirectory by adding an .asf.yaml file in the phoenix-omid-site repo.
>
> The Tephra website also looks like something built by the maven site
> plugin, and we seem to have a copy of the built website in the phoenix
> website repo, but
> I could not find the sources for it anywhere.
>
> Action items:
>
>    - Find the Lost Tephra Website Sources
>    - Decide if we are OK with Omid and Tephra living under phoenix.a.o.
>    If we are
>    - Find out if INFRA can redirect the incubating websites to
>    phoenix.a.o URLs
>    - Do the transition
>
>
> On Mon, Nov 30, 2020 at 9:52 PM Josh Elser <el...@apache.org> wrote:
>
>> Should we just incorporate the omid and tephra websites into phoenix.a.o
>> going forward?
>>
>> I'm surprised infra didn't kill the old websites when the IPMC
>> "graduated" them.
>>
>> ASF websites are either updated via svn pub-sub, git pub-sub, or via ASF
>> CMS (which might be EOL, I forget).
>>
>> svn/git pub-sub essentially work the same way: when you commit to a
>> certain branch in a repository, magic happens on the infra side to
>> update the corresponding website. For SVN pubsub, this is just some
>> repo. For Git pubsub, the website branch defaults to "asf-site".
>>
>> ASF CMS was a home-grown content management system in which you would go
>> into your website, click a special bookmark, use a WYSIWYG editor,
>> stage, and publish changes.
>>
>> If we don't know what Omid (and Tephra) are using, we can ask infra.
>>
>> On 11/25/20 2:35 AM, Istvan Toth wrote:
>> > I have documented my unsuccessful attempt to update the Omid website in
>> > https://issues.apache.org/jira/browse/OMID-190
>> >
>> > Still looking for any information on update procedure for both websites.
>> >
>> > regards
>> > Istvan
>> >
>> > On Mon, Nov 9, 2020 at 1:30 PM Istvan Toth <st...@apache.org> wrote:
>> >
>> >> Hi!
>> >>
>> >> We have documented how to update the Phoenix website on the website
>> itself.
>> >> However, I could not find similar documentation for Omid and Tephra.
>> >>
>> >> If you have updated either website in the past, or know the procedure
>> to
>> >> update either, please describe the procedure, or link the relevant
>> >> documentation.
>> >>
>> >> thanks in advance
>> >> Istvan
>> >>
>> >
>>
>
>
> --
> *István Tóth* | Staff Software Engineer
> stoty@cloudera.com <https://www.cloudera.com>
> [image: Cloudera] <https://www.cloudera.com/>
> [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
> Cloudera on Facebook] <https://www.facebook.com/cloudera> [image:
> Cloudera on LinkedIn] <https://www.linkedin.com/company/cloudera>
> <https://www.cloudera.com/>
> ------------------------------
>