-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Perform November Crawl #118
Comments
If it fits with your planning, I'd suggest giving it another week starting the crawl around July 15. The reason is that the time period between crawls is usually two months. Adding one more week in this case keeps the time periods a bit more aligned. The more time between crawls, the more likely we will see differences. |
Given that we first need to address #122, the goal is to start the next crawl by September 2. |
We should start the crawl this week or next. |
We should crawl for both California and Colorado. |
@franciscawijaya will start the California crawl this week and afterwards @natelevinson10 will start the Colorado crawl. |
Adding @eakubilo as special advisor. 😄 |
As discussed today, we aim to crawl:
Ideally, we are even quicker to avoid getting into the Thanksgiving break. Before the California crawl we create the release (#76). |
I will be performing July Crawl. Taking into account the duration of June crawl and other upcoming tasks in the month of July, I am planning to start the Crawl around 8th of July so that we would have ample time for any possible re-do (if any of the batch fails), analysis, creating figures and provide the results to the planned datasets for community resource. After July Crawl is done, I would then move on to do other tasks for July.
The text was updated successfully, but these errors were encountered: