I think you meant HIVE-28666 (not HIVE-28166). Makes total sense to me to move to a normal (and modern) git controlled process for the docs, although the migration could take some time. +1
On Fri, Dec 13, 2024 at 8:08 AM Simhadri G <simhadri...@gmail.com> wrote: > I fully support improving the Hive documentation, as it's long overdue. > Moving the docs to the Hive website is a great step, making it easier for > contributors to update and maintain them. > > Additionally, we can incrementally enhance the Hive website by introducing > a search feature to help users navigate the documentation more efficiently. > It would also be beneficial to version the docs with every new release, > ensuring accuracy and relevance. > > So, it's a +1 from me! > > Thanks , > Simhadri G > > On Fri, Dec 13, 2024, 8:46 PM Stamatis Zampetakis <zabe...@apache.org> > wrote: > >> Hi all, >> >> The discussion has started in some parallel threads but for >> traceability and discovery purposes I thought that it would be better >> to start a dedicated thread to be sure that it won't be missed by >> anyone. >> >> All the context and motivation is under HIVE-28166, so I will not >> repeat those here. The current PR has already some approvals but since >> this is a change that will have quite some impact on the Hive >> documentation and our contributors I wanted to be sure that there is a >> general consensus before moving forward. >> >> Please share your thoughts about the current plan described under >> HIVE-28166, even if it is simply a +/-1 >> >> Best, >> Stamatis >> >
