IRC log of #novawebdev for Sunday, 2026-07-05

dcammue has quit (Ping timeout: 480 seconds)10:19
jallah-koleah has quit (Read error: Connection reset by peer)10:30
jallah-koleah_ has quit (None)10:33
jallah-koleah has quit (Remote host closed the connection)10:42
thomasboimahGood morning smohamud and jgurara 10:59
thomasboimahand zOnny 10:59
zOnnyGood morning thomasboimah 11:00
smohamudgood morning comrades11:02
zOnnyHey team, yesterday I started working on the LibreOrganize update and also checked in with others to see if anyone needed a hand. I have not blockers so far.11:02
zOnnyACTION done11:02
thomasboimahYesterday, I went to represent Jetro at Janet M. Kollie's graduation. No blockers.11:02
thomasboimahACTION done11:02
smohamudyesterday I changed SJC about page to Our Team and updated member details, added two new members.11:02
smohamuddone11:02
smohamudOne blocker - Zonny, can I get access to our Stripe? I want to play with the integration.11:03
smohamudOur homepage requires at least one more way to donate and I'd like to see what I can do with the messaging and all that.11:04
zOnnysmohamud: I think resl have an admin there11:04
zOnnysmohamud: let me look if I can invite you11:04
smohamudOk - I'll ask her if that's the case11:04
zOnnysmohamud: aren't we using opencollective? 11:05
smohamudLet me see, I actually don't know11:06
smohamudhref="https://donate.stripe.com/4gMcN6aQ8fpd8Qg4Xzbsc00">11:06
smohamudThey might be working together, though...11:07
thomasboimahI think the SJC team members' photos need to look the same on the page, just like on the NWD site. Is there someone taking care of the images? That could be a great task for the designer Jetro recruited.11:08
zOnnysmohamud: yup it is stripe working for the sjcompute11:08
smohamudI like that idea, Thomas.11:08
zOnnythomasboimah: +111:08
smohamud+111:08
zOnnythomasboimah: I did bring it to resl11:09
thomasboimahOkay11:09
zOnnythomasboimah: she has good gimp skills 11:09
zOnnyshe did mention that she will be working with smohamud 11:09
zOnnysmohamud: we haven't enable back the opencollective11:10
zOnnysmohamud: we were using stripe due that opencollective has a bug with their donations 11:10
thomasboimahI also make a proper merge request Adding personal pages for team members, with URLs following this pattern: https://sjcompute.org/our-team/janet-kollie/.11:10
zOnnysmohamud: I remember they did reply mentioning they have fixed it11:11
zOnnysmohamud: we just need to se if it works and update the sjcompute donate button11:11
smohamudOk - do you have the credentials for open collective is that also Resl?11:11
zOnnythomasboimah: I saw it11:12
zOnnythomasboimah: due to this updates with page members I think it is time to update the way LibreOrganize works11:14
zOnnythomasboimah: There isn't nothing wrong with it11:14
zOnnythomasboimah: it is hust the way we are at the point relying heavily on the json data11:15
zOnnythomasboimah: you have a great approach on adding the personal pages11:16
zOnnythomasboimah: it looks good to me11:17
smohamudZonny - could you elaborate on what the problem with Libre Organize is right now? Is it the fixtures being too inflexible?11:17
zOnnysmohamud: yup 11:18
zOnnysmohamud: additionally LibreOrganize is getting rusty11:18
smohamudI am glad you're thinking about that because I personally feel we may have overengineered a solution to a problem that doesn't really exist for most the apps built on it ....11:18
smohamudLike, I went through the fixtures we use for SJC and it's a handful and it actually made the code much less readable than just having that information in the actually home page...11:19
zOnnysmohamud: I see11:20
smohamudI don't see any benefit in using fixtures on our homepage in SJC and it abstracts away the content. Adds an extra step to modifying anything...11:21
zOnnyAgain we need to get in to the habit of maintaining our core porjects11:21
smohamud+111:21
zOnnythis means looking on how far is our django version from the actual one11:21
zOnnyYesterday I started to check some compatibility with django 6 and few packages are deprecated such as django-tempus-dominus11:23
zOnnyI'm still working on it on the develop branch11:24
zOnnyIt is the same with our Blog project11:25
zOnnyI'm glad django is a robust framework that works with the oldest version still :)11:25
smohamudwhat version of django are we using with LO?11:26
zOnnydjango 4.2 LTS11:26
zOnnysmohamud: we should have updated it to django 5.2 LTS 11:27
smohamudOhh... Django is already on 6 right?11:27
zOnnysmohamud: again the changes are not big deal in the django ecosystem11:27
zOnnythat's all11:27
smohamudOk... long as we update before it starts to cost us something.11:29
zOnnyI don't want us to get to the point skipping updates and keep working with the previous versions11:29
smohamud+111:29
zOnnysmohamud: I like went my phone gets updated and better looking features appear11:29
zOnnybut not always 11:30
smohamudlool I gotcha11:30
zOnnyI now we have become to skill up ourselves to the point of awareness11:30
smohamudI've dealt with dependencies a-lot, old versions are not a problem until they are... 11:31
zOnnyI know this is a tasks that thomasboimah or tony can take it11:31
smohamudIs Django dependency management that different from JS? I could probably handle it too.11:32
smohamudI've done similar for JS frameworks11:32
zOnnysmohamud: I'm sure you can also get it to the point of getting to update it11:33
zOnnysmohamud: similiar th JS11:33
zOnnysmohamud: I just want to bring it to your attention11:33
zOnnyI mean to the dev team11:33
smohamudOk, just want to make sure you know I also feel pretty much ready to handle it.11:34
zOnnythat is all, I will let you know if I get to the point of needing help with it11:34
smohamud+111:35
zOnnysmohamud: you have tasks 11:35
thomasboimahzOnny, 11:35
zOnnythomasboimah: I feel you can help on this too, yes?11:35
smohamud+111:35
zOnnythomasboimah: yes?11:37
thomasboimahJust to clarify, the changes I made for the SJC team member pages don't use the Box feature. The member data is currently stored in a Python dictionary (TEAM_MEMBERS) in views.py, so it's separate from the Box system.11:38
zOnnythomasboimah: I see11:38
thomasboimahThe only page on the sjc website the is using the box feature is the, home page11:39
thomasboimah*that11:39
zOnnythomasboimah: so they cannot update it from the UI? they just can update the json?11:39
thomasboimah+111:40
zOnnythomasboimah: I see11:40
zOnnythomasboimah: it works for me11:40
zOnnythomasboimah: we can leave it until someone come with the question "How I update the content of this member"11:41
thomasboimahyes11:43
smohamudKeep in mind I'm on the SJC board so I can handle that anytime. That said - that's the kind of question we should ask while onboarding new customers about whether than kind of ability is something they're interested in since it adds complexity to our job with the tradeoff being they have control11:43
zOnnythanks for your inputs11:44
zOnnysmohamud: you got a point11:44
zOnnysmohamud: I know we can do it for them11:44
zOnnyI know we can be at the request point and do it11:45
smohamudYeah, eventually I'll probably handle all the changes since I am a stakeholder11:46
zOnnysounds good11:47
smohamud+111:48
zOnnythomasboimah: I have approved your request11:48
zOnnythomasboimah: did you get notifiy when the reviewer approves it?11:48
thomasboimahjust a sec let me check my mail11:48
thomasboimahyes11:49
zOnnycool11:49
zOnnysmohamud: Is there any other changes you want to make to sjcompute?11:50
zOnnysmohamud: I'm going to pull your changes to prod11:50
smohamudToday, only the Resl cover photo update11:50
smohamudJust give me a few m...11:51
zOnnysmohamud: ok11:51
zOnnysmohamud: do you want me to check if we are planning in keep using stripe rather than opencollective?11:51
smohamudYes please check that11:52
zOnnywill do11:54
zOnnysmohamud: do you have access to the bitwarden?11:54
zOnnythomasboimah: Any blockers?11:56
thomasboimah-1 for now11:56
smohamudI do not11:56
smohamudhave access to bitwarden11:57
zOnnythomasboimah: I think you will be working with gabriel for the sprints jeff mention, yes?11:57
smohamudAlso - the cover change is pushed11:57
smohamudno further changes for Prod at the moment.11:57
thomasboimahbut my goal for this week is helping my team members understanding our infrastructure so they can also start contributing11:58
thomasboimahI mean working with: gabriel, Jallah, Derick and Mulbah11:59
zOnnythomasboimah: great12:00
zOnnythomasboimah: it is good to see jetro is building a solid team12:01
thomasboimahyes!12:01
zOnnythomasboimah: understanding their roles is the key12:01
smohamudteaching is a fantastic way to deepen your own understanding, too. if you haven't already ask Jeff how he would do it.12:02
zOnnythomasboimah: although in a coop roles aren't efficient at all due that it is a collaborative workflow12:02
zOnnythomasboimah: I'm glad jeff is making sure you all have the necessary resources for the jetro12:04
thomasboimahYes12:05
thomasboimahHe is making all hands to be on the desk12:05
smohamudawesome12:06
zOnnynice 12:06
zOnnyIt is good to have a break from him being around :-)12:08
thomasboimahlol12:09
smohamudlool12:10
zOnnysmohamud: I did pull12:16
zOnnybut navbar is not aligning the same way it does in my local12:17
zOnnyIs this just in my browser?12:19
zOnnyDoes the navbar also look on the left on your end?12:20
zOnnyHas anyone started updating sjcompute in the server recently12:31
zOnnyI'm seeing manual changes to the theme and the libreorganize there 12:32
smohamudHey, let me take a look12:40
smohamudSo, it's actually not aligned how I had wanted it, probably because of the merge conflict with the custom-css-removal. 12:41
smohamudEven on my local ---- it should be more centered, underneath the actual hamburger menu12:42
smohamudOtherwise, though, the centering is right locally and all.12:42
smohamudI looked at Prod and there aren't any of the changes yet --- what do you mean you're on your local?12:43
smohamud**not aligning the same was on your local12:43
zOnnysmohamud: it isn't the code12:46
zOnnythe gunicorn isn't taking the updates due that it is disabled for some reason12:47
zOnnyI'm looking on why it is disabled12:47
smohamudOk12:48
zOnnysmohamud: it is enabled now12:51
zOnnysmohamud: but the navbar on my end it is still looking on the left12:52
smohamudYeah, weird. Let me push a small change to align how I originally intended and that will erase this issue.12:52
smohamudWe can redeploy after that12:52
smohamud*probably erase the issue...12:53
zOnnysmohamud: I'm not done12:53
zOnnysmohamud: hold on12:54
thomasboimahjust a headsup pull first before you start work because my branch was merge12:54
thomasboimah*working12:54
zOnnywill do12:54
zOnnyis someone in the sjcompute server?13:02
thomasboimahMy bad, I was just looking at the git log, but i am out now13:03
reslsmohamud: Okay, sweet!13:03
smohamud+113:05
smohamudAnd I'm not in the server Zonny13:05
zOnnyis the members of mayfirst super slow13:09
zOnnyor it is my network13:09
zOnnyIt isn't loading on my end13:09
zOnnyI meant the mayfirst panel13:09
thomasboimahit is loading on my end13:10
thomasboimahmaybe it is your network13:10
zOnnyit looks like13:10
zOnnyI'm having a bad time with my network13:10
zOnnyI need starlink :(13:11
zOnnyI'm going to write to Elon and see if I can get a discount bc of the 4th of July13:11
smohamudSo, I just pulled and attempted to push. This is already an issue --- we need to schedule a meeting ASAP to get a proper deployment and merge process in place. For example, I didn't expect anyone else to be making changes to the SJC branch since nobody else had an assigned task but I ended up creating a conflict that could13:22
smohamudhave been avoided or at least would've have surprised me at the end of a work session13:23
smohamudI currently am two commits behind and have to resolve the old merge conflicts, again... 13:24
smohamudZonny - let me know if you're available to discuss the current process as you understand it and how we can either all get on the same page or improve the current process. We should also decide a naming scheme for our branches and codify the code review process. 13:36
smohamudDoesn't have to be today but the Dev team as a whole should come together and formalize this process or we'll risk confusion and delays when it really counts with customers down the road.13:37
smohamudAlso - have we not tried to automate the deploy process? That seems like a-lot of steps to take just to deploy. Regardless -- if we haven't codified the prod deployment process that should be done ASAP too.13:40
zOnnysmohamud: you have a good point13:42
zOnnysorry I was fixing the prod gunicorn13:42
zOnnysmohamud: that is why it is important to pull before adding more work13:43
zOnnysmohamud: it is matter of keeping in mind that you cannot asume nobody has updated anything13:43
zOnnysmohamud: first thing I do is git pull 13:44
smohamudOk but whether or not we pull everytime isn't the only issue --- that assumes someone is not waiting and handling several features at once...13:44
zOnnysmohamud: if I have some work done locally and someone has push changes13:44
zOnnysmohamud: I do git stash13:45
smohamudIf we have feature-branches that merge in on a regular basis, everyone is up-to-speed and it forces incremental changes...13:45
zOnnysmohamud: this hold my work and after pulling the changes I do git stash pop13:45
zOnnyso it brings back my work on top of the pull13:45
smohamudThat works, but the conflicts will still emerge after you pop the stash13:45
smohamudAnd --- now you have to decide whether your changes *should* overwrite the other dev, which might not be obvious at the time.13:46
zOnnysmohamud: it will if the changes have affected the files you are working on13:46
smohamudright but that's exactly what's happening. I know how Git merges happen, again, I've used it for 7 years professionally...13:46
zOnnysmohamud: the best way to avoid it is checkout to a new branch and create a merge request13:47
zOnnysmohamud: but once the merge request is made it will ask you for conflicts as well13:47
zOnnysmohamud: it is matter of deciding which one you want to apply13:48
smohamudThat doesn't remove the conflicts, though. Conflicts are tangible... One dev's code disagrees. If I checkout their branch, a clean copy, then any work I had done up to then will be subject to the conflicts. The issue isn't the clean branch, it's the huge time delays and large changes that happen in between devs pushing their work.13:48
smohamudA clean branch doesn't remove conflicts, it's a good way to start and avoid them but that's also accomplished by pulling13:49
zOnnysmohamud: yup13:49
smohamudWhich is why I think explicit feature-branches which I've done with a startup and can help us apply would reduce these conflicts.13:49
zOnny has quit (Remote host closed the connection)13:51
zOnnymy network is killing me13:53
smohamudInstead of "whoa, I didn't pull for a day but Sahnun just laid on a monster commit that conflicts with a ton of my stuff" it encourages us to make sure we deploy one-feature-at-a-time and encourages separation of concerns while developing.13:53
smohamudIt's not a magic solution for sure, but, I think it will add discipline to the frequency and scope of our commits and lead to less merge conflicts.13:53
zOnnysmohamud: that is exactly how we should do it13:54
smohamud+113:55
zOnnysmohamud: that is why thomasboimah did merge his feature branch13:55
smohamudLibre Organize actually defined a good naming scheme already we just haven't adopted it.13:55
zOnnysmohamud: it probably caught you by surprise once it got merged13:56
smohamudAh I see his feature branch --- we're heading in the right direction!13:57
zOnnysmohamud: but the point of this is really you both are working in the theme repo and both features will conflict eventually13:58
smohamudIt does look like the first feature branch that was used in the entire repo though, which to me means we need to standardize it.13:58
zOnnysmohamud: right13:58
zOnnysmohamud: we agreed on it for code review and awareness13:59
zOnnysmohamud: we have started applying from July 5th, 2026 :)14:00
smohamudWe probably would've but again this isn't about a specific conflict it's about anticipating future ones and having a good process. I think we have the right idea but just need it standardized even if it's tempting to jump straight to main branch14:00
smohamudI think we're all in agreement feature-branches are the way to go. Now, we just need a simple convention.14:01
zOnnysmohamud: before we didn't have this application due that we weren't that many devs involve in the project14:01
smohamudis feat/xyz changes what you're going for?14:01
zOnnysmohamud: right14:02
smohamudThat's fair Zonny, I think our needs have changed recently and I didn't know you had discussed using feature branches for everything alreayd.14:02
zOnnysmohamud: I have applied this for BT14:03
zOnnyhttps://gitlab.com/novawebdevelopment/business-tracker/-/blob/docs/contributing-branching-model/CONTRIBUTING.md14:03
zOnnyI forgot to do it in the theme repo14:04
zOnnyI will applied it to the the base branch and have it there for reference14:05
smohamudOk, it looks good and right but it wasn't an issue since you were basically the sole developer14:05
smohamudSweet - I think we have a solid path forward. Feature branches from here on out. 14:06
zOnnysmohamud: but you raised up the key point of good workflow14:06
zOnnyremember that theme repo is a little bit broader due that partners have their own branches and checking out from the partner's branch and work on a feature for later request a merge request into that branch14:08
smohamudSo, we need to think this one through, too...14:09
smohamudHow common would it be that changes would be me made in the theme repo that would affect multiple customers/apps?14:10
zOnnysmohamud: Nay14:10
smohamudAnd thanks - I want us to be customer ready asap and this is a meaningful part of that - being able to deliver on schedule.14:10
smohamudNay?14:11
smohamudOr do you mean *Any*14:11
zOnnysmohamud: theme is dedicated mostly for the front-end changes, that is the main goal of it. I t should not affect other branches14:11
zOnnysmohamud: however, whatever changes going in the parent branch (LibreOrganize) that will affect all theme branches14:12
smohamudLet me take a look I actually don't fully understand the repo and branch structure besides each customer is a branch of theme.14:12
resl+1 re: settling on our process - am learning a bit about different ways teams do things. I'd be grateful for Zonny to pick which one he prefers and we just use that in the meantime until we have time to do more deliberation if anyone has strong opinions on a different way if that makes sense.14:14
resl has quit (Remote host closed the connection)14:15
zOnnyresl: I think we have a clear path as for now due that feat/xyz helps us see what others are working on14:17
smohamud has quit (Ping timeout: 480 seconds)14:47
zOnnyalright14:57
zOnny[sjcompute is live again :)14:57
zOnnythomasboimah: your feat is live as well15:00
zOnnythomasboimah: seems you have done pulling it15:00
zOnnyalright team, I network is really bad today15:01
zOnnyI'm not sure what is going on. I usually have good network all the time but todays is not collaborating 15:02
zOnnythomasboimah: are you here15:07
thomasboimahYeah, Sorry i was reading Jeff research on deepseek about own a land in Liberia, since we will be meeting with someone today that may likely be helping when it come to that15:09
thomasboimah*owing15:09
zOnnythomasboimah: all good15:17
zOnnythat seems a big approach15:19
thomasboimahYeah15:20
zOnnyI'm sure it comes to a big cost 15:24
zOnnyalright team, I'm going to drop off my dad16:24
zOnnyACTION is stepping away16:24
zOnny has quit (Quit: Page closed)17:01
thomasboimahACTION stepping away for some minutes17:05
thomasboimahACTION sign off for the day18:13
thomasboimah has quit (Quit: Leaving)18:13
gabriel_jetro has quit (Ping timeout: 480 seconds)20:19
gabriel_jetro has quit (Ping timeout: 480 seconds)20:42
smohamud has quit (Ping timeout: 480 seconds)22:13
mulbah has quit (Remote host closed the connection)22:51
mulbah has quit (Remote host closed the connection)22:54
mulbah has quit (Remote host closed the connection)22:56
mulbah has quit (Remote host closed the connection)23:09
resl has quit (Remote host closed the connection)23:22

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