[Pandas-dev] Our own GitHub organization?

[Jeff Reback]

fine by me

I can be reached on my cell 917-971-6387

> On Oct 12, 2016, at 5:48 PM, Joris Van den Bossche <jorisvandenbossche at gmail.com> wrote:
> 
> Let's do it
> 
> No answer yet from the 'pandas' user?
> 
> 2016-10-12 23:27 GMT+02:00 Wes McKinney <wesmckinn at gmail.com>:
>> How do you all feel about moving the repos to github.com/pandas-dev?
>> 
>> On Tue, Sep 6, 2016 at 10:24 AM, Jeff Reback <jeffreback at gmail.com> wrote:
>> > no it was for the announcement and doc changes that matter here
>> > the redirects should be fine
>> >
>> >
>> > On Sep 6, 2016, at 10:20 AM, Joris Van den Bossche
>> > <jorisvandenbossche at gmail.com> wrote:
>> >
>> > I am not sure that it has to wait until the actual 0.19.0 release (we can
>> > certainly announce it then, but doing the transition earlier does not seem a
>> > problem given all redirects. Or Jeff, are you thinking of other problems?).
>> > But as Tom suggested, maybe we can wait until after the rc just to prevent
>> > possible short-term problems with travis etc that have to be fixed just
>> > before the rc.
>> >
>> > Joris
>> >
>> > 2016-09-05 17:48 GMT+02:00 Jeff Reback <jeffreback at gmail.com>:
>> >>
>> >>
>> >> I think this would need to wait for the actual 0.19.0 release to be live
>> >> so it can be announced - lots more folks read the whatsnew that are on the
>> >> mailing list
>> >> also we are changing links in the docs
>> >>
>> >> On Sep 5, 2016, at 11:17 AM, Jeff Reback <jeffreback at gmail.com> wrote:
>> >>
>> >> +1 in this
>> >>
>> >> On Sep 5, 2016, at 10:42 AM, Tom Augspurger <tom.augspurger88 at gmail.com>
>> >> wrote:
>> >>
>> >> I just migrated a repo and it was painless. Is there a reason to wait till
>> >> after the release candidate?
>> >>
>> >> On Mon, Sep 5, 2016 at 9:34 AM, Joris Van den Bossche
>> >> <jorisvandenbossche at gmail.com> wrote:
>> >>>
>> >>> I am positive on a move (although the 'pandas' org would be nice), so OK
>> >>> with going ahead.
>> >>>
>> >>> Joris
>> >>>
>> >>> 2016-09-05 16:04 GMT+02:00 Wes McKinney <wesmckinn at gmail.com>:
>> >>>>
>> >>>> What does everyone think about going ahead with the move? I imagine
>> >>>> there are a variety of services (e.g. Travis CI and others) we'll need
>> >>>> to migrate over concurrently. Want to avoid possible disruptions to
>> >>>> day-to-day development (luckily GitHub has made this mostly painless
>> >>>> in my experience).
>> >>>>
>> >>>> On Tue, Aug 23, 2016 at 5:42 PM, Wes McKinney <wesmckinn at gmail.com>
>> >>>> wrote:
>> >>>> > I've parked github.com/pandas-dev for the time being. Interested to
>> >>>> > see what others think about the migration
>> >>>> >
>> >>>> > On Tue, Aug 23, 2016 at 12:25 PM, Stephan Hoyer <shoyer at gmail.com>
>> >>>> > wrote:
>> >>>> >> Too bad about the "pandas" GitHub name. Still, if you want to go for
>> >>>> >> this, I
>> >>>> >> say you should go ahead.
>> >>>> >>
>> >>>> >> My sense (have not checked actual data here) is that all other
>> >>>> >> projects than
>> >>>> >> pandas add a very minimal amount of CI burden, though.
>> >>>> >>
>> >>>> >> On Tue, Aug 23, 2016 at 12:06 PM, Wes McKinney <wesmckinn at gmail.com>
>> >>>> >> wrote:
>> >>>> >>>
>> >>>> >>> According to GitHub, the pandas account is showing activity that is
>> >>>> >>> not publicly visible. I've contacted the user twice in an effort to
>> >>>> >>> start a dialog but GitHub is very strict about protecting users'
>> >>>> >>> privacy.
>> >>>> >>>
>> >>>> >>> We could do something like @pandas-org for the time being, and hope
>> >>>> >>> that at some point we are able to contact the @pandas user (or they
>> >>>> >>> become inactive).
>> >>>> >>>
>> >>>> >>> - Wes
>> >>>> >>>
>> >>>> >>> On Tue, Aug 23, 2016 at 11:49 AM, Stephan Hoyer <shoyer at gmail.com>
>> >>>> >>> wrote:
>> >>>> >>> > Did you have any luck going through GitHub's process for
>> >>>> >>> > reclaiming an
>> >>>> >>> > unused name? You don't necessarily need to contact the account
>> >>>> >>> > owner for
>> >>>> >>> > this.
>> >>>> >>> > https://help.github.com/articles/name-squatting-policy/
>> >>>> >>> >
>> >>>> >>> > I'm +1 for switching to a dedicated pandas org. GitHub's redirects
>> >>>> >>> > do
>> >>>> >>> > make
>> >>>> >>> > this quite smooth.
>> >>>> >>> >
>> >>>> >>> > The main reason I switched xarray to pydata (from the separate
>> >>>> >>> > xray org)
>> >>>> >>> > is
>> >>>> >>> > because I didn't think I would be successful claiming xarray,
>> >>>> >>> > which
>> >>>> >>> > appears
>> >>>> >>> > to be in active use.
>> >>>> >>> >
>> >>>> >>> > On Tue, Aug 23, 2016 at 11:40 AM, Wes McKinney
>> >>>> >>> > <wesmckinn at gmail.com>
>> >>>> >>> > wrote:
>> >>>> >>> >>
>> >>>> >>> >> We've occasionally discussed moving pandas and associated repos
>> >>>> >>> >> to a
>> >>>> >>> >> dedicated GitHub organization.
>> >>>> >>> >>
>> >>>> >>> >> Some arguments for moving to our own org:
>> >>>> >>> >>
>> >>>> >>> >> - More clear what repositories are part of the "pandas" umbrella
>> >>>> >>> >> (we
>> >>>> >>> >> can potentially formalize this in the pandas-governance repo)
>> >>>> >>> >>
>> >>>> >>> >> - Dedicated capacity from CI services
>> >>>> >>> >>
>> >>>> >>> >> - Easier for us to more clearly develop our own open source
>> >>>> >>> >> project
>> >>>> >>> >> branding independent from PyData (which has increasingly
>> >>>> >>> >> primarily
>> >>>> >>> >> become a conference / meetup brand)
>> >>>> >>> >>
>> >>>> >>> >> While I haven't had any success contacting the owner of
>> >>>> >>> >> github.com/pandas, if we can pick a suitable org name we might
>> >>>> >>> >> consider it. GitHub's route forwarding (including git remotes)
>> >>>> >>> >> makes
>> >>>> >>> >> org changes pretty painless these days
>> >>>> >>> >>
>> >>>> >>> >> Thoughts?
>> >>>> >>> >>
>> >>>> >>> >> - Wes
>> >>>> >>> >> _______________________________________________
>> >>>> >>> >> Pandas-dev mailing list
>> >>>> >>> >> Pandas-dev at python.org
>> >>>> >>> >> https://mail.python.org/mailman/listinfo/pandas-dev
>> >>>> >>> >
>> >>>> >>> >
>> >>>> >>
>> >>>> >>
>> >>>> _______________________________________________
>> >>>> Pandas-dev mailing list
>> >>>> Pandas-dev at python.org
>> >>>> https://mail.python.org/mailman/listinfo/pandas-dev
>> >>>
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> Pandas-dev mailing list
>> >>> Pandas-dev at python.org
>> >>> https://mail.python.org/mailman/listinfo/pandas-dev
>> >>>
>> >>
>> >> _______________________________________________
>> >> Pandas-dev mailing list
>> >> Pandas-dev at python.org
>> >> https://mail.python.org/mailman/listinfo/pandas-dev
>> >
>> >
>> >
>> > _______________________________________________
>> > Pandas-dev mailing list
>> > Pandas-dev at python.org
>> > https://mail.python.org/mailman/listinfo/pandas-dev
>> >
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pandas-dev/attachments/20161012/49abc78f/attachment.html>