-
Notifications
You must be signed in to change notification settings - Fork 13
GSoC 2014 Jennifer Parak & Julia Proft
I've recently graduated in MSc Advanced Computer Science at University of Sheffield, UK with a 1st-class Honours. My background is in Information Technology (Database, Web Design and Information Engineering) and I completed various other Computer Science modules this year covering: Advanced Programming in Java, Machine Learning, iOS Development, Speech Processing, Computer Security, Network Performance Analysis and Distributed Systems. My great interest lies in Computer Security, therefore I chose to write my MSc thesis on Cracking image-based Captchas.
Something about me: I'm originally from Austria, but home everywhere in the world. I speak 4 languages fluently, I love travelling, good books and movies, (live) music and sports especially Snowboarding (I'm a certified Snowboard Instructor) and also I play Ultimate Frisbee on a highly competitive level.
Basically everything I do - I do with a passion!
Website
LinkedIn Account
Github Account
Twitter Account
Email
I participated in Google Summer of Code 2014, working with the Peace Corps Ushahidi Crowdmap Project team with Julia Proft.
I was mainly focusing on Search and Map Features, as well as Adding Features and Pages (see Timeline).
Google Melange Project Description
- Meeting with Julia & Rose
- Updated Requirements V.07
- Updated my timeline
- tested VM environment on MAC (-->it works)
- in the middle of exam period
- No
- Talk to Mentors, add exam dates to timeline
- Talk to mentors, add exam dates to timeline
- 2 Exams, 1 Coursework
- start working on my first issue: Map Constrain Zoom
- As planned
- Google Hangout project update
- Testing MySQL access and VM
- Exams
- My last exam is on the 9th June (today)
- Considered in my timeline, will catch up on the work after exams
- Don't think so
- I will start working on my first issue and completing until next week
- Project Update on Wednesday
- Yes, so far so good.
- I've organised a weekly Google Hangout for our project team
- Exams
- My last exam is on the 9th June
- Considered in my timeline, will catch up on the work after exams
- Don't think so
- After my exam this Tuesday (tomorrow), I will start looking into my first issue, in order to start working on it straight away after my last exam on the 9th June
- Organise a way to communicate with our 'client', the Peace Corp volunteers, to keep them up to date
- Yes, so far so good.
- Finished my first issue: M2.1 Constrain Map
- Exams
- Warned my mentors that I will start late , Exams are over now
- No
- No
- finish 2 more issues this week
- update documentation on my blog (today)
- update my wiki page (today)
- Looks good, providing that code review goes well
- I've been pretty busy this week. I will send another pull request of my first task T1 Constrain Map Zoom (as I was working on the wrong repository) along with two tasks I finished this week: T3 Allow Partial Search in Report Filter as well as T6 Loading Screenshots.
- I am also about to finish my task T2 Remove 'Alert' tab and replace with 'opportunities' tab.
- We have had some difficulties with the repositories we were supposed to work on. It turns out, the Peace Corps Ushahidi repo as well as the forked Systers repo do not contain the correct version of Ushahidi. As a result, I was working on the wrong repository for half a week and had to do my work again from scratch.
- I've also accidentally mixed up my scheduled tasks, which is why I started working on T6. I realised, however, that it was a really small task so decided to finish it.
- Not yet I think.
- I'm still not 100% confident if what I'm doing is right, but I've been told to go ahead and keep on coding so that's what I'm doing :)
- I'm hoping we can sort it out during the next Update Meeting.
- I've got 2 more issues to work on: T4 Changes to Map Indicators and T5 Options for Filtering Reports
- Finish documentation tonight, as some parts are missing, but will be up today
- I'm actually ahead of schedule, but I'm aiming to leave some time spare for making changes to my code after our first code review.
- I have worked on adding a new page listing resources required, as well as a functionality for users to post resources offered which is returned in a list on the page. I further changed the options for filtering reports according to our clients' needs.
- I have underestimated the complexity of adding a new page.
- I had to do a lot of research on the Kohana Framework and I'm now doing a bit of bug fixing, but should be good.
- Incorrect repo, a few bugs in my code
- I'll ask a few questions at the meeting tomorrow
- Complete 'adding a new page task', Complete new task to add 'change current map indicators'
- It's looking good
- I have worked on T4 Adding a New Page and T5 Editing Filtering Options on my timeline
- None
- None
- Incorrect repo has been fixed
- No
- Now that the repo issue has been solved I want to spend this week going through what I have done and test my code again. If everything is okay I will start making pull requests to the correct repo so they can be code reviewed.
- Still on track
- As planned, I have copied all my code to the new crowdmap repository on Github and have sent 5 pull-requests
- On testing I have faced a few issues with my code, which I will go through with my mentors this week
- Not yet, waiting for code review
- Waiting for code review
- Waiting for code review
- I am going to work on two issues: "Changing map indicators" and "adding an active/inactive project button" which are scheduled for the 20th July. Ideally I would like to start working on my last issue, in order to have enough time for testing and getting my code to work.
- All good!
- I have worked on copying all my changes to the new repository
- I have finished 2 more issues on Map Indicators: showing inactive & active incidents, changing the map indicators on the Home Screen
- I've had problems copying all my changes, it seems that some of my work got lost.
- No, not yet.
- They still exist, but I only have one issue to work on and then I will make sure my old code works on the new repository.
- No, I will work on it end of this week.
- I am going to work on my last issue this week and send the outstanding pull requests.
- Still on track, cause gladly I left a puffer in my project timeline.
- I have worked on my last issue on the project timeline: Add Azerbaijani character to search bar
- None
- None
- None
- None
- I want to publish all my pull requests on Github so I can go through all my code with my mentors and also look into what needs to be done before the end this years GSoC
- Looking good.
- I have finished my last task: Add Azerbaijani character to search bar and sent my last pull request on Github ready for code review
- None
- None
- None
- None
- I'm planning on testing everything I have worked on this summer and resolve any issues if necessary. I also want to prepare for our Demo with the Peace Corps Team.
- Right on track :)
- I fixed a lot of my issues and most of them will hopefully be merged soon.
- I've had a lot of problems getting all my code to work. Unfortunately I didn't know that we would have a Demo before the end of the GSOC programme, but I'm trying to get everything done as quickly as possible
- No, not yet.
- Yes, I will try and sort them out with my Mentor today.
- None
- I'm planning on making my code look nice, finish documentation & testing.
- Official project schedule looks fine, but I'm scared I won't get everything done before the Demo.
Hi there! I was a Google Summer of Code (GSoC) student with Systers in 2013 and 2014, and I've been a Systers GSoC mentor since then. I also manage all of the virtual servers for our GSoC projects as the technical infrastructure coordinator for the Anita Borg Institute. It's nice to meet you!
Personal Website
GitHub Account
LinkedIn Account
- I met with Jennifer and divvied up the tasks for the Ushahidi project. Then, I updated my timeline (which can be found here). Also, I installed and tested the VM environment successfully.
- None!
- Nothing to resolve!
- Nope!
- Negatory!
- If everything is all set with the Ushahidi environment, I plan to start working on the first coding item on my timeline (changing the required field error validation outcome on the new report page).
- Right on track!
- This week, I finished the first item on my task list (changing the required field error validation outcome on the new report page). A description of the problem and the solution I came up with can be found on my documentation page here.
- No issues this week!
- Nothing to resolve!
- Nope!
- Negatory!
- For the next two weeks, I have three items on my schedule: enabling admin editing of default report fields, putting form field explanations under the field name, and allowing members to edit their own submitted reports. I'll start working on those tomorrow. :-)
- Right on schedule!
- In addition to starting work on other tasks, I fixed a bug (admin edit links are no longer displayed for non-admin next to every report) and added a feature (member edit links are displayed for the author of the report if s/he is not an admin). You can find a lot more information about the issue and my solution here
- The only issue I had, and a minor one at that, was that I had not been told the username and password for the MySQL account on the VM.
- Yep! I was told the login information!
- I was able to successfully log in, so the issue has been surmounted. :-)
- Nope!
- Next week, I plan to finish the two items I started at the beginning of the week (but stopped working on while I waited for the MySQL password); these tasks are the editing of default report fields and the ability to move the form field explanations.
- Still on schedule!
- This week was very busy indeed. :-) I accomplished the two scheduled items on my timeline: enabling admin to add field explanations as subtext beneath the names of custom fields, and allowing admin to have some control over default report fields.
- No issues this week!
- Nothing to be resolved!
- Nope!
- Nope!
- For the next two weeks, I'm shifting my focus from the reports to the home page. The next two items on my list are removing unnecessary features from the index page and adding a search bar to this same page with local language support. I will work on the former item for this coming week, and the second one for the week after.
- Right on schedule!
- I did a bunch of different things this week! I have been working on improving the Ushahidi homepage, and one of the tasks I completed allows admin to decide whether they want users to redirect to their personal dashboard or to the homepage upon login. I also added unit tests to my documentation this week (see here). To decide how best to streamline the homepage and remove unnecessary features, I made a mockup layout (which you can find here); I then updated the Peace Corps clients on what I have accomplished thus far, and I got some feedback on the layout. Lastly, I finished merging and preparing all the code I have worked on for a code review.
- One issue is that the Peace Corps Ushahidi repo does not contain the version of Ushahidi that they are using. As a result, the Systers repo also contains the incorrect version, and it does not make sense to fork from the Systers repo since the files are completely different.
- No, not yet.
- The wrong-version issue has not been a roadblock per se because it hasn't actually impacted my work (I've been working with a fork of the correct version), but it still needs to be fixed to facilitate code reviews. We have discussed the issue as a team, and it should hopefully be resolved soon.
- No, I'll just continue my work the way I've been doing it; and once the issue is fixed, I will fork the Systers repo.
- I will continue working on the homepage and its revamped search bar. :-)
- On track!
- This week, I gave site admin the ability to deactivate unnecessary features from the homepage by adding several more options in the settings. To accompany this, I created a new Ushahidi theme that matches the mockup layout I sent to the Peace Corps clients last week. Finally, I improved the look of the search bar on the homepage; and for this coming week, I am going to enhance it by allowing users to search for keywords and have the map dynamically update with report hits for the keywords.
- No new roadblocks this week.
- Nothing new to be resolved.
- Just the incorrect repo issue, but that's not impeding my work.
- No, I have been able to complete my work despite the repo issue.
- As I mentioned above, I will add enhanced functionality to the search bar, and I will use this same searching functionality to give users the ability to download reports based on a keyword search.
- Right on track!
- Building off of the work that I did last week, I enhanced the search bar on the home page by allowing a keyword search to dynamically update the report markers that appear on the map. Along a similar vein, I gave users the ability to further customize the CSVs generated when downloading reports using keyword searches. I also contacted the Peace Corps clients with a few questions, clarifications, and suggestions concerning these tasks. I should be hearing from them soon, and when I do, I will make any needed adjustments to my work this week accordingly.
- None!
- Nothing to resolve!
- No issues still exist now that the repo has been fixed. :-)
- Nope!
- I will make any changes necessary to my work this week based on what the Peace Corps clients think, and I will also begin work on my next set of tasks, which includes creating notifications for the reports tab and the opportunities tab as well as fixing an issue where comments do not display.
- Still on track!
- Based on the needs of the Peace Corps clients, I decided to create a new format for downloading reports. I also looked into the issue where comments would not display on reports, and I fixed a bug that I believe was causing the problem.
- No roadblocks!
- Nothing to resolve!
- No existing problems!
- Negatory!
- Next week, I will work on adding notifications to tabs that will let users know when there is new content. If I have time, I will tackle a few miscellaneous items for filling out reports. Additionally, I will start preparing all my code for the new GitHub repo!
- Right on track!
- Huzzah! I managed to finish the remaining two tasks on my list, which were the notifications for tabs and some improvements for filling out reports. A couple of the tasks will still need some additional work after my work is integrated with Jennifer's, but for the time being, they are complete!
- No major issues!
- Nothing to resolve!
- No existing issues!
- Nope!
- Early next week, hopefully tomorrow, I am going to get all of my code on the new GitHub repo for review. :-) I also need to write a couple SQL scripts for the database changes I made on my virtual machine.
- Ahead of schedule!
- At long last, I finally made a pull request with all of my changes to the GitHub repo! (See for the details about the commits.) In addition to this, I wrote the necessary SQL scripts for the database changes I made, and I also fixed a couple bugs.
- No roadblocks!
- Nothing to resolve!
- Nope!
- Negatory!
- Next week, I will continue the code review process with my mentors and make changes as needed. :-)
- Right on track!
- This week, I updated the Peace Corps clients with the details of the tasks I have completed during the second half of this summer. In addition, I have been trying to arrange a live demo date with Peace Corps, which will hopefully happen within a week or so.
- No issues!
- Nothing to resolve!
- Negatory!
- Nope!
- I will make further arrangements and prepare the demo. I will also continue the code review process with my mentors. :-)
- Right on schedule!
- I didn't have much to do this week, other than going over a few things with my mentors. My code has been merged into the Systers fork of the Ushahidi platform as of last Tuesday!
- No roadblocks!
- Nothing needs to be resolved!
- Nope!
- Negatory!
- Hopefully, we'll have our demo with the Peace Corps clients next week! I will continue to prepare the application on the server and test it out to make sure everything runs smoothly.
- Right on track!