Change Details

Date: 24 June 2016 Time: 12:30 UTC Type: IRC (channel #gsoc-catimages) Description: 9th meeting (Week 5) to discuss the Midterm Evaluation and Measurable outcomes as well as the last 50% of the Project Plan accordingly == Agenda: [ ] Midterm Evaluation, let's check on the Outcomes/Measurables - faces: haarcascade, generally - Consensus on plan and timeline (MVP is now!) [ ] Project Plan, second 50% - ? learning? how time consuming? (not to spend too much time on something that we cannot finish - though a actually should be quite easy to have a first theoretically working script) - ? train the bot with images of persons we now in advance that they will appear in a dataset (e.g. generals or politicians during wars, etc.) - ? train the bot on the dataset itself at least after humans have gone over it - ? Docker - ? have 2 different bot run modes: - auto: be conservative - no false-positive not to annoy commons users with unreliable bot work (and give the maintainer a lot of work to fix stuff) - user-maintained: be more experimental - show ALL possible results (no matter how significant) and the user decides which ones are valid - ? brings me to the idea {T138119} [ ] Outcomes/Measurables to be finished (and redefined) [ ] Milestones [ ] News regarding beta-tests [ ] video copyright project (jayvdb) [ ] Brief status report (jayvdb) [ ] we have to think about integrating it into this project (cross-language python and .NET) [ ] after the MVP we will start to work together (hacking session, mettings/communication, etc.) == Minutes of the Meeting:

Date: 24 June 2016 Time: 12:30 UTC Type: IRC (channel #gsoc-catimages) Description: 9th meeting (Week 5) to discuss the Midterm Evaluation and Measurable outcomes as well as the last 50% of the Project Plan accordingly == Agenda: [x] Midterm Evaluation, let's check on the Outcomes/Measurables - faces: haarcascade, generally - Consensus on plan and timeline (MVP is now!) [ ] Project Plan, second 50% - ? learning? how time consuming? (not to spend too much time on something that we cannot finish - though a actually should be quite easy to have a first theoretically working script) - ? train the bot with images of persons we now in advance that they will appear in a dataset (e.g. generals or politicians during wars, etc.) - ? train the bot on the dataset itself at least after humans have gone over it - ? Docker - ? have 2 different bot run modes: - auto: be conservative - no false-positive not to annoy commons users with unreliable bot work (and give the maintainer a lot of work to fix stuff) - user-maintained: be more experimental - show ALL possible results (no matter how significant) and the user decides which ones are valid - ? brings me to the idea {T138119} [ ] Outcomes/Measurables to be finished (and redefined) [ ] Milestones [x] News regarding beta-tests [ ] video copyright project (jayvdb) [ ] Brief status report (jayvdb) [ ] we have to think about integrating it into this project (cross-language python and .NET) [ ] after the MVP we will start to work together (hacking session, mettings/communication, etc.) == Minutes of the Meeting: - Midterm Evaluation, Outcomes/Measurables: - Have a pypi package "pypi-catimages" which can perform a minimal set of the functions that catimages.py could: in progress https://gist.github.com/AbdealiJK/a94fc0d0445c2ad715d9b1b95ec2ba03 - Detect faces using haarcascades and landmarks (need to output positions of eyes, mouth etc. were possible) - Categorize based on metadata: in progress, needs to output categorization hints to console - Barcode and QR Code detection using zbar and zxing - Graphics detection code of catimages implemented and improved but not tested on a mixed/random set yet - Consensus on plan and timeline (MVP is now!) - need @jayvdb to decide finally - @AbdealiJK proposes T138121#2395622 and T138121#2403802 which look reasonable despite some pitfals (e.g. 2 and 4): we have to take care not to spend too much time on minor things - for next week - Graphic detection on random set - Do analysis for the ETH Zurich library images - Make dlib wheel - Figure out a better way to handle dependencies - Make a CLI script which is the official bot script - Handle EXIF face data - we should not forget the setup/install procedure for experimental/development version using Docker - other proposals are welcome too, but we should avoid spending too much time here now since may be we have to sort that out in another seperate project (proper implementation of externals as vendor package management) - have 2 different bot run modes: - auto: be conservative - no false-positive not to annoy commons users with unreliable bot work (and give the maintainer a lot of work to fix stuff) - user-maintained: be more experimental - show ALL possible results (no matter how significant) and the user decides which ones are valid - brings me to the idea {T138119} - no beta-tests or new testers this week - what can we do to increase that number?

Date: 24 June 2016 Time: 12:30 UTC Type: IRC (channel #gsoc-catimages) Description: 9th meeting (Week 5) to discuss the Midterm Evaluation and Measurable outcomes as well as the last 50% of the Project Plan accordingly == Agenda: [ x] Midterm Evaluation, let's check on the Outcomes/Measurables - faces: haarcascade, generally - Consensus on plan and timeline (MVP is now!) [ ] Project Plan, second 50% - ? learning? how time consuming? (not to spend too much time on something that we cannot finish - though a actually should be quite easy to have a first theoretically working script) - ? train the bot with images of persons we now in advance that they will appear in a dataset (e.g. generals or politicians during wars, etc.) - ? train the bot on the dataset itself at least after humans have gone over it - ? Docker - ? have 2 different bot run modes: - auto: be conservative - no false-positive not to annoy commons users with unreliable bot work (and give the maintainer a lot of work to fix stuff) - user-maintained: be more experimental - show ALL possible results (no matter how significant) and the user decides which ones are valid - ? brings me to the idea {T138119} [ ] Outcomes/Measurables to be finished (and redefined) [ ] Milestones [ x] News regarding beta-tests [ ] video copyright project (jayvdb) [ ] Brief status report (jayvdb) [ ] we have to think about integrating it into this project (cross-language python and .NET) [ ] after the MVP we will start to work together (hacking session, mettings/communication, etc.) == Minutes of the Meeting: - Midterm Evaluation, Outcomes/Measurables: - Have a pypi package "pypi-catimages" which can perform a minimal set of the functions that catimages.py could: in progress https://gist.github.com/AbdealiJK/a94fc0d0445c2ad715d9b1b95ec2ba03 - Detect faces using haarcascades and landmarks (need to output positions of eyes, mouth etc. were possible) - Categorize based on metadata: in progress, needs to output categorization hints to console - Barcode and QR Code detection using zbar and zxing - Graphics detection code of catimages implemented and improved but not tested on a mixed/random set yet - Consensus on plan and timeline (MVP is now!) - need @jayvdb to decide finally - @AbdealiJK proposes T138121#2395622 and T138121#2403802 which look reasonable despite some pitfals (e.g. 2 and 4): we have to take care not to spend too much time on minor things - for next week - Graphic detection on random set - Do analysis for the ETH Zurich library images - Make dlib wheel - Figure out a better way to handle dependencies - Make a CLI script which is the official bot script - Handle EXIF face data - we should not forget the setup/install procedure for experimental/development version using Docker - other proposals are welcome too, but we should avoid spending too much time here now since may be we have to sort that out in another seperate project (proper implementation of externals as vendor package management) - have 2 different bot run modes: - auto: be conservative - no false-positive not to annoy commons users with unreliable bot work (and give the maintainer a lot of work to fix stuff) - user-maintained: be more experimental - show ALL possible results (no matter how significant) and the user decides which ones are valid - brings me to the idea {T138119} - no beta-tests or new testers this week - what can we do to increase that number?