*** diablo_rojo has joined #openstack-tc | 00:13 | |
*** edmondsw has joined #openstack-tc | 00:42 | |
*** edmondsw has quit IRC | 00:48 | |
*** dklyle has quit IRC | 01:38 | |
*** diablo_rojo has quit IRC | 01:51 | |
*** gcb has joined #openstack-tc | 02:33 | |
*** rosmaita has quit IRC | 03:40 | |
*** dtroyer has quit IRC | 03:40 | |
*** dtroyer has joined #openstack-tc | 03:52 | |
*** ricolin has joined #openstack-tc | 03:57 | |
*** gcb has quit IRC | 04:22 | |
*** mriedem has quit IRC | 04:49 | |
*** eumel8 has quit IRC | 04:51 | |
*** eumel8 has joined #openstack-tc | 04:51 | |
*** gcb has joined #openstack-tc | 05:36 | |
*** e0ne has joined #openstack-tc | 05:59 | |
*** zaneb has quit IRC | 06:34 | |
*** zaneb has joined #openstack-tc | 06:34 | |
*** dklyle has joined #openstack-tc | 06:39 | |
*** e0ne has quit IRC | 06:51 | |
*** dklyle has quit IRC | 07:06 | |
*** cdent has joined #openstack-tc | 07:55 | |
*** jpich has joined #openstack-tc | 08:10 | |
*** tosky has joined #openstack-tc | 08:12 | |
openstackgerrit | Thierry Carrez proposed openstack/governance master: Add Tripleo Ansible repo https://review.openstack.org/583416 | 08:42 |
---|---|---|
cdent | tc-members: office hours | 09:00 |
ttx | hi! | 09:00 |
cdent | mornin'! | 09:01 |
ttx | Thanks for starting the PTG etherpad. Added one thing to it | 09:01 |
ttx | https://etherpad.openstack.org/p/tc-stein-ptg for those following at home | 09:01 |
* ttx is still catching up from PTO week | 09:04 | |
ttx | That cycle sure went fast | 09:04 |
cdent | yeah, I'm still trying to get tasks done from Sydney | 09:06 |
ttx | That's the feel I (badly) tried to address by making the cycle longer | 09:06 |
ttx | We review progress faster than we do things :) | 09:07 |
cdent | I don't think changing cycle length has any impact on the fact that some people are consistently trying to do too many things | 09:07 |
ttx | right. Which is why it was "badly" | 09:07 |
cdent | I have something like 5 upstream roles that could easily be enough to fill my time | 09:07 |
ttx | Although having separate PTGs led to review progress every 3 months instead of every 6 months | 09:08 |
ttx | which was probably a great idea in 2015, not so much in 2018 | 09:08 |
*** ricolin has quit IRC | 09:09 | |
* cdent likes the 3 month checkins | 09:09 | |
ttx | some of it is less resources, som eof it is just components maturing and things taking longer to change | 09:09 |
ttx | Checking in every 3 months on progress is good, but 3-month in-person checkin was a bit of a luxury | 09:10 |
cdent | Does "openstack as base layer for k8s" fit into the constellation concept? | 09:11 |
ttx | which less and less contributors can afford | 09:11 |
ttx | hmm, I guess so | 09:11 |
ttx | "What are the set of components you need to deploy to achieve that" | 09:12 |
ttx | a minimal openstack install letting you take advantage of the openstack K8s cloud provider | 09:12 |
cdent | yeah, that's what I was thinking. It has marketing cachet. More work for dims!! :) | 09:13 |
*** e0ne has joined #openstack-tc | 09:13 | |
* ttx needs to book Denver travel today | 09:13 | |
* cdent wonders if we need to rejigger the office hours hours | 09:46 | |
*** jaosorior has quit IRC | 09:53 | |
*** jaosorior has joined #openstack-tc | 09:53 | |
ttx | The "European" hour is usually quite light, and if you add the Europeans propension to take PTO in July/August | 10:08 |
* cdent needs to learn to take more PTO | 10:08 | |
ttx | it's harder to reach critical mass | 10:09 |
ttx | cdent: how much PTO do you have ? | 10:09 |
ttx | ttx has ~7weeks but has a hard time taking more than 4 | 10:10 |
cdent | there's some confusion on that because my official employment is UK based thus I have some standard approx 26 days of PTO plus holidays etc. But my group and mgt team is more US-based where it is much more ad hoc | 10:10 |
cdent | ttx your message just now about the PTG being with the next summit is the closest to official word I've seen on that. I think that change has been way underdiscussed and socialized. | 10:11 |
cdent | (Not saying I disagree with it, just that the motions of the foundation in this case we're not very scrutable) | 10:12 |
ttx | cdent: it was posted in that email I linked to, but i agree that it was not that widely or aggressively communicated | 10:12 |
ttx | mostly because we were still working out the details of how to make it work | 10:13 |
cdent | If you were an average daily contributor a message with subject of " Vancouver Summit Joint Leadership MeetingUpdate" on the foundation list would be fairly invisible | 10:13 |
ttx | I think we'll make a post-lunch presentation about it at the PTG itself | 10:14 |
ttx | that sounds like the best way to fully reach the targeted audience | 10:14 |
cdent | I would think we need that, posts to os-dev, superuser article, at the bare minimum | 10:15 |
ttx | agreed. Timing-wise, do you think doing that in September will work ? Doing it earlier might confuse people preparing for the September PTG | 10:17 |
ttx | also August is not the best month for wide comms | 10:17 |
cdent | I'm not sure. As we've said many times: overcommunicating and being overly verbose is way better than under communicating | 10:21 |
cdent | I think there are plenty of people who like to have good visibility over the next year as soon as possible | 10:22 |
ttx | Yeah, that's fair. I'll work on an article/blogpost that summarizes the rationale, survey results etc. | 10:24 |
cdent | that sounds good | 10:25 |
ttx | (and clearly say that it's not a perfect solution at all) | 10:25 |
*** diablo_rojo has joined #openstack-tc | 12:05 | |
*** rosmaita has joined #openstack-tc | 12:06 | |
*** edmondsw has joined #openstack-tc | 12:24 | |
scas | re: tc report - 2015 had a conversation about letting chef 'gracefully die'. in 2018, the survey analytics suggest that some giants would have to undergo a cosmic shift as a consequence of losing an upstream path | 13:00 |
scas | arguably, if i weren't mostly focused on the one thing, that would not preclude me from branching out more as an individual | 13:02 |
scas | on the other hand, refocusing is a signal to undergo that cosmic shift | 13:02 |
scas | some are getting to that point on the enterprise time scale, finding natural break points to strategically refactor some tech debt | 13:03 |
*** mriedem has joined #openstack-tc | 13:05 | |
scas | as an operator for one of the aformentioned giants, that's a footgun and facemine waiting to happen. it's nothing short of mass retraining | 13:06 |
dims | cdent : on top of the starter constellation i want to throw ironic (and other things needed) to be able to deploy bare metal with https://github.com/kubernetes-sigs/cluster-api too | 13:07 |
scas | losing out on valuable summit time hasn't helped my case any | 13:07 |
cdent | dims: I was thinking in terms of a sort of "all your own stuff kubernetes and openstack starter kit" for what amounts to "hobbyists" as that could be a good source of contributors if we make it clear that the barriers to entry aren't too high | 13:08 |
dims | yes starter constellation can definitely be used for minimal k8s deployments (without Load balancers which need neutron-lbaasv2 or octavia) | 13:08 |
dims | cdent : right | 13:09 |
scas | one of my goals is to have chef deploy on top of kubernetes by default, be it through kitchen or zuul/ansible playbooks. my 'starter kit' is a fairly easy barrier to entry, although i won't be able to really showcase that until a) the gerrit downtime and 2) i fix my docs that somehow bitrotted | 13:09 |
dims | cdent : i am yet to poke at what we have for all-in-one docker based deployments | 13:10 |
scas | chef has a mostly working kitchen-dokken scenario, which is built on docker using the docker-api rubygem for glue. the standard scenario is all-in-one | 13:10 |
dims | ++ scas | 13:10 |
scas | mostly working because i'm but one person | 13:10 |
dims | understood :) | 13:11 |
scas | it mostly works even in integration, which smells promising if i can get the job to complete | 13:11 |
scas | i've focused on aio as a result of my own personal pains, and it was something i could manage myself without having to actively recruit just to implement my grand delusions | 13:12 |
dims | cdent : i like it! | 13:12 |
scas | my notion is that my downstreams have teams to implement the more complex architectures, so if i provide the basic primitives to get them there, they tend to go the rest of the way on their own | 13:14 |
scas | in my operator life, this is true. i tend to rely on the work i do in the open to better dogfood things, without falling into that cosmic shift button | 13:17 |
dhellmann | scas : given the number of times I hear about custom deployment tools, focusing on building primitives seems like a very good approach | 13:21 |
mugsie | yeah, you either allow for complete customisation, or build primitives that people glue together | 13:22 |
scas | dhellmann: it works well enough for the clouds i operate to scale to 400k cores and above (presented at sydney), which i suppose is some form of validation | 13:23 |
mugsie | e.g. If I hear "we want to do X but $TOOL will overwrite it, and we can't stop it" again, I think I may cry | 13:24 |
scas | my cookbooks are peppered with guards and conditionals to allow that flexibility. the complexity, of course, increases exponentially, but it works | 13:25 |
scas | works > lamenting about how some tool can't change -- at least to me | 13:25 |
mugsie | scas: a lot of it assumes a uniform deployment layout - a lot of people will have some nodes set to 1:1, 3:1 and some for pinning. Some have SR-IOV on designated nodes, and others have wierd OS setups to support weirder vendor software | 13:26 |
scas | mugsie: of course. like fingerprints, each cloud is differently tailored for its needs | 13:26 |
scas | how to avoid 100% individual criticality is part of the goal, with everything laid out like that | 13:27 |
scas | the longer i solo it, the more it becomes a self-fulfilling prophecy | 13:27 |
dhellmann | tonyb, persia, diablo_rojo : can you give us an idea of how the elections would be affected by approving this extra-atcs patch late? https://review.openstack.org/#/c/586751/1 | 13:28 |
persia | dhellmann: Are the results intended to change voter eligibility, or just other extra-ATC permissions? | 13:28 |
*** zaneb has quit IRC | 13:30 | |
scas | things like superuser may make for some clicks, if i'm able to be patient enough to get docs working and published. i'm largely awaiting the upcoming gerrit downtime before i can really tear into it | 13:30 |
*** zaneb has joined #openstack-tc | 13:30 | |
diablo_rojo | dhellmann, I whouldn't think there would be an issue as we havent run the rolls to generate the electorate yet. | 13:30 |
dhellmann | persia, diablo_rojo : yeah, the effect on the voter roles was what I was looking for. There are some additions to the list, so I think those would be new folks for the i18n PTL election roll | 13:31 |
persia | Also, I18n appears to be an uncontested PTL election, although there is time to go before nominations close. In the event it remains uncontested, those people wouldn't need to vote anyway. | 13:31 |
openstackgerrit | Doug Hellmann proposed openstack/governance master: typo fix in voting description for chair-proposed typo fixes https://review.openstack.org/587432 | 13:33 |
scas | given the discussions on the ml and here about entry points, i'm inclined to write something up going through the basic workflow to 'get to openstack' | 13:33 |
dhellmann | mnaser : that one's for you ^^ | 13:33 |
scas | docs are docs, but they're dry | 13:34 |
dhellmann | persia : I cannot imagine having a second candidate step up for that team, so I think we're safe. I just want to make sure we don't approve something after the deadline we set if it's going to cause a problem :-) | 13:34 |
diablo_rojo | If you can wait till nominations close to merge it we can be safe, but I also don't think there would be an issue dhellmann | 13:35 |
diablo_rojo | lol | 13:35 |
persia | dhellmann: The potential problem is that at this point officials may have generated rolls (which takes a few hours), and if there was an I18N election, would need to regenerate. | 13:35 |
diablo_rojo | If we want these people included should there be an i18n election, merge now. If we don't want them included, wait till nominations close. | 13:36 |
scas | btw, i'm doing my musing here 'out loud' because it would otherwise be me talking to myself in my head, where everything is a great idea | 13:36 |
persia | Yes, and try to avoid merging late if an election is expected. Those election officials not participating in this discussion have generated rolls already. In this case, we expect it not to matter. | 13:37 |
diablo_rojo | Well, nominations close and rolls are genreate | 13:37 |
diablo_rojo | *generated | 13:37 |
dhellmann | I think, since the election for that team is a formality, it's safe to leave the patch open until the normal deadline for approving it | 13:41 |
scas | the good news, to stop being so negative, is that i can get with the program on the releases repo going forward. i completed the general availability of the queens release of the cookbooks recently, which gives me a natural quiet time while i stabilize rocky once the packages are available | 13:44 |
diablo_rojo | dhellmann, works for me :) | 13:45 |
scas | for one person, four or so months to stabilize a release part-time isn't the worst. at least it wasn't like newton | 13:47 |
persia | dhellmann: In practice, we don't actually run elections where they are uncontested: I'm forgetting the nomenclature at the moment but there is another word for how uncontested PTLs end up with their positions. | 13:47 |
dhellmann | persia : true | 13:48 |
scas | the sarcastic part of me wants to joke about the word being 'gullible' | 13:50 |
smcginnis | :) | 13:50 |
jroll | stockholm syndrome? :P | 13:51 |
ttx | acclaimed | 13:51 |
scas | jroll: :) | 13:51 |
persia | ttx: Thank you :) | 13:51 |
scas | it's meant in jest, really | 13:51 |
ttx | we would say "plebiscited" in French but apparently that did not transfer to English | 13:52 |
ttx | (although plebiscite did) | 13:52 |
scas | in america, that would be interpreted as "you have a what?!?" | 13:52 |
scas | in all seriousness, 'something' needs to happen with chef to either breathe new life into it, or signal that cosmic shift amongst the giants. as a dogfooder, i have somewhat of a vested interest in its success | 13:55 |
scas | is superuser enough, at this stage? | 13:56 |
smcginnis | It's at least one way to get some publicity for it I think. | 13:57 |
scas | vancouver was intended to have sessions talking about it. according to the emails back then, some people had added the sessions to their schedule before i had to change plans | 13:59 |
scas | without someone else to present, it's down to me figuring out how to get to summits and conferences, while juggling everything else | 14:00 |
smcginnis | scas: So you're saying it's all your fault? | 14:00 |
smcginnis | :) | 14:00 |
scas | it's my fault that mitaka didn't see the end of it :) | 14:01 |
scas | at the end of the mitaka cycle, ibm and others pulled back. my operator ways kept feeding code into the machine long after it became apparent that it was just me | 14:03 |
scas | as i've mentioned before, in the past, relocating chef openstack came up when there were more cores. the inertia of relocating it somewhere else can be even more deterimental than doubling down, so to speak. github and gitlab are not ideal places i want to hinge a deploy project like that, because they're funded ventures that can and will change course if the business agrees it should | 14:13 |
scas | if the self-reporting is to be believed, the users that do exist by default agree with the current positioning | 14:16 |
*** hongbin_ has joined #openstack-tc | 14:18 | |
ttx | tc-members I put out the call for post-lunch presentations at the Denver PTG: https://etherpad.openstack.org/p/PTG4-postlunch | 14:29 |
scas | it seems like it might be worthwhile for me to do whatever i can do make the denver ptg, if only to have conversations like this in-person for a change | 14:30 |
zaneb | no love for Zeppo? | 14:31 |
scas | provided there are no surprises in the next few months, i'm targeting being at the berlin summit. ptg never was too valuable for the chef cores internally due to the distributed nature of the team. irc worked until it didn't | 14:33 |
ttx | zaneb: hard choices had to be made | 14:34 |
scas | we had more engagement when it was in stackforge, with bleary-eyed first-thing-monday google hangouts. irc made it harder to convey intent, including being overly transparent | 14:35 |
*** AlanClark has joined #openstack-tc | 14:46 | |
mnaser | ttx: i'd be up to help out with some of them "welcome to the ptg" stuff if you need filling in for that question mark | 14:49 |
ttx | mnaser: perfect, please add your name to it :_ | 14:50 |
mnaser | ttx: cool, let me know when you want to sit and figure out what we have to do | 14:50 |
*** diablo_rojo has quit IRC | 15:03 | |
*** ricolin has joined #openstack-tc | 15:13 | |
*** e0ne has quit IRC | 15:23 | |
*** AlanClark has quit IRC | 15:27 | |
*** zaneb has quit IRC | 15:34 | |
*** zaneb has joined #openstack-tc | 15:35 | |
*** dklyle has joined #openstack-tc | 15:56 | |
openstackgerrit | Merged openstack/governance master: typo fix in voting description for chair-proposed typo fixes https://review.openstack.org/587432 | 16:13 |
*** diablo_rojo has joined #openstack-tc | 16:33 | |
*** jpich has quit IRC | 16:35 | |
*** dtruong2 has joined #openstack-tc | 16:36 | |
*** dklyle has quit IRC | 16:48 | |
*** dklyle has joined #openstack-tc | 17:07 | |
mnaser | https://governance.openstack.org/election/ | 17:11 |
mnaser | are we failing to publish? | 17:11 |
mnaser | oh wait | 17:12 |
mnaser | post queue is probably long | 17:12 |
dhellmann | mnaser : I see 2 election patches in the post queue with ages over 3 hrs | 17:39 |
mnaser | just wanted to have a general figure of what projects dont have anyone elected (if any) yet | 17:39 |
dhellmann | yeah, I was wondering that myself | 17:39 |
smcginnis | 6 hours left, so I'd like to see a little better picture too. | 17:40 |
smcginnis | Looks like a bunch waiting to be approved yet. | 17:40 |
dhellmann | smcginnis , mnaser : render-statistics gives me: http://paste.openstack.org/show/726963 | 17:45 |
dhellmann | which of course doesn't include those waiting | 17:45 |
mnaser | the ones i identify with nothing proposed are: security (but that's unique), trove, RefStack, Loci, Winstackers, Packaging_Rpm, Freezer, Searchlight and Dragonflow | 17:47 |
mugsie | Trove has a candiate | 17:47 |
mnaser | https://review.openstack.org/#/q/project:openstack/election i didnt see one there :X | 17:48 |
mnaser | https://review.openstack.org/#/c/587333/ | 17:48 |
mnaser | oh | 17:48 |
mugsie | But I am not sure if it will pass https://review.openstack.org/#/c/587333/ | 17:48 |
mugsie | I think that may need to be a post election appointment by us | 17:48 |
dhellmann | http://paste.openstack.org/show/726966 is easier to read | 17:49 |
smcginnis | Security should be dropped from the election once we approve the patch since it's now a sig. | 17:49 |
smcginnis | hogepodge: Were you planning on being RefStack PTL again? | 17:50 |
smcginnis | I wonder if that makes more sense as a sig too though. | 17:50 |
mugsie | Yeah, or just rolled into InterOp | 17:51 |
smcginnis | Hmm, only one project needing an election so far. | 17:52 |
*** e0ne has joined #openstack-tc | 17:52 | |
mugsie | Senlin is going to need one as well I think | 17:54 |
dhellmann | nothing for dragonflow? | 17:54 |
dhellmann | or freezer? | 17:54 |
mugsie | nope | 17:54 |
dhellmann | or Loci | 17:54 |
smcginnis | Not too surprised on df or freezer, but a little surprised with Loci. | 17:55 |
mugsie | or searchlight, but that might just be Steve doesn't realise that it is that time of year | 17:55 |
dhellmann | I guess we need to start thinking about what we might do with some of these | 17:55 |
scas | i keep putting my name on the hat so you all can prolong those thoughts a bit more, at least in my realm | 18:06 |
smcginnis | So scas for all projects that fail to get a PTL. ;) | 18:07 |
scas | i've not perfected cloning yet | 18:07 |
TheJulia | Do we have transporters yet? Maybe that can create clones? | 18:18 |
scas | quantum teleportation does that, but it's not ready | 18:19 |
jroll | we just need a time machine to go to the future and steal the other technologies | 18:19 |
scas | i'm a bit larger than a photon | 18:19 |
*** dklyle has quit IRC | 18:23 | |
*** dklyle has joined #openstack-tc | 18:40 | |
*** ricolin has quit IRC | 18:53 | |
TheJulia | jroll: ++ but would that also mean that we would have teleportation? | 19:02 |
*** rosmaita has quit IRC | 19:03 | |
*** e0ne has quit IRC | 19:06 | |
*** cdent has quit IRC | 19:14 | |
*** diablo_rojo has quit IRC | 19:22 | |
*** e0ne has joined #openstack-tc | 19:48 | |
*** e0ne has quit IRC | 20:51 | |
*** amrith has joined #openstack-tc | 20:57 | |
*** amrith- has quit IRC | 20:57 | |
*** amrith is now known as Guest39490 | 20:57 | |
*** edmondsw has quit IRC | 21:00 | |
*** edmondsw has joined #openstack-tc | 21:01 | |
*** edmondsw has quit IRC | 21:01 | |
*** Guest39490 has quit IRC | 21:01 | |
*** edmondsw has joined #openstack-tc | 21:01 | |
*** amrith has joined #openstack-tc | 21:33 | |
*** amrith is now known as Guest43093 | 21:33 | |
smcginnis | dhellmann: Was that your own script you ran this morning that showed election candidates? | 21:36 |
dhellmann | smcginnis : no, it was a command in the election repo (tox -e venv -- render-statistics -v) | 21:37 |
smcginnis | Oh, nice. | 21:37 |
* dhellmann is feeling all smug for looking to see if that existed before he wrote one | 21:37 | |
smcginnis | Hah | 21:38 |
smcginnis | 7 without candidates, one of which is Security. | 21:39 |
dhellmann | which 7? | 21:40 |
dhellmann | or 6 I guess | 21:40 |
smcginnis | DragonFlow, Freezer, Loci, Packaging RPM, Searchlight, Winstackers | 21:43 |
smcginnis | Wait, refstack too. | 21:43 |
smcginnis | Maybe I didn't collate that right in my head. We have a few candidate patches not accepted yet. | 21:43 |
smcginnis | Assuming all of those are qualified candidates. | 21:43 |
*** mriedem has quit IRC | 22:14 | |
tonyb | On July 25th I sent an email to openstack-tc requesting the governance repo be tagged. I failed to notice it got caught in moderation and is still there. The TL;DR is can we, the election officials, please have the governance repo SHA cefd60f94f77066bf33d396811c6320de03eaa3e tagged as aug-2018-elections | 22:21 |
* tonyb can generate at list of open projects but it'll just be based on render-statistics | 22:23 | |
*** edmondsw has quit IRC | 22:23 | |
tonyb | dhellmann: can I graft your reviews into my tools-fix series mostly to get https://review.openstack.org/#/c/587649/1 | 22:23 |
*** edmondsw has joined #openstack-tc | 22:23 | |
tonyb | Zun and Trove will need TC attention | 22:26 |
dhellmann | tonyb : go for it | 22:29 |
tonyb | dhellmann: Thanks | 22:29 |
dhellmann | tonyb : I will tag the governance repo tomorrow | 22:30 |
tonyb | dhellmann: Thanks | 22:30 |
dhellmann | actually, let me see if I can just do it now | 22:30 |
dhellmann | I assume you need a signed tag | 22:30 |
*** edmondsw has quit IRC | 22:30 | |
tonyb | dhellmann: Yes please | 22:31 |
*** edmondsw has joined #openstack-tc | 22:31 | |
dhellmann | tonyb : done | 22:31 |
tonyb | dhellmann: Thanks, that's perfect! | 22:32 |
fungi | yeah, having a tagged point in history of the governance repo makes it easier to see later what teams/deliverables/extra-atcs were considered | 22:33 |
fungi | as opposed to just "whatever the head of master was at the time we ran stuff" | 22:34 |
tonyb | I've hacked up a tool that makes it a little quicker to setup an election so once the PTL elections have concluded we can keep the momentum up and set the TC elections up | 22:34 |
fungi | awesome | 22:35 |
tonyb | part of that will be to add an item to the release scheule for 'tag the governance repo' | 22:35 |
fungi | with ptl and tc elections moving around relative to one another, that's hard to do until we know the release schedule | 22:36 |
tonyb | We can *probably* even set the 'T' dates ... at least pencil them in | 22:36 |
tonyb | fungi: Yeah a little but the next TC election is fixed to the Berlin summit, after that it gets hard to do anything other then pencil them in | 22:37 |
scas | fungi: i resemble that remark about the head of master! that is, until after the next gerrit downtime | 22:38 |
smcginnis | tonyb: We can add something to the releases process doc to note it as a task that needs to be done at a certain point in the cycle. | 22:44 |
tonyb | smcginnis: Thanks, that was my plan. to include it as a x-project item when we add the otehr election details | 22:46 |
smcginnis | tonyb: That's a little different than what I'm saying. We have the process.rst doc that we follow that notes at what points in the cycle certain tasks should be performed. I wonder if that is a better place for it than in the actual cycle schedule itself. | 22:47 |
tonyb | smcginnis: Oh yeah that could work. It feels a bit like 'crossing the streams' to me in that PROCESS.rst is tasks the realease team needs to do to get a release out the door (in general) where as this is definately a thing for the election officials to do with the help of the TC. | 22:49 |
tonyb | smcginnis: I see it mostly the same as 'extra ATC updates' but the bottom line is as long as it happens in a reasonably controlled fashion it doesn't matter where it's tracked ;P | 22:50 |
dhellmann | tonyb : we have several other items in that list to remind other teams already | 22:51 |
dhellmann | #keepersofthecalendar | 22:51 |
tonyb | dhellmann: Okay. | 22:51 |
* tonyb will come up with a chnage to process.rst | 22:54 | |
*** hongbin_ has quit IRC | 23:00 | |
*** edmondsw has quit IRC | 23:11 | |
*** tosky has quit IRC | 23:35 | |
mnaser | Maybe for | 23:58 |
mnaser | For tomorrow’s office hour we need to | 23:58 |
mnaser | Figure out about the projects needing attention | 23:58 |
mnaser | (Sorry extra enters) | 23:59 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!