Tuesday, 2020-07-14

*** tetsuro has joined #openstack-tc00:10
*** cloudnull has quit IRC02:13
*** cloudnull has joined #openstack-tc02:13
*** cloudnull6 has joined #openstack-tc02:34
*** cloudnull has quit IRC02:35
*** cloudnull6 is now known as cloudnull02:35
*** ricolin_ has joined #openstack-tc03:00
openstackgerritzhangboye proposed openstack/governance master: migrate testing to ubuntu focal  https://review.opendev.org/74085103:03
*** tetsuro has quit IRC03:04
*** iurygregory has quit IRC03:54
*** TheJulia has quit IRC03:54
*** TheJulia has joined #openstack-tc03:55
*** tetsuro has joined #openstack-tc04:22
*** tetsuro_ has joined #openstack-tc04:26
*** tetsuro has quit IRC04:27
*** evrardjp has quit IRC04:33
*** evrardjp has joined #openstack-tc04:33
*** tetsuro_ has quit IRC04:41
*** tetsuro has joined #openstack-tc04:46
*** tetsuro has quit IRC04:58
*** dklyle has quit IRC06:39
*** iurygregory_ has joined #openstack-tc07:10
*** iurygregory_ is now known as iurygregory07:31
*** ralonsoh has joined #openstack-tc07:31
*** tosky has joined #openstack-tc07:37
*** e0ne has joined #openstack-tc08:01
ttxtc-members, mnaser: reminder that we have a community newsletter going out this week, so if you have any OpenStack news to suggest, please add to https://etherpad.opendev.org/p/newsletter-openstack-news08:44
openstackgerritLuigi Toscano proposed openstack/project-team-guide master: Import the Zuul v3 porting guide  https://review.opendev.org/74072708:46
*** camelCaser has quit IRC09:15
*** camelCaser has joined #openstack-tc09:17
*** frickler is now known as frickler_pto09:44
*** frickler_pto is now known as frickler09:47
*** tkajinam has quit IRC10:12
*** ShadowJonathan has quit IRC10:22
*** gouthamr has quit IRC10:22
*** ShadowJonathan has joined #openstack-tc10:22
*** gouthamr has joined #openstack-tc10:23
*** Jeffrey4l has quit IRC10:23
*** Jeffrey4l has joined #openstack-tc10:24
openstackgerritLuigi Toscano proposed openstack/project-team-guide master: Import the Zuul v3 porting guide  https://review.opendev.org/74072711:26
*** iurygregory has quit IRC11:46
*** iurygregory has joined #openstack-tc12:00
*** ijolliffe has joined #openstack-tc12:25
*** Luzi has joined #openstack-tc12:55
*** Luzi has quit IRC13:29
*** Luzi has joined #openstack-tc13:45
*** ralonsoh has quit IRC13:49
*** frickler is now known as frickler_pto13:50
*** ralonsoh has joined #openstack-tc14:00
knikollao/14:04
jungleboyjo/14:04
njohnstono/14:08
*** Luzi has quit IRC14:18
gmanno/14:21
gmannttx: addedabout tc-uc merge and new uc charter14:24
gmann*added  tc-uc merge and new uc charter14:24
gmannnot sure if we mentioned that in last newsletter if so, then we can skip. other than that nothing else i can remember to add than existing items14:25
*** dklyle has joined #openstack-tc14:34
*** johnthetubaguy has quit IRC14:50
ShadowJonathangmann: i'm currently all set-up to start working on the drafts, do you think it's alright if i submit them under branches 'draft/{nebula,dew,aurora}', and under rst files 'doc/source/ideas/{nebula,dew,aurora}.rst'?14:51
*** johnthetubaguy has joined #openstack-tc14:52
gmannShadowJonathan: i was thinking all three as separate rst file as they are three different ideas?14:52
gmannor you mean separate rst only?14:52
ShadowJonathanyeah, that's my plan, but that i submit all 3 induvidually under a 'draft/` branch, and as a single file each (for now) in 'doc/source/ideas/'14:53
ShadowJonathanindividually*14:53
smcginnisShadowJonathan: Under Gerrit, that would be three different topics.14:53
smcginnisBetter to have them separately in a local branch so none of them are dependent on the other patch landing.14:54
ShadowJonathanthat'd be perfect, as i would want to discuss them as separate ideas14:54
ShadowJonathanno, i'm going to submit them as induvidual branches, no worries about that14:54
gmannShadowJonathan: yeah, under this is fine 'doc/source/ideas/' we will merge it once it is complete i mean no draft dir etc required14:55
ShadowJonathanif git-review just submits the latest commits under the currently-selected branch since a `master` commit, then it'll be alright14:55
ShadowJonathanyeah, that's what i realised as well, no draft dir needed if the branch will already be tagged as that14:56
smcginnisYep, so as long as you don't stack you commits on top of each other, they are submitted as separate independent reviews.14:56
ShadowJonathanyup14:56
smcginnisSo it can all be in one branch, even master, as long as you "git reset --hard HEAD~1" between each one. The local branching is just a convenient way for them to be submitted under different topics.14:56
ShadowJonathanthat's basically stepping back one commit, right?14:57
ShadowJonathanwhy not `git reset --hard master`? much more reliable and doesnt depend on relative commits14:58
mnasertwo ways of saying the same thing :)14:59
mnaserexcept smcginnis way doesn't depend on having a specific remote15:00
ShadowJonathanyeah, but i'm not gonna delete local commits, i'll be placing them in seperate branches, so i'll still keep track of them15:00
mnaseryou would need to add origin/master or gerrit/master depending on what you remote is15:00
ShadowJonathaniirc `git reset --hard` just removes them15:00
ShadowJonathanseperate local* branches15:00
ShadowJonathan"Resets the index and working tree. Any changes to tracked files in the working tree since <commit> are discarded."15:02
ShadowJonathanit removes local files, which is something i especially wouldn't want, as commits are actually inscribed (and hopefully the only thing that git-review looks at), and local workspace can be as cluttered as you want, but it'd only be cumbersome if it merges upon checkout15:02
mnaserright, you'd run that after committing and running git review15:03
mnaserthe commit still exists locally15:03
fungigit-review will want to perform a test rebase to make sure the change isn't in merge conflict with the target branch, so it'll tell you to stash uncommitted changes first15:03
ShadowJonathani'd need local files like `venv/` and `.idea/` and soforth because they're not specified in the .gitignore file, so those will be 'seen' by git15:04
ShadowJonathanhmmmm15:04
ShadowJonathanfungi: thanks for telling me that, i'll stash some stuff then15:04
fungii believe it will be fine if there are untracked files though15:04
fungijust a problem if you have a diff to any tracked files which hasn't been committed15:04
*** cloudnull6 has joined #openstack-tc15:44
*** cloudnull has quit IRC15:46
*** cloudnull6 is now known as cloudnull15:46
ShadowJonathanoof, this is going to be a relatively opinionated piece16:05
fungiopinions are good16:05
ShadowJonathanI'm currently writing the Dew draft, I didn't realise how much of it was biased views instead of some more logical proposals to observations16:06
ShadowJonathanAurora is probably going to be somewhat the same, they both have a need to "tell a story" first before making a case16:09
mnaserShadowJonathan: sending a review doesn't necessarily mean it's baked and read, it could very much be an rfc16:20
ShadowJonathani know, i'm just commenting on the fact how differently this draft is turning out for me right now16:21
*** e0ne has quit IRC16:38
openstackgerritJonathan de Jong proposed openstack/ideas master: First (rough) draft for Dew project [RFC]  https://review.opendev.org/74100516:51
ShadowJonathanthere we go16:51
ShadowJonathanwait, master?16:51
*** njohnston is now known as njohnston|lunch16:58
ShadowJonathaneh, i think this is already a foot in the door, i'll be finishing the other two before making sending an RFC to the mailing list16:59
openstackgerritJonathan de Jong proposed openstack/ideas master: First (rough) draft for Dew project [RFC]  https://review.opendev.org/74100817:05
*** ijolliffe has quit IRC17:06
knikollathat created two reviews, please abandon one of them.17:07
ShadowJonathanjust did that with the first17:07
ShadowJonathani didn't know how to add an additional commit, and i thought the wiki said to squash both commits into a completely new one, but apparently i don't understand how to do such a thing properly, sorry about that17:08
fungiif you want to revise an existing review, commit --amend to the original. gerrit keeps the history of the prior revisions for you17:09
funginot sure what wiki you're talking about, but the general workflow is documented in the opendev manual: https://docs.opendev.org/opendev/infra-manual/latest/gettingstarted.html#updating-a-change17:10
ShadowJonathanyeah i looked over there, but i wasn't reading it correctly17:10
fungiunder the hood, gerrit looks at the change-id footer in each commit message to determine whether it's a revision of a change it already has or a new change17:11
ShadowJonathanah17:11
fungiif there's already a change for that target project and branch with the same change-id then it creates a new revision of that change. if there is no prior occurrence of that change-id for the target project and branch, gerrit creates an entirely new change17:11
fungia git commit-hook runs when you originally commit to generate a random change-id if none is not already present, and appends it when you save the commit message17:12
ShadowJonathanalright, thanks about that17:15
ShadowJonathansorry* about that17:16
fungino worries. how gerrit works can take a bit of getting used to, unless you happen to be a linux kernel developer (gerrit is basically an attempt at automating the lkml patch review workflow)17:17
ShadowJonathanYeah, I'm more used to the GitHub flow of contribution (fork-commit-PR-(discuss-commit)-squash-merge), so this might take a moment or two to get used to17:39
*** ralonsoh has quit IRC17:57
*** ricolin_ has quit IRC18:41
*** njohnston|lunch is now known as njohnston18:41
*** slaweq has joined #openstack-tc18:54
*** slaweq has quit IRC18:56
openstackgerritJonathan de Jong proposed openstack/ideas master: First (rough) draft for Dew project [RFC]  https://review.opendev.org/74100819:37
ShadowJonathanheck yeah, got the amend option working correctly19:38
ShadowJonathanfungi: thanks for telling me about it being identified by `Change-Id`, as `git commit --amend` did not seem to pick up my additional changes, so i just reset and recommitted with the right files, but with the same change-id header19:39
fungiyeah, it would either be `git commit -a --amend` or `git commit --amend some/file another/file that/third/file`19:42
ShadowJonathanyeah, i didn't do either of those (as i didn't know that), and doing `-a` would've just added my whole venv directory, heh19:43
fungi-a says commit all changes for tracked files but if you only want certain file changes added you would list them independently19:43
fungior you can git add them first19:43
ShadowJonathanwait, only tracked ones?19:43
fungiyeah, git never commits untracked files19:44
ShadowJonathani meant adding them, as `-a` to me seems like "git add -a", which just adds every file19:45
smcginnisShadowJonathan: if you use tox, that will create any venv's under the .tox directory that is included in .gitignore.19:48
ShadowJonathanthose are venvs that're used by the tox tool, and generally should/could be wiped upon every test for a completely untouched environment19:49
fungiShadowJonathan: similar use of -a, `git add -a` says track all untracked files and stage any changes for commit while `git commit -a` says to commit any changes for tracked files whether or not they were staged for commit19:49
fungiyou can also git add a tracked file and any of its changes will be staged for commit19:50
ShadowJonathanah19:50
ShadowJonathanthat makes more sense, yeah19:50
ShadowJonathanthanks19:50
*** e0ne has joined #openstack-tc20:57
*** markvoelker has joined #openstack-tc21:23
*** markvoelker has quit IRC21:27
openstackgerritJonathan de Jong proposed openstack/ideas master: [RFC] Rough draft for Nebula/Constellation project  https://review.opendev.org/74105721:30
ShadowJonathani think that's probably enough for me today, i'll most likely submit Aurora tomorrow, take one last look, and then send an email to the openstack-discuss mailing list21:33
*** e0ne has quit IRC21:37
*** e0ne has joined #openstack-tc21:38
ShadowJonathanhttps://review.opendev.org/Documentation/intro-user.html#drafts21:39
ShadowJonathanwelp, didn't know about this, better use that to stage stuff next time21:39
fungiShadowJonathan: don't try. we have acls in place to disable draft changes, they were never actually useful for our workflow, and the implementation of them in gerrit was severely flawed anyway. later versions of gerrit (we're in the midst of prepping for a long overdue upgrade) got rid of the draft option entirely for similar reasons21:45
fungiif you want to signal that a change is not yet ready for reviewing, you can just set a workflow -1 vote on it21:45
fungithat will mark it as a work in progress21:45
ShadowJonathanAh, I simply marked all of my changes thus far as "RFC", will that get the right intention across as a changeset that's more about discussing the content than actually working towards applying it?21:46
ShadowJonathanI have 0 intention to have my drafts fly into the repo (and site) as they are now, I know they're flawed and probably biased, so I want to discuss them21:47
ShadowJonathanfungi: *bump*21:50
gmannShadowJonathan: usually we use [WIP] in title commit msg to mark work-in-progress from cmt msg or -1 workflow is easy to block change to get it merge. but getting review feedback  on those can be done by pushing it on ML or irc even in WIP stage21:50
ShadowJonathanI'll be doing that after having pushed the third project, so I can focus on receiving feedback, and not composing them in the meantime, but yeah, thanks for telling me that21:51
*** e0ne has quit IRC22:21
*** jamesmcarthur has joined #openstack-tc22:32
*** tosky has quit IRC22:50
*** tkajinam has joined #openstack-tc22:58
*** e0ne has joined #openstack-tc23:11
*** e0ne has quit IRC23:13
*** jamesmcarthur has quit IRC23:36
*** jamesmcarthur has joined #openstack-tc23:48

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!