So here we are, week two of the course and the first week a student takes on the role of sheriff. Jia and I volunteered to try it out first. We officially took over the mantel on Monday and the first two days where pretty slow. Not a lot of PR’s rolling in or questions being asked. All of that changed on Wednesday. I started to poke the bear on Wednesday to see where everyone was at with their work , and to see if anyone needed help breaking through an issue. I got a bunch of responses saying that they are wither working on it or that they needed help. In typical student fashion, everyone decided to leave their work for the week until the night before it was due.
I had the honor of leading our first real triage meeting on Thursday morning. All in all I think it went pretty well. We made sure that a couple of last minute PR’s got in before the release was done. I then went through and assigned people to tasks. I decided to look at issues that had nobody assigned to them yet. I find it’s nice to have multiple things on the go so that if you get stuck on something you can work on something else while you wait for help on the issue. After the triage meeting I told everyone that I would be doing the release at high noon. There weer some peers who would not be able to make it so we decided to record the process as Dave walked me through the process.
I enjoyed my time as sherriff, but having all those responsibility left me with minimal time to work on code. That’s why I took on the issue that I did, well that and the issue directly affects me.
PR for the week
Not a lot of coding for me this week. More R&D into the things that I will be taking on in the weeks to come. I did have two PR’s this week however. The first one was from an old task that was left over from last semester #2668. It had passed all the reviews so all that I had to do was rebase it. Dave informed us of a pretty neat tool to help expedite that process in the GitHub CLI. After installing and the using the command gh pr checkout 1234 I was able to switch to the branch in question, rebase it, and then send out a new PR for review and merging.
The other PR I did was an emergency PR done as the sheriff. We had merged some code that ended up producing a bug that prevented the backed from spinning up. So I got to do my first revert commit in order to take that bit of code out of the main line while keeping the code that was merged after the bug was introduced.
2.6 and Beyond
Professor Dave has tasked us with figuring out what we would like to contribute by the time 3.0 rolls around, and to think about how we will get there in that time frame. Aside from the Sheriff duties and the bit of coding, I have been looking into the next steps needed for Docker in the project. After reading Dave’s discussion on Docker and 3.0 I found a couple of issue related to it and have been reading documentation to figure out what needs to be done. I started off by looking at issue #2526 where raygervais suggests using Docker-slim to reduce the size of our images. After reading some of docker-slims docs I think we will need to register our images in a container registry, most likely in DockerHub or with GitHub’s own container registry. Putting them in a registry is also another issue, which I assigned myself to. It would seem that raygervais and Josue are the back end container guru’s, so I will likely have to lean on thier knowledge in order to accomplish the goal of getting the images registered and slimmed in time to ship for 3.0
Tim's Blog for DPS 909 