Log file Viewer
Help
|
Karma
| Search:
#dcpython logs for Tuesday the 7th of August, 2012
(
Back to #dcpython overview
) (
Back to channel listing
) (
Animate logs
)
[
16:50:34
] <
aclark
> jaraco: you got rfa's number right?
[
17:05:50
] <
jaraco
> aclark: I do now. Thanks.
[
17:06:36
] <
jaraco
> where are the slides again?
[
17:08:44
] <
aclark
> !google dc python generic meetup slides
[
17:08:44
] <
pmxbot
> http://www.slideshare.net/dcpython/generic-meetup-slides - Generic meetup slides
[
17:08:52
] <
aclark
> jaraco: ^
[
17:33:23
] <
jaraco
> !thanks aclark
[
17:33:23
] <
pmxbot
> you're doing good work, aclark!
[
17:43:14
] <
aclark
> J1m: Any chance we can move the old buildout code to github?
[
17:51:23
] <
J1m
> aclark, I have no idea what you're talking about.
[
17:55:07
] <
aclark
> J1m: zc.buildout source in svn.zope.org, can it move to github? (next to where you are currently working on buildout2)
[
17:57:16
] <
J1m
> It was moved, but I don't particularly want to see version 1 maintained there.
[
17:58:17
] <
aclark
> J1m: ah ok
[
17:58:57
] <
J1m
> I suppose my arm can be twisted, but I really don't see the point.
[
17:59:40
] <
aclark
> J1m: well i think folks want to get a 1.5.3 out the door and possible maintain the 1.x series a bit longer
[
18:00:18
] <
J1m
> Do those folks not have subversion access?
[
18:00:39
] <
aclark
> J1m: well, i have it but probably most others don't
[
18:00:52
] <
J1m
> Most others who?
[
18:01:32
] <
J1m
> There was this idea that moving the code to github would release a flood of volunteers, but I'm not seeing it.
[
18:03:50
] <
aclark
> J1m: e.g. https://twitter.com/iElectric/status/231874083397177345 and you can follow the thread up
[
18:04:17
] <
J1m
> I saw that thread. It looks like BS to me.
[
18:04:30
] <
J1m
> Twitter is a stupid place for discussion IMO.
[
18:04:33
] <
aclark
> J1m: what if I get Ross to resubmit his patch on github?
[
18:04:35
] <
aclark
> hah true
[
18:04:59
] <
aclark
> seems like svn.zope.org/zc.buildout should be marked closed as well
[
18:05:21
] <
J1m
> which patch, the optimization patch?
[
18:05:21
] <
aclark
> (if it's not already)
[
18:05:25
] <
aclark
> right
[
18:05:54
] <
J1m
> His optimization patch was in the 1.4 branch afaict and is included in 2.
[
18:06:06
] <
J1m
> I think it's in the svn trunk.
[
18:06:48
] <
J1m
> He has access to svn.zope.com so if he wants to make a 1.5.3 release, he has everything he needs afaict.
[
18:07:12
] <
J1m
> btw, I asked him to verify that his patch was in the git master and he never replied.
[
18:08:08
] <
aclark
> J1m: ok you want to add me to https://pypi.python.org/pypi/zc.buildout/1.5.2 and i'll push this along?
[
18:08:52
] <
J1m
> I assume you mean https://pypi.python.org/pypi/zc.buildout
[
18:08:56
] <
J1m
> sure.
[
18:09:05
] <
aclark
> i can do a release when appropriate (i.e. when i'm sure it won't be worse than 1.5.2)
[
18:09:07
] <
J1m
> Someone should make sure the tests pass on windows.
[
18:09:07
] <
aclark
> right
[
18:09:16
] <
aclark
> Yeah I will do that first
[
18:09:17
] <
J1m
> thanks.
[
18:09:23
] <
aclark
> np
[
18:09:30
] <
J1m
> what's your pypi id?
[
18:09:34
] <
aclark
> aclark
[
18:09:48
] <
aclark
> So should we release from svn or can this all be done on github?
[
18:11:48
] <
J1m
> I would prefer to release 1 from svn, but I'm willing to defer.
[
18:12:21
] <
J1m
> The svntrunk branch in github should be pretty close to the svn trunk.
[
18:12:46
] <
aclark
> ok i'll look at that too
[
18:14:20
] <
J1m
> The master branch was made from the svn 1.4 branch, so someone could conceivably make a 1.4 branch from an early version of that, assuming that's possible w got.
[
18:14:23
] <
J1m
> s/got/git
[
18:14:56
] <
J1m
> btw, if you're going to get involved, you should join: https://groups.google.com/forum/?fromgroups#!forum/buildout-development
[
18:15:40
] <
J1m
> I'm trying to give you access in pypi. but it keeps timing out. I wish I had time to rewrite pypi as a simple bobo app. sigh
[
18:23:26
] <
aclark
> J1m: yeah trying to figure out how to join the group
[
18:27:30
] <
aclark
> I can favorite it :-)
[
18:27:32
] <
aclark
> confusing UI
[
18:27:41
] <
J1m
> aclark, I'll have to add you to pypi some time when it isn't so cranky.
[
18:27:55
] <
aclark
> J1m: k
[
18:28:28
] <
J1m
> google groups got a lot weirder a few months back.
[
18:28:37
] <
J1m
> It used to be pretty straightforward.
[
18:30:05
] <
aclark
> Oh maybe this is the prob: Access to public Google Groups has been restricted by your domain admin.
[
18:31:16
] <
J1m
> um
[
18:31:26
] <
J1m
> anyway, I sent you an invite.
[
18:32:20
] <
aclark
> thanks
[
18:39:54
] <
aclark
> J1m: I guess add me to the github org too, what are your concerns if we start working in there?
[
18:40:22
] <
aclark
> (everyone loves teh githubs)
[
18:50:25
] <
iElectri1
> hi
[
18:50:27
] <
aclark
> iElectri1: yo
[
18:50:54
] <
aclark
> J1m: can you add me to the buildout org too?
[
18:52:21
] <
J1m
> My concern is that I didn't set up that github repo to be used for making buildout 1 releases.
[
18:52:45
] <
J1m
> I also don't see the point.
[
18:52:50
] <
iElectric
> J1m: it might benefit in future to have that on github in case we want to backport commits
[
18:53:11
] <
J1m
> or in case pigs fly.
[
18:53:51
] <
J1m
> someone will at least have to screw around with the setup file to make releases from git work, but, whatever...
[
18:54:22
] <
J1m
> Using it for this feels like extra work just to be fashionable..... but again, whatever....
[
18:54:49
] <
iElectric
> there is always fun to tinker the toy
[
18:56:05
] <
J1m
> aclark, you are now a member.
[
18:56:40
] <
aclark
> J1m: thanks, i think it's just easier to collab there (even if it's more work software-wise)
[
18:59:25
] <
aclark
> iElectric: ok so you want to send a pull request and i'll merge to the svntrunk branch?
[
19:13:45
] <
iElectric
> aclark: sure
[
19:14:04
] <
iElectric
> trying to find a way to add svn repo to git svn