explain the roadmap

[rakyll]

Could you add on README what is the roadmap for the dep tool?

Should we consider this to proposed to the core project once it is mature enough? What are the next steps once the proposal is accepted? What happens if the proposal is not accepted? Can I depend dep on an actual use case right now?

[sdboyer]

I'll answer what of this I can off the cuff...

Could you add on README what is the roadmap for the dep tool?

I suspect we can add as much as we know right now, and keep it up to date. Not everything's clear yet, though. (We may also end up keeping that information somewhere other than the README.)

Should we consider this to proposed to the core project once it is mature enough?

Yes, though you should also expect that it will not make a direct, 1:1 migration into the toolchain. So, no go dep ensure. @rsc doesn't want to see sub-sub-commands; he instead wants to see it integrated in a deeper, more transparent way.

Can I depend dep on an actual use case right now?

No. The README is already clear on this, I think.

[Oxyrus]

Will this be included as dependency manager in future releases of Golang?

[rakyll]

Will this be included as dependency manager in future releases of Golang?

@sdboyer, I think these types of FAQ questions needs be answered on the README.

Currently, the tool looks like it is the new blessed solution which happened to be in pre-alpha state. (Even pre-alpha is vague because the Go project doesn't have an alpha/beta/stable labelling.) FWIW, people who don't follow the Go news on a daily basis don't often have context about what's going on and might end drawing wrong conclusions or expectations.

[davecheney]

Seconded. You're carrying the hopes and dreams of all gophers, keep it classy.

[sdboyer]

@rakyll these are great points. I'll update the language tonight.

@davecheney 😱 🎩 🎩 👍

[sdboyer]

s/tonight/tomorrow/. need 🛌

[sdboyer]

small update to say - i have to confer with the committee before putting up a roadmap, even a tentative one. i'll get that up as soon as i can next week. meanwhile, i've updated the README to state clearly that the tool is neither official, nor blessed.

[krisnova]

Isn't the tool at least a candidate to becoming official/blessed? If so would it make sense to call that our in the README?

[sdboyer]

@kris-nova it is indeed a candidate, and that's very much the path we're on. I tried to indicate as much:

It IS, however, the consensus effort of most of the Go community, and being integrated into the go toolchain is the goal.

[sdboyer]

Took much longer than I'd hoped (sorry!), but here's the promised roadmap: https://github.com/golang/dep/wiki/Roadmap

I'll be updating the README presently.