ETS move to github complete

classic Classic list List threaded Threaded
21 messages Options
12
Reply | Threaded
Open this post in threaded view
|

ETS move to github complete

Ilan Schnell
Hello everyone,

Anthony any I are happy to announce that the svn git
conversion of all ETS projects is complete.  All projects
can be found under: https://github.com/enthought/
For example:
https://github.com/enthought/traits

I have verified that all svn tags correspond (diff -r) to all
git tags.  Anthony finished some documentation
improvement.  Now we have, e.g.:
http://enthought.github.com/traits/

To get-up and running:
1.) Install git
2.) Download https://github.com/enthought/ets/raw/master/ets.py
3.) Run the following
    $ mkdir ETS
    $ cd ETS    # and copy ets.py here
    $ python ets.py clone
    $ python ets.py develop
4.) Get a github user account, and let us know your github account
    name so we can grant you push permissions.

We hope everyone likes the change as much as we do.

Best   Ilan and Anthony
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

Ilan Schnell
I just noticed, that if you're getting an error of the form:
Permission denied (publickey).
fatal: The remote end hung up unexpectedly

Do the following change in ets.py:
< ets_url = "[hidden email]:enthought/%s.git"
---
> ets_url = "<a href="https://github.com/enthought/%s.git">https://github.com/enthought/%s.git"

- Ilan


On Fri, Jan 28, 2011 at 2:22 AM, Ilan Schnell <[hidden email]> wrote:

> Hello everyone,
>
> Anthony any I are happy to announce that the svn git
> conversion of all ETS projects is complete.  All projects
> can be found under: https://github.com/enthought/
> For example:
> https://github.com/enthought/traits
>
> I have verified that all svn tags correspond (diff -r) to all
> git tags.  Anthony finished some documentation
> improvement.  Now we have, e.g.:
> http://enthought.github.com/traits/
>
> To get-up and running:
> 1.) Install git
> 2.) Download https://github.com/enthought/ets/raw/master/ets.py
> 3.) Run the following
>    $ mkdir ETS
>    $ cd ETS    # and copy ets.py here
>    $ python ets.py clone
>    $ python ets.py develop
> 4.) Get a github user account, and let us know your github account
>    name so we can grant you push permissions.
>
> We hope everyone likes the change as much as we do.
>
> Best   Ilan and Anthony
>
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

John Wiggins
Can't you also fix this by adding your public key to your github account?

On Fri, Jan 28, 2011 at 3:16 AM, Ilan Schnell <[hidden email]> wrote:
I just noticed, that if you're getting an error of the form:
Permission denied (publickey).
fatal: The remote end hung up unexpectedly

Do the following change in ets.py:
< ets_url = "[hidden email]:enthought/%s.git"
---
> ets_url = "<a href="https://github.com/enthought/%s.git" target="_blank">https://github.com/enthought/%s.git"

- Ilan


On Fri, Jan 28, 2011 at 2:22 AM, Ilan Schnell <[hidden email]> wrote:
> Hello everyone,
>
> Anthony any I are happy to announce that the svn git
> conversion of all ETS projects is complete.  All projects
> can be found under: https://github.com/enthought/
> For example:
> https://github.com/enthought/traits
>
> I have verified that all svn tags correspond (diff -r) to all
> git tags.  Anthony finished some documentation
> improvement.  Now we have, e.g.:
> http://enthought.github.com/traits/
>
> To get-up and running:
> 1.) Install git
> 2.) Download https://github.com/enthought/ets/raw/master/ets.py
> 3.) Run the following
>    $ mkdir ETS
>    $ cd ETS    # and copy ets.py here
>    $ python ets.py clone
>    $ python ets.py develop
> 4.) Get a github user account, and let us know your github account
>    name so we can grant you push permissions.
>
> We hope everyone likes the change as much as we do.
>
> Best   Ilan and Anthony
>
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev


_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

Darren Dale
I think the "[hidden email]:" protocol requires write permissions to
the repository being accessed. The "https://github.com" protocol is
read-only.

On Fri, Jan 28, 2011 at 9:53 AM, John Wiggins <[hidden email]> wrote:

> Can't you also fix this by adding your public key to your github account?
>
> On Fri, Jan 28, 2011 at 3:16 AM, Ilan Schnell <[hidden email]>
> wrote:
>>
>> I just noticed, that if you're getting an error of the form:
>> Permission denied (publickey).
>> fatal: The remote end hung up unexpectedly
>>
>> Do the following change in ets.py:
>> < ets_url = "[hidden email]:enthought/%s.git"
>> ---
>> > ets_url = "<a href="https://github.com/enthought/%s.git">https://github.com/enthought/%s.git"
>>
>> - Ilan
>>
>>
>> On Fri, Jan 28, 2011 at 2:22 AM, Ilan Schnell <[hidden email]>
>> wrote:
>> > Hello everyone,
>> >
>> > Anthony any I are happy to announce that the svn git
>> > conversion of all ETS projects is complete.  All projects
>> > can be found under: https://github.com/enthought/
>> > For example:
>> > https://github.com/enthought/traits
>> >
>> > I have verified that all svn tags correspond (diff -r) to all
>> > git tags.  Anthony finished some documentation
>> > improvement.  Now we have, e.g.:
>> > http://enthought.github.com/traits/
>> >
>> > To get-up and running:
>> > 1.) Install git
>> > 2.) Download https://github.com/enthought/ets/raw/master/ets.py
>> > 3.) Run the following
>> >    $ mkdir ETS
>> >    $ cd ETS    # and copy ets.py here
>> >    $ python ets.py clone
>> >    $ python ets.py develop
>> > 4.) Get a github user account, and let us know your github account
>> >    name so we can grant you push permissions.
>> >
>> > We hope everyone likes the change as much as we do.
>> >
>> > Best   Ilan and Anthony
>> >
>> _______________________________________________
>> Enthought-Dev mailing list
>> [hidden email]
>> https://mail.enthought.com/mailman/listinfo/enthought-dev
>
>
> _______________________________________________
> Enthought-Dev mailing list
> [hidden email]
> https://mail.enthought.com/mailman/listinfo/enthought-dev
>
>
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

Chris Colbert
In reply to this post by Ilan Schnell
Sooo much better than SNV. Thanks you two for doing this!
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

Chris Colbert
s/SNV/SVN

On Fri, Jan 28, 2011 at 10:19 AM, Chris Colbert <[hidden email]> wrote:
Sooo much better than SNV. Thanks you two for doing this!


_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

Anthony Scopatz
In reply to this post by Chris Colbert
No Problem!  Also, what is your github account name so we can add you?

On Fri, Jan 28, 2011 at 3:19 PM, Chris Colbert <[hidden email]> wrote:
Sooo much better than SNV. Thanks you two for doing this!
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

Chris Colbert

On Fri, Jan 28, 2011 at 12:43 PM, Anthony Scopatz <[hidden email]> wrote:
No Problem!  Also, what is your github account name so we can add you?



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

bryce hendrix-2
What are we doing w/ Trac? Are we dumping it all together & moving to github to track issues, or are we going to install a git plugin for Trac?

On Fri, Jan 28, 2011 at 12:27 PM, Chris Colbert <[hidden email]> wrote:

On Fri, Jan 28, 2011 at 12:43 PM, Anthony Scopatz <[hidden email]> wrote:
No Problem!  Also, what is your github account name so we can add you?



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

Travis Oliphant

On Jan 28, 2011, at 2:35 PM, bryce hendrix wrote:

What are we doing w/ Trac? Are we dumping it all together & moving to github to track issues, or are we going to install a git plugin for Trac?


We haven't fully decided, I don't think.    I would prefer that we used the github issue tracking and move away from Trac entirely.   What do others think? 

-Travis


On Fri, Jan 28, 2011 at 12:27 PM, Chris Colbert <[hidden email]> wrote:

On Fri, Jan 28, 2011 at 12:43 PM, Anthony Scopatz <[hidden email]> wrote:
No Problem!  Also, what is your github account name so we can add you?



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev


_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev

---
Travis Oliphant
Enthought, Inc.
1-512-536-1057




_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

Ilan Schnell
+10 for github issue tracker

- Ilan

On Fri, Jan 28, 2011 at 2:37 PM, Travis Oliphant <[hidden email]> wrote:

>
> On Jan 28, 2011, at 2:35 PM, bryce hendrix wrote:
>
> What are we doing w/ Trac? Are we dumping it all together & moving to github
> to track issues, or are we going to install a git plugin for Trac?
>
>
> We haven't fully decided, I don't think.    I would prefer that we used the
> github issue tracking and move away from Trac entirely.   What do others
> think?
> -Travis
>
> On Fri, Jan 28, 2011 at 12:27 PM, Chris Colbert <[hidden email]> wrote:
>>
>> On Fri, Jan 28, 2011 at 12:43 PM, Anthony Scopatz <[hidden email]>
>> wrote:
>>>
>>> No Problem!  Also, what is your github account name so we can add you?
>>>
>>
>> https://github.com/sccolbert
>> _______________________________________________
>> Enthought-Dev mailing list
>> [hidden email]
>> https://mail.enthought.com/mailman/listinfo/enthought-dev
>>
>
> _______________________________________________
> Enthought-Dev mailing list
> [hidden email]
> https://mail.enthought.com/mailman/listinfo/enthought-dev
>
> ---
> Travis Oliphant
> Enthought, Inc.
> [hidden email]
> 1-512-536-1057
> http://www.enthought.com
>
>
>
> _______________________________________________
> Enthought-Dev mailing list
> [hidden email]
> https://mail.enthought.com/mailman/listinfo/enthought-dev
>
>
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

bryce hendrix-2
In reply to this post by Travis Oliphant


On Fri, Jan 28, 2011 at 12:37 PM, Travis Oliphant <[hidden email]> wrote:

On Jan 28, 2011, at 2:35 PM, bryce hendrix wrote:

What are we doing w/ Trac? Are we dumping it all together & moving to github to track issues, or are we going to install a git plugin for Trac?


We haven't fully decided, I don't think.    I would prefer that we used the github issue tracking and move away from Trac entirely.   What do others think? 

Fine with me as long as someone ports the "good" pages and the "still relevant" issues. Its the latter that might prove painful.

Bryce

_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

Ilan Schnell
Porting could just mean creating a link in the github issue to the
existing issue in Trac.

- Ilan

On Fri, Jan 28, 2011 at 2:41 PM, bryce hendrix <[hidden email]> wrote:

>
>
> On Fri, Jan 28, 2011 at 12:37 PM, Travis Oliphant <[hidden email]>
> wrote:
>>
>> On Jan 28, 2011, at 2:35 PM, bryce hendrix wrote:
>>
>> What are we doing w/ Trac? Are we dumping it all together & moving to
>> github to track issues, or are we going to install a git plugin for Trac?
>>
>>
>> We haven't fully decided, I don't think.    I would prefer that we used
>> the github issue tracking and move away from Trac entirely.   What do others
>> think?
>
> Fine with me as long as someone ports the "good" pages and the "still
> relevant" issues. Its the latter that might prove painful.
> Bryce
> _______________________________________________
> Enthought-Dev mailing list
> [hidden email]
> https://mail.enthought.com/mailman/listinfo/enthought-dev
>
>
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

bryce hendrix-2
On Fri, Jan 28, 2011 at 12:47 PM, Ilan Schnell <[hidden email]> wrote:
Porting could just mean creating a link in the github issue to the
existing issue in Trac.



Yeah, I'd settle for that, I suppose, but I'd really, really like if we could clean up a lot of old tickets at the same time. Anyone want to volunteer to trim the tickets?

Bryce

_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

Anthony Scopatz
Actually, I prefer the situation as it stands now: Issues (0).  ;)

There are also redmine-github hooks that I have seen.  I am not sure how well they work.  

However, the benefit of everything being in one place on github is fairly high.

Be Well
Anthony

On Fri, Jan 28, 2011 at 8:49 PM, bryce hendrix <[hidden email]> wrote:
On Fri, Jan 28, 2011 at 12:47 PM, Ilan Schnell <[hidden email]> wrote:
Porting could just mean creating a link in the github issue to the
existing issue in Trac.



Yeah, I'd settle for that, I suppose, but I'd really, really like if we could clean up a lot of old tickets at the same time. Anyone want to volunteer to trim the tickets?

Bryce

_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev



_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

Gael Varoquaux
In reply to this post by Ilan Schnell
On Fri, Jan 28, 2011 at 02:39:38PM -0600, Ilan Schnell wrote:
> +10 for github issue tracker

IMHO, the github issue tracker is really bad. It's the only thing I don't
like about github. But:

    1. I haven't found an issue tracker that I really like
    2. It simplifies things to give up completely on trac

So I am +0 for the github issue tracker.

G
_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

bryce hendrix-2
On Fri, Jan 28, 2011 at 2:39 PM, Gael Varoquaux <[hidden email]> wrote:
On Fri, Jan 28, 2011 at 02:39:38PM -0600, Ilan Schnell wrote:
> +10 for github issue tracker

IMHO, the github issue tracker is really bad. It's the only thing I don't
like about github. But:

   1. I haven't found an issue tracker that I really like
   2. It simplifies things to give up completely on trac

So I am +0 for the github issue tracker.


I am +1 on ditching trac. For a few reasons: 

1. historical tickets with vague descriptions, like a ticket I just closed, "Make Enable Faster" need to go away.
2. We need to be able to reference commits from tickets and tickets from commits.
3. I find its UI cumbersome for updating multiple tickets.

I'd really, really appreciate some help in cleaning out old tickets. Pick a subproject you're familiar with, and close any ticket that has been fixed, is no longer relevant, or too vague, or you know we'll never get to. I've closed 30 or so today so far, only 396 to go.

If no one starts volunteering, I'll start handing out homework assignments...

Bryce

_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

Gael Varoquaux
On Fri, Jan 28, 2011 at 02:57:14PM -0800, bryce hendrix wrote:
>    I'd really, really appreciate some help in cleaning out old tickets. Pick
>    a subproject you're familiar with, and close any ticket that has been
>    fixed, is no longer relevant, or too vague, or you know we'll never get
>    to.

That's the real issue: doing work.

>    I've closed 30 or so today so far, only 396 to go. If no one starts
>    volunteering, I'll start handing out homework assignments...

I am drowning. I might not do my homework. Sorry,

Ga�l

_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

Jonathan Guyer
In reply to this post by bryce hendrix-2

On Jan 28, 2011, at 5:57 PM, bryce hendrix wrote:

> I am +1 on ditching trac. For a few reasons:

I have no dog in this fight, but...



> 1. historical tickets with vague descriptions, like a ticket I just closed, "Make Enable Faster" need to go away.

This sort of seems like "we need to do the dishes, so let's burn the house down."  8^)


> 2. We need to be able to reference commits from tickets and tickets from commits.

Trac has this. ticket:123 in commits, r54321 in ticket comments.


> 3. I find its UI cumbersome for updating multiple tickets.

This looks promising: http://trac-hacks.org/wiki/BatchModifyPlugin


_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
Reply | Threaded
Open this post in threaded view
|

Re: ETS move to github complete

bryce hendrix-2
On Fri, Jan 28, 2011 at 5:24 PM, Jonathan Guyer <[hidden email]> wrote:

On Jan 28, 2011, at 5:57 PM, bryce hendrix wrote:

> I am +1 on ditching trac. For a few reasons:

I have no dog in this fight, but...



> 1. historical tickets with vague descriptions, like a ticket I just closed, "Make Enable Faster" need to go away.

This sort of seems like "we need to do the dishes, so let's burn the house down."  8^)


I can't disagree. Moving 400 tickets to github by hand could help solve this though.
 

> 2. We need to be able to reference commits from tickets and tickets from commits.

Trac has this. ticket:123 in commits, r54321 in ticket comments.


Yes, but we either need a git plugin for trac now, if we continue using trac.
 

> 3. I find its UI cumbersome for updating multiple tickets.

This looks promising: http://trac-hacks.org/wiki/BatchModifyPlugin

I'll have to look at that, thx.

Bryce

_______________________________________________
Enthought-Dev mailing list
[hidden email]
https://mail.enthought.com/mailman/listinfo/enthought-dev
12