Hi Kyle, Fixing the website is a crucial next step. Thanks for this valuable contribution. IIUC, as the first step, you will need to create a fork of apache/xtable repo and create a pull request from the fork.
Best, Ashvin On Wed, Feb 28, 2024 at 10:49 PM Kyle Weller <k...@onehouse.ai> wrote: > @Jesus and @Vinoth, the PR is ready, looks like I don't have permissions to > push to a branch: > > > > *git push origin website_renameremote: Permission to > apache/incubator-xtable.git denied to kywe665.* > *fatal: unable to access 'https://github.com/apache/incubator-xtable.git/ > <https://github.com/apache/incubator-xtable.git/>': The requested URL > returned error: 403* > > I assume I need to be added as a contributor in the fresh project. My > github handle is kywe665 > > Thanks, > Kyle > > On Wed, Feb 28, 2024 at 5:09 PM Kyle Weller <k...@onehouse.ai> wrote: > > > I have started work on the website and docs to change all names, images, > > references from OneTable -> XTable. I hope to have a PR soon. > > > > I recommend for the website update we break it in two phases for > > incremental speed. First PR will do all the text/img/ref name change > above, > > but it will not have adjusted the website code into separate repo/etc. I > > recommend we do this part ASAP while in parallel we start the discuss > > thread and infra request for next website adjustment. This will quickly > > unblock us from sharing all resources, mailing lists, links, etc, and > will > > quickly get the website inline with the now repo migration. > > > > This sound good? > > > > On Wed, Feb 28, 2024 at 4:34 PM Jesus Camacho Rodriguez < > > jcama...@apache.org> wrote: > > > >> Thanks, Vinoth! > >> > >> A lot of work is ahead of us, but it's fantastic to see the repo already > >> under the Apache org :) > >> > >> As of now, I haven't created any issues or started any work. [1] > provides > >> some good guidelines for what should be our next steps. Here are a few > >> ideas: > >> - Ensure source files use the standard Apache boilerplate headers, > NOTICE > >> and LICENSE are correct, etc. > >> - Repackaging the code. Concretely, move it under the apache namespace, > >> i.e., org.apache.xtable. > >> - Refactoring the code. Concretely, OneTable entity references should be > >> substituted by either something generic or XTable. > >> - Updating documentation. > >> - Determine the path forward for the XTable website under ASF (we can > >> start > >> a DISCUSS thread). It seems some ASF projects have a separate repository > >> to > >> host the website and then enable GitHub pages. That seems a good path > >> forward. If we choose this path, we can start by requesting a new repo > >> from > >> INFRA. > >> - We should probably highlight as well how to reach out to the community > >> (i.e., mailing lists, Slack channel, etc.), most people probably have no > >> idea yet. > >> - Discuss any review/contribution guidelines that should be established > in > >> the mailing list, e.g., if the contributor is a committer, do we enforce > >> code reviews by a different person than the contributor, or do we leave > it > >> at the committer discretion? > >> > >> -Jesús > >> > >> > >> [1] > >> > >> > https://incubator.apache.org/guides/transitioning_asf.html#initial_clean_up > >> > >> > >> On Wed, Feb 28, 2024 at 3:59 PM Vinoth Chandar <vin...@apache.org> > wrote: > >> > >> > Hi all, > >> > > >> > Now that we have moved the repo over to ASF officially. Love to chip > in > >> > with any cleanups. > >> > > >> > Jesus - you were probably driving a bunch of these. Please lmk if > there > >> are > >> > issues I can pick up. > >> > > >> > Thanks > >> > Vinoth > >> > > >> > > >
