Rename this repository to "handbook"

[rufuspollock]

• [x] move repo (very easy)
• [x] edit description of repo on github
• [ ] remove the current CNAME
• [ ] implement a redirect for datapatterns.org (Rufus needs to do this)

Reflecting its new purpose a la: https://discuss.okfn.org/t/creating-a-labs-handbook/2507

Create a Labs "handbook" containing key learning and instructional materials.

• Introduction to concepts around labs - civic tech, data wrangling, open tools etc
• Participating in the community - getting started with Labs - tbc
• Basic introduction to tooling
• Learning data wrangling
• (Learning civic tech - tbc)

Would live either at a subdomain or a subpart of the main site.

Note: we originally thought of renaming to labs-handbook but then we would not have it deploy at http://okfnlabs.org/handbook/ (which is what we want).

[gsilvapt]

Items to-do:

• [ ] Introduction to concepts around labs - civic tech, data wrangling, open tools etc
• [ ] Participating in the community - getting started with Labs - tbc
• [ ] Basic introduction to tooling
• [ ] Learning data wrangling
• [ ] Learning civic tech - tbc

Participating in the community has suggestions here: https://github.com/okfn/handbook/issues/89

[danfowler]

@rgrp @gsilvapt Flagging potential confusion with existing, and popular, Open Data Handbook.

[gsilvapt]

@danfowler There will be a few guides and docs available so I guess you are right. Even if this is changed to Core Datasets Handbook, it is too many handbooks.

I still think documentation should be centralized in one place, even though Open Data Handbook has a diffferent purpose than these guides and Frictionless data.

[rufuspollock]

@danfowler i know about the confusion but what would you suggest we do? If we want this to show up at e.g. http://okfnlabs.org/handbook/ we need the repo named this way. If we were willing to have at a subdomain then we could name it something like "labs-handbook". I also think the ultimate chance of confusion is relatively small in that most people do not come to the github and we do have a description on the repo.

@danfowler flag if you think there are still issues.

@gsilvapt i do not think that, at least at present, we want to merge this with Open Data Handbook. Let's see how we get on here for now.

[gsilvapt]

@rgrp I didn't suggest merging this with Open Data Handbook, although I think it would be helpful to merge with Frictionless Data's tutorials.

But now you put it this way, I think we will be fine

[rufuspollock]

@gsilvapt great!

Also in terms of the todo list above i your comment https://github.com/okfn/handbook/issues/85#issuecomment-218015745 - I suggest moving that out to a separate issue (in fact i think we may already have many of those items in separate issues). Then we can close this once we have done remaining todos in original issue description (I have just added a couple).