I think after this final pr, is will be proper to archive the repository so it doesn't look active ( https://help.github.com/en/articles/archiving-a-github-repository). It will be accessible, but read-only, and won't come up in the default GitHub search. Here's an example for such a repository (archived and with a comment): https://github.com/yahoo/druid-extensions
On Fri, Apr 26, 2019 at 11:14 AM Julian Hyde <jh...@apache.org> wrote: > One trick that people sometimes use is to create a new branch called > “obsolete” or similar, update the README in that branch to point to the new > project location, and make that branch the default branch in GitHub. > > > On Apr 26, 2019, at 11:02 AM, Gian Merlino <g...@apache.org> wrote: > > > > That makes sense to me. Are you interested in doing a PR to the > > docker-druid repo to make its README point to the new Dockerfiles? If so, > > that should do it. > > > > On Fri, Apr 26, 2019 at 3:33 AM Jokin Cuadrado <joki...@odeian.com> > wrote: > > > >> Hi, I was searching for a way to run druid on docker for some > >> experimentation, and the first results has been a repo on the droid-io > >> organization https://github.com/druid-io/docker-druid > >> > >> I found after (Thanks to dylan pointing out in slack) that there are > newer > >> dockerfiles commited on the apache incubatin repo. > >> > >> As the ol repo sits unmodified and with some open pull request, I think > >> that cleaning the old repo, marking as deprecated and pointing to the > new > >> repo would be nice. The https://github.com/druid-io organization should > >> maybe also point to the incubator project, as the only active project > it's > >> the website code. > >> > >> Regards, > >> Jokin. > >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > For additional commands, e-mail: dev-h...@druid.apache.org > >
