| DrTrigon edited the task description. (Show Details) |
EDIT DETAILS
- faces: haarcascade[ ] Categorize based on metadata: in progress, generally
- Consensus on planneeds to output categorization hints to console
[ ] Graphics detection code of catimages implemented and timeline (MVP is now!)improved but not tested on a mixed/random set yet
- Consensus on plan and timeline
[ ] Project Plan, second 50%
- 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}
- @AbdealiJK proposes T138121#2395622 and T138121#2403802 which look reasonable despite some pitfals
- ? 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)
- ? 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)
[ ] video copyright project (jayvdb)
...
[ ]- Midterm Evaluation, let's check on the Outcomes/Measurables:- faces: haarcascade[ ] Categorize based on metadata: in progress, generally
- Consensus on planneeds to output categorization hints to console
[ ] Graphics detection code of catimages implemented and timeline (MVP is now!)improved but not tested on a mixed/random set yet
- Consensus on plan and timeline
[ ] Project Plan, second 50%
- 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}
- @AbdealiJK proposes T138121#2395622 and T138121#2403802 which look reasonable despite some pitfals
- ? 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 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)
...
[ ] News[ ] News regarding beta-tests - how can we increase the number? regarding beta-tests(India Meeting)[ ] video copyright project (jayvdb)
...
TASK DETAIL
EMAIL PREFERENCES
To: DrTrigon
Cc: pywikibot-bugs-list, jayvdb, Aklapper, AbdealiJK, DrTrigon, Zppix, Lethexie, Jay8g
Cc: pywikibot-bugs-list, jayvdb, Aklapper, AbdealiJK, DrTrigon, Zppix, Lethexie, Jay8g
_______________________________________________ pywikibot-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/pywikibot-bugs
