hi Alessandro — I just merged the PR, thank you! I would still like us to move to use ipython_directive in the authoring of Python examples so that authors do not have to copy-paste console output into the recipes, but that doesn't have to be addressed right now.
Thanks, Wes On Wed, Jul 28, 2021 at 8:28 AM Alessandro Molina <alessan...@ursacomputing.com> wrote: > > Hi everybody, > > The Cookbook PR has been open for more than a week at this point and we > have received tons of great feedback and suggestions, many of which we > incorporated already. > For the benefit of being able to verify the publishing workflow and the CI > I'd love to ask if there is anyone who could merge the PR (unless there are > major blockers) as it's an apache repository and thus requires explicit > permissions. > So we can start verifying that the build process we put in place leads to > the expected results and maybe add a link to the Cookbook from the Arrow > Documentation before the new documentation gets deployed for 5.0.0 > > On Tue, Jul 20, 2021 at 12:24 PM Alessandro Molina < > alessan...@ursacomputing.com> wrote: > > > The Pull Request for the Cookbook has been created ( > > https://github.com/apache/arrow-cookbook/pull/1 ) > > I left as comments in the PR the steps that need to be done to enable > > compilation of the cookbook once the PR is merged (enabling actions, gh > > pages etc...) anyone willing to merge it should probably also take care of > > those few steps so that we can make sure that all pieces are in place. > > Thanks! > > > > On Wed, Jul 14, 2021 at 11:43 PM Wes McKinney <wesmck...@gmail.com> wrote: > > > >> I just initialized > >> > >> https://github.com/apache/arrow-cookbook > >> > >> On Wed, Jul 14, 2021 at 1:33 PM Wes McKinney <wesmck...@gmail.com> wrote: > >> > > >> > On Wed, Jul 14, 2021 at 8:33 AM Alessandro Molina > >> > <alessan...@ursacomputing.com> wrote: > >> > > > >> > > On Tue, Jul 13, 2021 at 2:40 PM Wes McKinney <wesmck...@gmail.com> > >> wrote: > >> > > > >> > > > I requested its creation here > >> > > > > >> > > > https://github.com/apache/arrow-cookbook > >> > > > > >> > > > If you can set up a PR into this repo (not sure if I need to push an > >> > > > empty "initial commit" repo, but let me know), > >> > > > >> > > > >> > > Seems your concern was correct, you can't open PRs against an empty > >> > > repository. > >> > > If you could make an initial commit that would be great. > >> > > >> > OK, will do. > >> > > >> > > > >> > > > please make sure > >> > > > everyone who has contributed has an ICLA on file with the ASF > >> > > > secretary. I'm not sure that it's necessary for us to conduct an IP > >> > > > clearance but others can comment if they disagree. > >> > > > > >> > > > >> > > I guess that http://people.apache.org/phonebook.html only covers a > >> list of > >> > > committers and PMC members, not general contributors. > >> > > Is there any way to check if any contributor has already signed an > >> ICLA? > >> > > Also, for my general understanding, should we ask to sign the ICLA > >> before > >> > > accepting/merging PRs or is it acceptable to merge PRs from occasional > >> > > contributions even in absence of a signed ICLA? > >> > > >> > Since https://github.com/ursacomputing/arrow-cookbook is "outside the > >> > Arrow community", having the contributors to this repository sign > >> > ICLAs would be a good practice before moving the code to an Apache > >> > repository. Since this codebase isn't very old and we probably won't > >> > be making official ASF releases of this project, the formal IP > >> > clearance process is likely not necessary. > >> > > >> > We don't need ICLAs from normal contributors into Apache repositories. > >> > >
