@lresende, just wanted to check in about the state of merging the PR that Gino mentioned. Submitter claims to have signed the ICLA; so, we need to know whether or not we should wait until after the move to roll it in. This also brings up if there is a way for submitters to not need to sign the ICLA (as they do not with Apache Spark, I believe), since I imagine it will be hard to keep track of who has and has not signed the ICLA in the near future.
On Fri, Jan 8, 2016 at 6:28 PM Gino Bustelo <[email protected]> wrote: > Yep. Just heard back from GitHub support. > > We will just leave the issue tracker there until we migrate them to Apache > and then turn off the feature altogether. > > Gino B. > > > On Jan 8, 2016, at 5:45 PM, Julien Le Dem <[email protected]> wrote: > > > > I don’t think you can unfortunately. > > Disabling issues will hide the history. > > > >> On Jan 8, 2016, at 9:22 AM, Gino Bustelo <[email protected]> wrote: > >> > >> There are no PRs that we should wait for or ready to be merge. > >> > >> The repository has been set to read-only. > >> > >> Not sure how to disable NEW issues and PR without removing the entire > >> feature from the project. > >> > >> Is this what you've done in the past? > >> https://help.github.com/articles/disabling-issues/ > >> > >> Gino > > >
