Apache Allura / Chat

Apache Allura / Chat is hosted on FreeNode IRC channel #allura

Log for 2013-08-28

  • 15:10:41
    brondsem

    i think Rich would be binding since he's one of our mentors

  • 15:13:06
    cory_fu

    I thought he wasn't any longer?

  • 15:13:22
    cory_fu

    He said something to that effect at one point, and he didn't say (binding) in his +1 email

  • 15:14:25
    brondsem

    he's still on http://incubator.apache.org/projects/allura.html and I remember him saying he'd still be happy to mentor us through incubation even though he wasn't working at SourceForge

  • 15:14:52
    cory_fu

    kk

  • 15:15:21
    brondsem

    iiuc saying "(binding)" in email is just for convenience, it doesn't actually make your vote bind to something :)

  • 15:15:47
    cory_fu

    Yeah, but I thought I remembered him saying that he wasn't technically mentoring anymore.

  • 15:17:24
    brondsem

    hm

  • 15:18:00
    brondsem

    i don't see him on IRC or skype ,to ask

  • 15:19:22
    brondsem

    seems like he's still mentoring. he's involved in more threads than any other mentor

  • 15:20:06
    cory_fu

    True. I'll put him in binding

  • 15:47:04
    brondsem

    so I just discovered that Google Code repos (hg at least) can have multiple repos e.g. http://code.google.com/p/httplib2/source/browse?repo=async2

  • 15:48:20
    brondsem

    it doesn't seem like our importer handles that

  • 15:48:40
    cory_fu

    Not at all

  • 15:49:07
    cory_fu

    They do all have to the of the same type, at least

  • 15:55:36
    brondsem

    i'll ticket it up

  • 16:01:39
    cory_fu

    Supposedly, I'm subscribed to general@incubator.apache.org but I never get emails from there.

  • 16:04:06
    brondsem

    really? :(

  • 16:04:19
    cory_fu

    Are you subscribed?

  • 16:04:33
    cory_fu

    I just re-subscribed w/ my personal email. Maybe that will work

  • 16:05:47
    brondsem

    yes, i'm subscribed and get them (personal & work emails)

  • 16:05:55
    cory_fu

    Strange

  • 17:29:03
    brondsem

    for [#6611] i wonder if a general way to disable entry points would be good

  • 17:29:35
    brondsem

    wouldnt' matter for some entry points

  • 17:29:59
    brondsem

    but could be useful for some packages that might provide several entry points and you only want one. template overriding comes to mind as something you might want to disable

  • 17:40:25
    tvansteenburgh

    i still think it wouldn't be a bad idea to start using stevedore for our entry point mgmt

  • 17:40:30
    tvansteenburgh

    at some point

  • 17:43:02
    brondsem

    yeah i was just looking at it to see how it handled it

  • 17:52:24
    brondsem

    not sure it would help much in this case http://stevedore.readthedocs.org/en/latest/managers.html#enabledextensionmanager still would require us to set up the check function

  • 17:55:54
    tvansteenburgh

    oh, i was looking at the NamedExtensionManager

  • 17:56:39
    brondsem

    you have to provide the list of names for that one

  • 17:57:21
    brondsem

    seems like stevedore formalizes different patterns of dealing with extensions, but doesn't have a lot of glue or helpers around it

  • 17:58:12
    tvansteenburgh

    hm. ok, so with the one you were looking at, we'd have one global check_func that would see if the EP was disabled in the ini file, right?

  • 17:58:25
    brondsem

    yeah

  • 17:58:32
    brondsem

    and i'm thinking about just writing a helper function to do the same

  • 17:58:38
    cory_fu

    So you want enabled by default instead of disabled by default?

  • 17:58:50
    brondsem

    and replace iter_entry_points with the helper

  • 17:59:03
    brondsem

    and/or g.entry_points - not sure why we have that too

  • 17:59:08
    brondsem

    yes, enabled by default

  • 17:59:10
    brondsem

    is what i'm thinking

  • 17:59:16
    tvansteenburgh

    +1

  • 18:00:54
    tvansteenburgh

    question about the GH repo importer that 42cc did

  • 18:01:17
    tvansteenburgh

    they didn't do the controller that would expose the individual importer

  • 18:01:28
    tvansteenburgh

    should i add that, send it back, or was that being saved for later?

  • 18:01:55
    brondsem

    send it back, they probably just didn't know

  • 18:02:03
    tvansteenburgh

    k

  • 18:22:12
    tvansteenburgh

    i'm almost scared to find out how [#6530] conflicts with [#6526]

  • 18:23:31
    brondsem

    sooner rather than later :)

  • 18:23:43
    brondsem

    Cory's out tomorrow and github work progresses without it

  • 18:23:58
    tvansteenburgh

    i'm gonna try to rebase it to tv/6526

  • 18:24:13
    tvansteenburgh

    since that will presumable be merged soon

  • 18:24:21
    brondsem

    yes

  • 18:28:55
    tvansteenburgh

    wow, not bad at all

  • 18:29:16
    brondsem

    great

  • 18:29:26
    brondsem

    high five and a beer for somebody!

  • 18:29:29
    tvansteenburgh

    just a couple imports to clean up, \o/

  • 18:29:46
    tvansteenburgh

    i'll take a beer, cory can have the high five

  • 18:29:54
    brondsem

    haha

  • 18:30:18
    cory_fu

    No thanks. I'm a recovering high-five addict

  • 18:30:30
    tvansteenburgh

    lol

  • 18:31:12
    brondsem

    any thoughts on this syntax for controlling entry points?

  • 18:31:12
    brondsem

    disable_entry_points.allura.importers = trac-tickets

  • 18:31:13
    brondsem

    disable_entry_points.allura.project_importers = trac, github

  • 18:31:34
    cory_fu

    Could you just have a section?

  • 18:31:45
    cory_fu

    [disabled_entry_points] or whatever

  • 18:32:07
    cory_fu

    We don't use namespacing very well in our configs

  • 18:32:08
    brondsem

    i dunno. everything in [app:main] ends up on tg.config

  • 18:32:16
    brondsem

    not sure how to use another section

  • 18:32:20
    tvansteenburgh

    interesting, i was expecting just 'trac-tickets.disabled = True'

  • 18:32:42
    brondsem

    i want to have the group in there too

  • 18:32:45
    cory_fu

    +1 on tvansteenburgh's idea, if we can't do a namespace

  • 18:32:47
    brondsem

    so you can do it for anything

  • 18:33:05
    brondsem

    like admin extension points

  • 18:33:20
    brondsem

    disable_entry_points.allura.admin = importers

  • 18:33:25
    brondsem

    that turns off importing altogether

  • 18:33:32
    cory_fu

    Hrm

  • 18:33:47
    cory_fu

    I think you have that backwards, but yeah

  • 18:34:11
    brondsem

    backwards? it would disable this:

  • 18:34:12
    brondsem
      [allura.admin]
    
  • 18:34:18
    brondsem
      importers = forgeimporters.base:ImportAdminExtension
    
  • 18:34:25
    cory_fu

    Oh, I see

  • 18:34:40
    cory_fu

    That would disable the admin UI for the importers, but not the importers themselves

  • 18:34:52
    brondsem

    yeah

  • 18:34:53
    brondsem

    true

  • 18:35:12
    brondsem

    not quite as useful of an example then :)

  • 18:36:07
    tvansteenburgh

    i think 'allura.admin.importers.disabled = True` would be easier to remember, but i guess that's not doable?

  • 18:37:21
    brondsem

    yeah, not sure because theoretically you could have a [allura.admin.importers] group which would conflict then

  • 18:37:53
    tvansteenburgh

    yeah

  • 18:37:57
    brondsem

    allura.admin:importers = disabled ???

  • 18:38:32
    tvansteenburgh

    hm, that's not bad

  • 18:38:48
    tvansteenburgh

    otoh i don't want to waste time nitpicking syntax

  • 18:38:53
    cory_fu

    Yeah

  • 18:39:04
    tvansteenburgh

    i'm okay with the way it is

  • 18:39:18
    brondsem

    k

  • 18:39:18
    tvansteenburgh

    but i will always remind you that it's ugly

  • 18:39:21
    brondsem

    LOL

  • 18:39:26
    tvansteenburgh

    LOL

  • 20:20:09
    ASFBot

    Allura/292: #292 started building, estimated 13 minutes left. https://builds.apache.org/job/allura/292/

  • 20:33:51
    ASFBot

    Allura/292: #292 built successfully after 13 minutes https://builds.apache.org/job/allura/292/

  • 21:25:50
    brondsem

    so who knows the best way to query mongo to see if there's anything in project's repos?

  • 21:26:00
    brondsem

    or would checking via filesystem be better?

  • 21:27:59
    tvansteenburgh

    what's the mission?

  • 21:28:14
    brondsem

    given 150 projects, see if they've got a repo with anything in it or not

  • 21:29:10
    tvansteenburgh

    well if it were me i think i'd check the fs

  • 21:41:26
    cory_fu
  • 21:41:45
    cory_fu

    +1 on filesystem, also

  • 21:43:21
    brondsem

    i'm having second thoughts about 2 weeks

  • 21:43:31
    cory_fu

    1 week?

  • 21:43:41
    brondsem

    i wonder if some folks will question why

  • 21:44:40
    brondsem

    1 week seems reasonable to me

  • 21:44:47
    brondsem

    we could also say "at least". i think that's allowed

  • 21:44:48
    cory_fu

    Ok, I'll make it 1 week

  • 21:45:38
    cory_fu

    Vote will be open for at least 1 week (4/Sep/2013 12PM IST) to allow for it being our first release. ?

  • 21:46:43
    brondsem

    +1

  • 21:47:33
    cory_fu

    Should I include the checksums in the email?

  • 21:48:43
    brondsem

    i don't know

  • 21:48:57
    brondsem

    probably don't need to since the directory you link to has them. same for signatures too

  • 21:49:26
    cory_fu

    Yes, though if that directory were compromised, those checksum files would be as well

  • 21:49:47
    brondsem

    not sure we can do anything about that :)

  • 21:50:17
    brondsem

    i guess duplicating them is a bit of an insurance policy

  • 21:50:49
    cory_fu

    Yeah

  • 21:54:35
    cory_fu

    Anything else?

  • 21:57:09
    brondsem

    nope

  • 21:57:11
    brondsem

    thanks!

  • 21:57:13
    brondsem

    its exciting