Private vs Public

[rasagy]

Forking the conversation around documenting the project/opening the repo from here.

From what I’m seeing, this code is only front-end code (tilesets are read-only). I see no harm in making this public so others can understand how to build a project like this. It would also enable us to document the project in the Readme/wiki here.

@batpad Based on the https://github.com/mapbox/osm-analysis-dashboard/issues/9#issuecomment-330739661 I think both Jennings & Ramya would prefer to make this repo open and document the project using wiki/Readme. Want to go ahead and make it open?

cc @jenningsanderson @ramyaragupathy

[rasagy]

Just realized Jennings has already started documenting properties in the wiki: https://github.com/mapbox/osm-analysis-dashboard/wiki

[batpad]

I'm 👍 on making this repository public.

cc @michaelsteffen @mikelmaron

[batpad]

^ Let's just make sure we do a review of commit history and issues before we do so and scrub anything that needs to be scrubbed with issues linking to internal repos or anything else

[jenningsanderson]

:wave: I started some quick documentation in the Wiki - can easily move this out to a separate about.html page, but the wiki seems like a good place to do it, and since this is all front-end, I also see no problems with it being open

[batpad]

I have looked through the issues and code history and I don't see anything that prevents us from making this public.

Am going to give this a few hours in case anyone has any objections and then go ahead with making this public.

[jenningsanderson]

👍