| smohamud has quit (Ping timeout: 480 seconds) | 00:23 | |
| smohamud_ has quit (Ping timeout: 480 seconds) | 00:23 | |
| jgurara has quit (Ping timeout: 480 seconds) | 04:28 | |
| mulbah has quit (Quit: Leaving) | 09:43 | |
| thomasboimah has quit (Quit: Leaving) | 12:42 | |
| smohamud has quit (Ping timeout: 480 seconds) | 20:58 | |
| smohamud has quit (Quit: Leaving) | 21:35 | |
| resl | !list | 22:01 |
|---|---|---|
| Websterss | No meetings currently scheduled in this channel. | 22:01 |
| resl | !create NWD Devs Flow Follow-up Tuesday 22:00 UTC | 22:01 |
| Websterss | Meeting created! ID: 5V2D | Name: NWD Devs Flow Follow-up Tuesday 22:00 UTC | 22:01 |
| zOnny | Hello Everyone | 22:01 |
| resl | !add checkins, facilitator: Tony; note-taker: resl, anyone in IRC | 22:03 |
| Websterss | No active meeting and no meeting ID provided. | 22:03 |
| resl | !add 5V2D checkins, facilitator: Tony; note-taker: resl, anyone in IRC | 22:03 |
| Websterss | Added to agenda: [I1] 'checkins, facilitator: Tony; note-taker: resl, anyone in IRC' (by resl) | 22:03 |
| smohamud | Proposed agenda: Versioning decision, CI process approval | 22:03 |
| smohamud | Confirm the current Workflow document is good to move forward with. | 22:04 |
| resl | smohamud: That looks good! I'll add it and we can go with that unless there are other strong suggestions, etc. | 22:04 |
| resl | !add 5V2D versioning decision | 22:05 |
| Websterss | Added to agenda: [I2] 'versioning decision' (by resl) | 22:05 |
| smohamud | +1 thanks! | 22:05 |
| resl | !add 5V2D CI process approval | 22:05 |
| Websterss | Added to agenda: [I3] 'CI process approval' (by resl) | 22:05 |
| resl | !add 5V2D confirm current workflow and use NextCloud doc (or a shared doc in gitlab?) to keep record of our process | 22:06 |
| Websterss | Added to agenda: [I4] 'confirm current workflow and use NextCloud doc (or a shared doc in gitlab?) to keep record of our process' (by resl) | 22:06 |
| resl | !agenda | 22:06 |
| Websterss | No active meeting and no meeting ID provided. | 22:06 |
| resl | !start | 22:06 |
| Websterss | Invalid arguments. | 22:06 |
| resl | !start 5V2D | 22:06 |
| Websterss | Meeting '5V2D - NWD Devs Flow Follow-up Tuesday 22:00 UTC' is now active! | 22:06 |
| resl | !sethost 5V2D anthony_p | 22:07 |
| Websterss | Invalid arguments. | 22:07 |
| resl | !sethost anthony_p | 22:07 |
| Websterss | Host changed from resl to anthony_p | 22:07 |
| resl | !agenda | 22:07 |
| Websterss | **Agenda for '5V2D - NWD Devs Flow Follow-up Tuesday 22:00 UTC'** [✅ ACTIVE] | 22:07 |
| Websterss | 4. [I4] confirm current workflow and use NextCloud doc (or a shared doc in gitlab?) to keep record of our process (by: resl) | 22:07 |
| resl | Karaaaaa: Can you also help with notes in this channel, with what Tony's been saying? I'm lagging behind a bit | 22:08 |
| zOnny | https://gitlab.com/novawebdevelopment/business-tracker/-/blob/docs/contributing-branching-model/CONTRIBUTING.md | 22:09 |
| resl | or anyone who has a good memory of the flow Tony just described - thanks zOnny for the shared doc I meant to reference | 22:09 |
| Karaaaaa | resl, yes i can | 22:09 |
| resl | Notes: | 22:10 |
| smohamud | I really like this Tony - we can can use this excluding the develop branch. | 22:10 |
| smohamud | I do think develop would add complexity without adding too much benefit but could be wrong. | 22:11 |
| resl | Refer to the md file zOnny shared above for the current and ongoing workflow. I'm not clear smohamud on the exclusion of the develop branch - I'll ask anthony_p to give this summary once more for me in Jitsi | 22:11 |
| zOnny | I think I have done tags based on the release as well | 22:12 |
| resl | smohamud asks: Do we stick with including a development branch between feature branches and main/production? anthony_p answers I think that would be best in our case because we have several different projects and some of them will benefit from versioning and staging (anthony_p can you add a note in this chat too on what you said?) | 22:17 |
| Karaaaaa | anthony_p says that we can have many development sites | 22:19 |
| resl | smohamud: our May First organizational membership for NWD right now gives us >400gb of disk space I think and the various branches are all on gitlab of course - but am I misunderstanding anthony_p? | 22:19 |
| zOnny | Agreed | 22:19 |
| zOnny | something we have to understand is that develop decouples two things that are otherwise tangled together | 22:20 |
| zOnny | something like : Is this feature done and merged? | 22:21 |
| resl | Karaaaaa: Nice, so this flow isn't changing anything about our disk space use... Is it correct that the flow including the development branch then is like I said earlier a way to make sure we include an extra step before production zOnny? | 22:21 |
| zOnny | BT's master was following that process before having the feat/multi-coop | 22:22 |
| Karaaaaa | resl, i believe so? | 22:22 |
| smohamud | I don't think we should adjust our git model based on the utility to interns. It's kind, but it prioritizes the wrong thing, we need a model that maxes productivity and code quality | 22:22 |
| resl | Tony adds that the development branch included in this flow is a normal standard especially with interns and newer developers on staff | 22:22 |
| smohamud | Nevertheless, I agree. | 22:23 |
| smohamud | We should use this model, it's what I've seen at every company but partly because live staging / testing environments were used. | 22:23 |
| smohamud | So, that alone isn't a good reason. I do think this works for us, though. | 22:24 |
| zOnny | aapfeldorf: they do very similar | 22:25 |
| resl | smohamud: I think the idea about the interns is that this flow makes it easier for devs at all levels to work more productively by separating the development from main, leaving the final review to the few folks who can do it most critically and with the most experience | 22:26 |
| zOnny | Neither I | 22:26 |
| resl | Proposal: versioning milestones decided at road map creation of each project | 22:26 |
| resl | Sahnun notes that deciding for each project might add more complexity than is needed and making the milestones time-based is maybe the simplest/most reasonable structure | 22:29 |
| smohamud | resl: the productivity hit is in that we now have to do multiple merges, local to dev and then dev to production. That's not easier, it's a cost. | 22:29 |
| zOnny | that is a good call on it | 22:32 |
| resl | smohamud: It's a huge cost when things get broken like they have when there were not clear steps before pushing to production but I'm stating the obvious. Not sure why I have to do that lol | 22:32 |
| zOnny | our main focus for know should be main develop and feature/ | 22:32 |
| zOnny | **now | 22:32 |
| resl | main, develop, and feature* right, zOnny? three separate stages | 22:32 |
| zOnny | right | 22:34 |
| zOnny | that is actually I was refereing to | 22:34 |
| zOnny | **referring | 22:34 |
| resl | That's great to clarify - thanks zOnny! | 22:35 |
| zOnny | develop is a moving target. we as devs keep merging new features into it. But at some point we need to say "this is what's going out the door" | 22:36 |
| zOnny | wht should come in mind should be that the release branch is that freeze point. It's a snapshot of develop at certain point | 22:39 |
| smohamud | I'm good with that | 22:39 |
| zOnny | yup we can do that and review it | 22:40 |
| smohamud | +1 | 22:40 |
| zOnny | +1 | 22:40 |
| resl | zOnny: Yep! That makes sense. anthony_p re: versioning meetings +1 | 22:40 |
| smohamud | resl: understood | 22:41 |
| smohamud | +1 on that | 22:41 |
| zOnny | I think that will come after certain features have been completed and we can call a release meeting | 22:41 |
| anthony_p | +1 | 22:42 |
| Karaaaaa | +1 | 22:42 |
| zOnny | +1 | 22:42 |
| aapfeldorf | +1 | 22:42 |
| zOnny | are we all clear with develop? | 22:42 |
| smohamud | +1 | 22:42 |
| resl | I think so. I haven't reviewed the md doc fully yet though so I need to do that, sorry. There is a naming convention in there, right anthony_p? | 22:43 |
| zOnny | I can help with it if needed | 22:43 |
| smohamud | Tony - could you document the Versioning procedure in the Gitworkflow doc on nextcloud? | 22:44 |
| zOnny | I need to warn that multi coop will add complexity to our feature built | 22:45 |
| anthony_p | sure, i will do that sometime this week | 22:45 |
| anthony_p | i have the ams meeting tomorrow | 22:45 |
| smohamud | I don't remember discussing major/minor release versions if we're planning to have that. | 22:45 |
| smohamud | +1 thanks | 22:45 |
| resl | zOnny: there are protections for merges for our different projects on gitlab, so you can make sure that for each project, certain devs who have the responsibility and permissions to manage the project in question are the final reviewer(s) before production, right? | 22:48 |
| resl | like zOnny you are the project manager for BT, so you are able to set permissions and decide if anyone else is authorized to review changes before production, and otherwise, you are the one with those permissions, right? | 22:49 |
| zOnny | Karaaaaa: how is the library app team workflow? | 22:51 |
| zOnny | The only new development is only from aapfeldorf, yes? | 22:54 |
| Karaaaaa | zOnny, sorry for not seeing. we just make branches that may be wip or a feature branch (no naming conventions really) and then make a pull request that josh, ben, or i usually approve. once approve, the branch may be merged into main | 22:55 |
| Karaaaaa | *approved | 22:56 |
| zOnny | Karaaaaa: got it. very straightforward move with a small team | 23:01 |
| resl | !agenda | 23:02 |
| Websterss | **Agenda for '5V2D - NWD Devs Flow Follow-up Tuesday 22:00 UTC'** [✅ ACTIVE] | 23:02 |
| Websterss | 4. [I4] confirm current workflow and use NextCloud doc (or a shared doc in gitlab?) to keep record of our process (by: resl) | 23:02 |
| resl | !help remove | 23:02 |
| Websterss | !remove <item_id_or_text> | 23:02 |
| Websterss | Only the meeting host, item creator, or an operator can remove items. | 23:02 |
| resl | !remove I4 | 23:02 |
| Websterss | Removed: [I4] 'confirm current workflow and use NextCloud doc (or a shared doc in gitlab?) to keep record of our process' | 23:02 |
| resl | !finish | 23:03 |
| Websterss | Meeting '5V2D - NWD Devs Flow Follow-up Tuesday 22:00 UTC' has been finished and removed. | 23:03 |
| zOnny | smohamud: ? | 23:03 |
| zOnny | thanks everyone | 23:03 |
| Karaaaaa has quit (Read error: Connection reset by peer) | 23:04 | |
| Karaaaaa has quit (Read error: Connection reset by peer) | 23:05 | |
| thomasboimah has quit (Quit: Leaving) | 23:07 | |
| resl has quit (Quit: resl) | 23:16 | |
| anthony_p | https://amstest.novawebdevelopment.coop/accounts/ | 23:16 |
| jgurara has quit (Ping timeout: 480 seconds) | 23:35 | |
| smohamud has quit (Ping timeout: 480 seconds) | 23:43 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!