Publicize Goals, Milestones, and Progress of Spec

[nebhale]

In order to help the community have visibility into the project, it's important to publicize the goals, milestones (bonus for a non-binding schedule), and progress of the spec as it moves towards official release.

[jkutner]

+1. @nebhale you mentioned that we were already tracking these somewhere, is that right?

[nebhale]

Not that I'm aware of. For example, we're about to this alpha 2, but we've never announced that to the community anywhere, what we're working to have in it, a target date, etc. There's a communal knowledge from the call, but even that call is not publicized for the wider community to attend. We're still running the project as a "Four Owners + co-workers" kind of project and it needs to become radically more open than that (especially after your presentation today ;))

[ekcasey]

I believe https://github.com/buildpacks/community should at least partially address this concern. We can open narrower issues against the community repo to capture what's missing.