We have less than 3 weeks left now.
Projects that are just starting aren’t necessarily going to be finished and that’s expected.
Presentations need to be done soon, quality is better than quantity. Presentations should be less than 10 minutes long, and being shorter is generally better than longer, don’t fill for time. Showing is better than telling and it helps to write a script for yourself and do a few trial runs before you start recording.
We will have a ‘post-mortem’ meeting on April 10th at 2 pacific time (an hour before our usual meetings).
ChipX86 talked to a couple people about revised schedules and is hoping people have a bit better of an idea as to where they are in their current projects, and would love to see a rough time table based on that.
ChipX86 reviewed the requests that were online and people likely saw lots of comments. This is normal and is going to happen while people are learning the coding style and Pythonic ways of doing things.
ChipX86 says that every line of code in ReviewBoard must be reviewed. If you’re working on a big project, you probably want to post smaller reviews when you start out so that you can get feedback to make sure you’re on the right path.
Even David and Christian review each other’s code so that everything gets reviewed.
ChipX86 and purple_cow are working on a patch for the issue where running a subset of tests no longer works.
ChipX86 proceeded to help people with questions specific to their project.
I started the code sprint by picking up bug #495: Add a To Me column to the Dashboard. The bug was really good for seeing how ReviewBoard and Djblets work together. I ended up doing a lot of digging in the DataGrid and Column classes.
I spent a good amount of time helping others with git on Saturday and got some help from ChipX86 with some issues I was having with my bug and finished that up and submitted my first review to ReviewBoard.
All in all the sprint seemed fairly successful, git is all set up and I now know how to post my stuff to ReviewBoard.