- Implemented an initial version of dependencies earlier in the week.
- Dealing with the always fun “first version” bugs/errors/breakdowns.
- Gathering more context to aid in the development process. (i.e. I’ve mapped out multiple features from the project, such as Groups, Bugs, and People, so that I can see how each is implemented to better understand the system.)
- Scheduling (i.e. My main days for project time shift depending on scheduling, so for example, this week my day to work on RB happens to be after the “24 hour” deadline for update reports, yet still before my meeting, therefore on paper my week looks flat.)
- Figuring out what my initial version is missing that is stopping it from allowing the saving of new dependency input for a review. I’ve mapped/charted out similar inputs (bugs, groups, etc.) and apparently I’m missing something somewhere, although atm I cannot peg it down.
- Continue developing my task and fixing errors or mistakes when they appear.
- Research, research, and more research.
- Continue finding large chunks of time to dedicate. (so far so good) My work recently changed shift procedures so I’m adjusting to a new system there.
- I’m curious on some context on datagrid.py. I understand that it seems to order column based data, and I see how it connects to the more front facing areas to allow querying of groups, group members, etc. Just wondering about it in general.
- Any suggestions on where I could find out how input error checking occurs when entering in an invalid input during a new review request? I was able to track down the jQuery for the red error bar during the hackathon weekend, but I’ve yet to peg down where the checks are done, because this might have a role in my current roadblocks. I just can’t find where it’s coded.
- Implemented self-closing as planned, published in a WIP review.
- Waiting for a bit of feedback for that.
- I have to write a good test for the above; the fixtures don’t cover it, I might need a bit of help on how to create review requests, file reviews, and issues to test against.
- Talk again to the RB devs about how they would like to see the optional”everybody/group can click fixed/drop” implemented
- None, all answered in last IRC
CURRENT (IN THE PROCESS OF DOING UNTIL SATURDAY NIGHT):
- Front end for browsing extensions. User searches for extensions (gives some parameters) and the search results are shown with the ability to install.
- Integrate the front end with the backend implemented last week (that “talks” to the server)
- Maintain a design documentation (since the actual official extensions “store” will be done later separetely).
- Add a modal window that would show more information about an extension that the user is interested in; since presently, the front end would simply let a user browse extensions (and install if needed).
- Add unit tests for the extension browser module on djblets.
- Further steps are subject to discussion/review on this week’s work and will be discussed in IRC.
- None yet.
- Making database model for trophies.
- I have a error with database evolving
- Understand Jango Framework and solve the error.
- Implement compute_trophies function which get data from database
- I just joined, so I’m working on running and building ReviewBoard on my Macbook
- Currently having an issue related to the installer script and llvm-gcc, but I will likely be able to figure it out
- Finish building + running ReviewBoard on my local machine
- Make first bug fix
- None yet
- Just reinstalled the OS on my computer, so had to setup development environment again. Seems to be running fine.
- Initial unit tests didn’t pass; asked on IRC and it may be due to some Fedora update
- ChipX86:okay, so I think this is due to a fix we got from the fedorahosted guys that didn’t actually fix the unit test
- Otherwise fine, trying to get rolling.
- Pick off a few easyfix bugs and select a project from the list.
- Nothing big
- I got a new computer so I’ve been working on getting my development environment set-up. Done, works, builds.
- I’ve been reading over the extensions sections in djiblets and review-board sections, but have not made any changes in code yet.
- (Tomorrrow) I will be working on the project and will start to make come with a first code changes and test to see how I can implement the sandboxing.
- (This week) Make progress on determining best way to implement sandboxing based on results of working tomorrow and asking any questions that may arise.
- Fix the unit test for SSH Key Deletion
- Usually work on the project on Friday night or weekend, so haven’t done much yet after last status report
- Continue on the markdown functionality
- First, build the toggle on editor which will let user to choose whether enable markdown
- Nothing for now
- My computer crashed this week, so much of my time was dealt with recovery with luckily went quite smoothly.
- Code reading
- Start hashing out some new code, I plan to start this weekend to catch up
[Edited to add Yuri’s report at 10:50pm EST]
- Fix bugs(2753) completely
- Study django
- I don’t understand how to work templates.
- Improve understanding about django.
- Which does python-codes control templates? (esp. “templates/accounts”)
[Edited to add Gabriel’s status report]
- Cleaned up the CSS of the widgets in the admin in preparation of using the drag and drop from jQuery UI (for some reason the widgets on the right were using masonry, but only for one column, so replaced it with floats) And researched the ways to do the drag and drop and checked how the different widgets are built.
- I still need to make resizable the charts in the widgets which are now with fixed width. Then when all the widgets are free from their fixed sizes, will do the drag and drop.