Re: Proposal: Revamp Apache Hive website.

[Simhadri G]

Thanks everyone,

 I will begin with creating the PR and share the link in this thread soon.

Thanks
Simhadri G

On Sat, 24 Sep 2022, 04:52 Ayush Saxena,  wrote:

> Thanx Everyone,
> Almost a week and we don’t seems to have any objections to start with up
> revamp task with hive-site repo for now.
>
> Other things as mentioned can be followed up and we can try to ask folks
> to establish a PMC consensus if the need be for the futher migration tasks.
>
> Simhadri, would be good to create a Jira and link the PR and drop the link
> here in the thread as well, so as people interested can drop suggestions
> regarding the design and content of the website over there, for anything
> else we can always come back here if we are blocked on something, or if
> something more needs to be done in this context.
>
> -Ayush
>
> On 21-Sep-2022, at 6:35 PM, Stamatis Zampetakis  wrote:
>
>
> 
> The javadocs are currently in svn and they can remain there for the
> moment. Eventually, they could be moved to a hive-site repository and for
> sure we don't want them in the main hive repo. I don't see an immediate
> need to change the place where javadocs are stored but if needed we can
> raise a JIRA ticket and continue the discussion there. It's not a good idea
> to discuss under a closed issue/PR.
>
> The hive-site repo is always gonna be the place for storing the generated
> website (html files etc). When you talk about moving back to the hive repo
> I guess you refer to the source/markdown files. The decision to change the
> process of publishing the website will probably require a PMC vote with
> lazy consensus.
>
> I agree that we can start by updating the current setup. Then we can kick
> off the discussion about moving the website sources to hive repo and start
> publishing from there. I don't know if we need to move the javadocs, so we
> can postpone this discussion till we hit an obstacle.
>
> Best,
> Stamatis
>
> On Mon, Sep 19, 2022 at 12:01 PM Simhadri G  wrote:
>
>> Thanks Owen, Stamatis, Ayush and Alessandro for the feedback.
>>
>>- Regarding the javadocs and the automatically build and to deploy
>>github-pages discussion in the previous PR thread [1]
>>,
>>
>>
>>- Apache Iceberg-docs ([2]
>>   ) has recently set up
>>   a github workflow ([3])
>>   
>> 
>>   to publish the javadocs from a given javadocs dir [4]
>>    , I
>>   think we can setup the same workflow for Hive javadocs.
>>   - As Ayush and Stamatis have mentioned, I think over the past 2
>>   years, apache infra has added support for github actions and we can 
>> confirm
>>   that from Apache Iceberg/calcite docs that are currently using it.
>>   - But I am not sure regarding which branch or directory we will
>>   need to put the hive javadoc files . This needs more discussion and we 
>> can
>>   follow up on this([5]
>>   )
>>   .
>>
>>
>>-  I am not aware about the procedure or the approvals we need to
>>move from hive-site repo back to the main repository. We will need help
>>with this.
>>
>>- I was able to setup the github action on the POC repo:
>>https://github.com/simhadri-g/hive-site/tree/new-site  .
>>- Any changes to this repo/new-site will automatically reflect here
>>   once the github workflow completes:
>>   https://simhadri-g.github.io/hive-site/  .
>>
>>   - Considering the feedback, I think we can plan to do in 3 phases,
>>for the first cut I would like to update the website in the present setup,
>>followed by moving the javadocs to the hive-site repo  and as for the 
>> third
>>phase , we can work on migrating from hive-site to hive repo.
>>
>>- If everyone agrees, can we please go ahead with the first phase?
>>
>>
>> [1]https://github.com/apache/hive/pull/1410,
>> [2]https://iceberg.apache.org/javadoc/latest/
>> [3]
>> https://github.com/apache/iceberg-docs/actions/runs/3062679467/jobs/4943928455
>> [4]https://github.com/apache/iceberg-docs/tree/main/javadoc
>> [5]https://github.com/apache/hive/pull/1410#issuecomment-680111530
>> [6] https://github.com/apache/hive/pull/1410#issuecomment-680102815
>>
>>
>> Thanks!
>> Simhadri G
>>
>> On Mon, Sep 19, 2022 at 1:50 PM Alessandro Solimando <
>> alessandro.solima...@gmail.com> wrote:
>>
>>> Hi everyone,
>>> thanks Simhadri for pushing this forward.
>>>
>>> I like the look and feel of the new website, and I agree with Stamatis
>>> that having the website sources in the Hive repo, and automatically
>>> publishing the site upon commits would be very beneficial.
>>>
>>> Best regards,
>>> Alessandro
>>>
>>> On Thu, 15 Sept 2022 at 23:11, Stamatis Zampetakis 
>>> wrote:
>>>
 Hi all,

Re: Proposal: Revamp Apache Hive website.

[Ayush Saxena]

Thanx Everyone,
Almost a week and we don’t seems to have any objections to start with up revamp 
task with hive-site repo for now.

Other things as mentioned can be followed up and we can try to ask folks to 
establish a PMC consensus if the need be for the futher migration tasks.

Simhadri, would be good to create a Jira and link the PR and drop the link here 
in the thread as well, so as people interested can drop suggestions regarding 
the design and content of the website over there, for anything else we can 
always come back here if we are blocked on something, or if something more 
needs to be done in this context.

-Ayush

On 21-Sep-2022, at 6:35 PM, Stamatis Zampetakis  wrote:
> 
> 
> The javadocs are currently in svn and they can remain there for the moment. 
> Eventually, they could be moved to a hive-site repository and for sure we 
> don't want them in the main hive repo. I don't see an immediate need to 
> change the place where javadocs are stored but if needed we can raise a JIRA 
> ticket and continue the discussion there. It's not a good idea to discuss 
> under a closed issue/PR.
> 
> The hive-site repo is always gonna be the place for storing the generated 
> website (html files etc). When you talk about moving back to the hive repo I 
> guess you refer to the source/markdown files. The decision to change the 
> process of publishing the website will probably require a PMC vote with lazy 
> consensus.
> 
> I agree that we can start by updating the current setup. Then we can kick off 
> the discussion about moving the website sources to hive repo and start 
> publishing from there. I don't know if we need to move the javadocs, so we 
> can postpone this discussion till we hit an obstacle.
> 
> Best,
> Stamatis 
> 
>> On Mon, Sep 19, 2022 at 12:01 PM Simhadri G  wrote:
>> Thanks Owen, Stamatis, Ayush and Alessandro for the feedback. 
>> Regarding the javadocs and the automatically build and to deploy 
>> github-pages discussion in the previous PR thread [1],
>> Apache Iceberg-docs ([2]) has recently set up a github workflow ([3]) to 
>> publish the javadocs from a given javadocs dir [4] , I think we can setup 
>> the same workflow for Hive javadocs.
>> As Ayush and Stamatis have mentioned, I think over the past 2 years, apache 
>> infra has added support for github actions and we can confirm that from 
>> Apache Iceberg/calcite docs that are currently using it.
>> But I am not sure regarding which branch or directory we will need to put 
>> the hive javadoc files . This needs more discussion and we can follow up on 
>> this([5]) . 
>>  I am not aware about the procedure or the approvals we need to move from 
>> hive-site repo back to the main repository. We will need help with this.
>> 
>> I was able to setup the github action on the POC repo:  
>> https://github.com/simhadri-g/hive-site/tree/new-site  . 
>> Any changes to this repo/new-site will automatically reflect here once the 
>> github workflow completes: https://simhadri-g.github.io/hive-site/  .
>> 
>> Considering the feedback, I think we can plan to do in 3 phases, for the 
>> first cut I would like to update the website in the present setup, followed 
>> by moving the javadocs to the hive-site repo  and as for the third phase , 
>> we can work on migrating from hive-site to hive repo. 
>> 
>> If everyone agrees, can we please go ahead with the first phase?
>> 
>> [1]https://github.com/apache/hive/pull/1410,
>> [2]https://iceberg.apache.org/javadoc/latest/
>> [3]https://github.com/apache/iceberg-docs/actions/runs/3062679467/jobs/4943928455
>> [4]https://github.com/apache/iceberg-docs/tree/main/javadoc
>> [5]https://github.com/apache/hive/pull/1410#issuecomment-680111530
>> [6] https://github.com/apache/hive/pull/1410#issuecomment-680102815
>> 
>> 
>> Thanks!
>> Simhadri G
>> 
>>> On Mon, Sep 19, 2022 at 1:50 PM Alessandro Solimando 
>>>  wrote:
>>> Hi everyone,
>>> thanks Simhadri for pushing this forward.
>>> 
>>> I like the look and feel of the new website, and I agree with Stamatis that 
>>> having the website sources in the Hive repo, and automatically publishing 
>>> the site upon commits would be very beneficial.
>>> 
>>> Best regards,
>>> Alessandro
>>> 
 On Thu, 15 Sept 2022 at 23:11, Stamatis Zampetakis  
 wrote:
 Hi all,
 
 It's great to see some effort in improving the website. The POC from 
 Simhadri looks really cool; I didn't check the content but I love the look 
 and feel.
 
 Now regarding the current process for modifying and updating the website 
 there is some info in this relatively recent thread [1].
 
 Moving forward, I would really like to have the source code of the website 
 (markdown etc) in the main repo of the project [2], and use GitHub actions 
 to automatically build and push the content to the site repo [3] per 
 commit basis.
 This workflow is used in Apache Calcite and I find it extremely convenient.
 
 Best,
 Stamatis