Comments (6)
Structural aspects that need to be checked / fixed when reviewing profiles:
from opws-dataset.
Okay, quick back-of-the-envelope calculation says I can knock all of these out by the end of the month if I accomplish five reviews a day.
That seems... maybe manageable, but, of course, the big thing is, what do I want a review to entail? The reason I've made so little progress, really, is because each review I've done has involved so much other stuff, like, in a lot of cases, figuring out what happened to a site, or how something I wrote before relates to what I'm doing now, and stuff like that.
So... ech.
from opws-dataset.
FWIW, what I'm finding right now is not so much that I'm getting blocked on the reviews themselves, but that I'm getting swamped by all the refactoring I'm doing between reviews, including all the meta-natter that I'm putting into issues. Like, I'm four profiles behind schedule right now, and that's because, for the last few days, I've been up several hours past midnight spittin' proposals and cross-references and stuff like that trying to keep track of what I'm not recording. (I think just coming up with the WILDCARD
solution took me up to 11 PM on Tuesday night.)
That said, previously I've let that stop me from working on this, and, well, this month it's my Project of the Month, so I'm going to stick with it, and I'll see what keeps popping up in the long term, and, well, we'll see.
from opws-dataset.
Okay, so, I've made pretty good progress on this so far (there are 25 remaining to be profiled, and, wow, I'm pretty sure that number was over 100 before I started), doing these reviews has given me a lot of insight into how the schema should be drafted, and I've hit on a really solid workflow for putting these reviews together in the future.
However, as much as I want to review the 25 remaining unreviewed profiles before the 28th, I'd rather spend the rest of this month closing out a bunch of the other remaining issues on this project, including splitting it up into separate repositories, and writing a proper schema with validation.
As such, I've decided I'm going to chump out and add reviewed dates to any remaining profiles that were added individually based on the timestamp of their first commit (or the last commit that meaningfully updated their information), and then only immediately review any that are still unreviewed after that. (A new issue can be opened up once this is done to review all the profiles that got retroactive review dates based on a "review everything before April 15 2015" filter, which can then be done post-February.)
from opws-dataset.
Okay, I'm merging this in now, as #280. (I'm holding back a couple profiles that I intend to either remove or move with review, as those will be separate PRs.) Every site that was added with its own commit (including everything after this project was first established) uses the date of that commit as its timestamp; every site that was added in the original blot.pw list in a monolithic commit adding multiple sites uses the date of the prior commit (as we can't know for certain that it was any later).
For reference, this is the breakdown of how the backfill dates were established:
Backfilled from domainprofiles commit
- flattr.com
- diigo.com
- disneyworld.disney.go.com
- trello.com
- iwantmyname.com
- topcoder.com
- zipcar.com
- gravatar.com
- wordpress.com
Backfilled from atomic blot.pw commit
Backfilled to 2013-10-22T06:29:22Z, committed at 2013-10-25T18:19:02Z
- eventbrite.com
- guru.com
Backfilled to 2013-06-16T01:33:52Z, committed at 2013-09-09T06:25:54Z
- laptopscreen.com
- digitalocean.com
Backfilled to 2013-05-30T17:41:28Z, committed at 2013-06-16T01:33:52Z
- html5-ninja.com
- twilio.com
- projecteuler.net
- wibit.net
Backfilled to 2013-05-06T11:07:47Z, committed at 2013-05-22T13:09:06Z
- yahoo.com
- linode.com
from opws-dataset.
Okay, now that #280, #281, #282, #284, and #285 have closed, all profiles have a reviewed
field (as far as I know), so this issue, in its current form, can finally be closed (with the potential for a similar issue to be opened later).
from opws-dataset.
Related Issues (20)
- Moving terms and statements into a general "Legal" list HOT 12
- Limits on how much you can change / reset your password HOT 1
- Using `email` and/or `password` fields under `form` instead of `account` when only one is present HOT 1
- Shim layers HOT 2
- Matching URLs HOT 2
- Diversifying `password.value.blacklist.previous` HOT 1
- registration.form.company
- registration.form.country HOT 1
- Standardizing commit / pull request title format HOT 2
- Some profiles are REALLY pushing the schema
- Input masking should be described as `masking`, not `characters`
- Profile needed for Zapier
- Profile needed for cron-job.org
- Profile needed for Uptime Robot
- Deprecating schema issues in this repository
- Removing notes that won't migrate in v0.2 HOT 2
- selfservice.travelers.com password rules need review
- Profile needed for USPS.com
- usps.com profile needs password reset flow
- Profile needed for postable.com
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from opws-dataset.