20:39:24 #startmeeting 20:39:25 Meeting started Tue Feb 28 20:39:24 2012 UTC. The chair is mtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:39:26 Useful Commands: #action #agreed #help #info #idea #link #topic. 20:39:52 quick vote of confidence for providing stackforge.org as a place to shove satellite projects? 20:40:55 mtaylor: just to clarify - there will be a catalog/directory (with comments/rating/...) eventually — and a set of tools (like gerrit/jenkins/...) 20:41:12 mtaylor: I like the concept a lot, also wondered if we should offer a similar sandbox/trial for doc tools. We sort of do. 20:41:13 mtaylor: satellite projects will be able to use one *OR* the other 20:41:20 anotherjesse: right now I'm just focused on the set of tools - but I do think that a catalog/ratings would be a great next step 20:41:39 anotherjesse: and yes - one or the other 20:41:52 mtaylor: the reason I'm asking is that I don't want people to think they *HAVE* to use the tools in order to be "satellite" 20:41:52 I don't want to make gerrit/jenkins/project conformance a prereq 20:41:56 right 20:41:56 ++ 20:41:57 k 20:42:02 having it available is ++ 20:42:18 and having a catalog of things to put on your openstack iaas cluster is ++ 20:42:18 mtaylor: ++ 20:42:23 annegentle: we should chat about that and about what it would look like 20:42:29 mtaylor: sounds like running CI on that could end up being more complex than CI for core/incubated projects; more of them. Are you not concerned that would be a distraction? 20:42:47 +0, hoping it doesn't divert too much attention from core CI 20:42:52 zns: I'm going to be more restrictive with what is allowed as far as that goes 20:43:22 zns: essentially - if you want to be there, you HAVE to conform 100% to the interface, and you will get no customized jobs special for your project 20:43:31 mtaylor: what will that mean for satellite projects? What kind of restrictions? 20:43:38 so is there an implied limitation to how big the ecosystem can be? mtaylor and team can only handle so much 20:43:43 you'll get the set of standard tests that everything else gets 20:43:51 No gates then across projects? Just gates with core? 20:44:15 zns: no special gates intra-project, correct - only gate with themselves and with them and latest core 20:45:07 notmyname: my goal is that we use this as a way to force ourselves to make core CI more repeatable, and that we can loop more contributors in to working on stuff (wikipedia did a great job with that) 20:45:19 notmyname: but I'm also hiring more folks ... :) 20:45:55 mtaylor: yes, but wikipedia want to encourage contributions to the core. we do too, but I'd like to see more ecosystem contributions than core contributions 20:47:01 notmyname: indeed- but I meant they did a good job of getting the admin of their systems done enough via puppet that more random folks could help out with running the services (without giving out root access willy-nilly) 20:47:10 I'd like to see that more with us, so that jeblair and I are less special 20:47:28 mtaylor: you will always be special. 20:47:36 * mtaylor blushes 20:47:54 I think providing tools for an ecosystem to use is great 20:48:19 I hope it doesn't imply some sort of requirements to be part of the ecosystem, but we can address that when/if it happens 20:48:25 I'm all for it, but with the provision that core projects have priority when hell freezes 20:48:32 ++ 20:48:35 ++ 20:48:49 ttx: actually, wouldn't that be up to HP since they are providing the people and computers? 20:49:03 notmyname: it's up to the CI team, which is cross-company 20:49:10 well, they'd have to figure out how to force me to pick one set of priorities over another :) 20:49:24 the fact that HP actively invests in it doesn't mean it's "Hp property" 20:49:40 agree 20:50:51 so at least at the CI team level, it should be clear that core is their priority 20:51:03 even if the mileage may vary when it comes to direct orders to people 20:51:50 i.e. HP could provide CI resources that would only work on Satellite. 20:52:22 HP _is_ going to provide CI resources that would only work on Satallite, actually 20:52:51 although I'm going to try to arrange things so that we can make use of them for core as well :) 20:53:42 mtaylor: you need a formal vote or you're happy with that ? 20:54:02 I'm happy with that - although I may need to come back next week and ask for a formal vote 20:54:18 so if people don't _mind_ voting, that would be neat 20:55:26 next week, or now ? 20:55:41 either one. 20:55:48 * ttx is confused :) 20:55:55 +1 if it's clear that it's CI team prio 2 20:55:56 I think we may be at the end of the hour though ... let's let this be good for this week 20:56:21 thanks everybody! 20:56:34 #endmeeting