Apache Allura / Chat is hosted on FreeNode IRC channel #allura
i think Rich would be binding since he's one of our mentors
I thought he wasn't any longer?
He said something to that effect at one point, and he didn't say (binding) in his +1 email
iiuc saying "(binding)" in email is just for convenience, it doesn't actually make your vote bind to something :)
Yeah, but I thought I remembered him saying that he wasn't technically mentoring anymore.
i don't see him on IRC or skype ,to ask
seems like he's still mentoring. he's involved in more threads than any other mentor
True. I'll put him in binding
it doesn't seem like our importer handles that
Not at all
They do all have to the of the same type, at least
i'll ticket it up
Supposedly, I'm subscribed to firstname.lastname@example.org but I never get emails from there.
Are you subscribed?
I just re-subscribed w/ my personal email. Maybe that will work
yes, i'm subscribed and get them (personal & work emails)
wouldnt' matter for some entry points
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
i still think it wouldn't be a bad idea to start using stevedore for our entry point mgmt
at some point
yeah i was just looking at it to see how it handled it
oh, i was looking at the NamedExtensionManager
you have to provide the list of names for that one
seems like stevedore formalizes different patterns of dealing with extensions, but doesn't have a lot of glue or helpers around it
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?
and i'm thinking about just writing a helper function to do the same
So you want enabled by default instead of disabled by default?
and replace iter_entry_points with the helper
and/or g.entry_points - not sure why we have that too
yes, enabled by default
is what i'm thinking
question about the GH repo importer that 42cc did
they didn't do the controller that would expose the individual importer
should i add that, send it back, or was that being saved for later?
send it back, they probably just didn't know
sooner rather than later :)
Cory's out tomorrow and github work progresses without it
i'm gonna try to rebase it to tv/6526
since that will presumable be merged soon
wow, not bad at all
high five and a beer for somebody!
just a couple imports to clean up, \o/
i'll take a beer, cory can have the high five
No thanks. I'm a recovering high-five addict
any thoughts on this syntax for controlling entry points?
disable_entry_points.allura.importers = trac-tickets
disable_entry_points.allura.project_importers = trac, github
Could you just have a section?
[disabled_entry_points] or whatever
We don't use namespacing very well in our configs
i dunno. everything in [app:main] ends up on tg.config
not sure how to use another section
interesting, i was expecting just 'trac-tickets.disabled = True'
i want to have the group in there too
+1 on tvansteenburgh's idea, if we can't do a namespace
so you can do it for anything
like admin extension points
disable_entry_points.allura.admin = importers
that turns off importing altogether
I think you have that backwards, but yeah
backwards? it would disable this:
importers = forgeimporters.base:ImportAdminExtension
Oh, I see
That would disable the admin UI for the importers, but not the importers themselves
not quite as useful of an example then :)
i think 'allura.admin.importers.disabled = True` would be easier to remember, but i guess that's not doable?
yeah, not sure because theoretically you could have a [allura.admin.importers] group which would conflict then
allura.admin:importers = disabled ???
hm, that's not bad
otoh i don't want to waste time nitpicking syntax
i'm okay with the way it is
but i will always remind you that it's ugly
so who knows the best way to query mongo to see if there's anything in project's repos?
or would checking via filesystem be better?
what's the mission?
given 150 projects, see if they've got a repo with anything in it or not
well if it were me i think i'd check the fs
+1 on filesystem, also
i'm having second thoughts about 2 weeks
i wonder if some folks will question why
1 week seems reasonable to me
we could also say "at least". i think that's allowed
Ok, I'll make it 1 week
Vote will be open for at least 1 week (4/Sep/2013 12PM IST) to allow for it being our first release. ?
Should I include the checksums in the email?
i don't know
probably don't need to since the directory you link to has them. same for signatures too
Yes, though if that directory were compromised, those checksum files would be as well
not sure we can do anything about that :)
i guess duplicating them is a bit of an insurance policy