Capture some additional metadata in templates

[keefertaylor]

• Name / Contact => Historically useful for folks to get in touch, and for internet points
• Created => Useful for easy dates
• State => Useful to know where a proposal is, and what happened to it.

[Fitblip]

I like name/contact (probs an email?), but I think date of creation and state are better managed through the git process TBH since it records all this information anyway.

EDIT: then again, git/github also gives an email right?

[keefertaylor]

I think that folks should be contactable through whatever means they think is long lived for them and we should support that.

I'm fine if you want to drop creation date - how would you propose github manages state? Do we just not merge failed proposals?

[Fitblip]

I think that folks should be contactable through whatever means they think is long lived for them and we should support that.

Yeah IMO github is that thing so an additional contact info feels extraneous, but I don't feel strongly about that.

I'm fine if you want to drop creation date - how would you propose github manages state? Do we just not merge failed proposals?

Yeah I think this repo can serve as a source of truth for this off-chain process, but I also think that in general KIPs will generally lead to DAO proposals, even if they fail on-chain (so maybe we should add a link to the on-chain proposal when it happens). The goal is to get things squared away and work out the kinks of implementation in a collaborative way (here) instead of in a vacuum.

IMO zooming out we serve as the initial council to help shepherd things, but I also think that anyone who submits a proposal in earnest should be given contribution rights to this repo since they're obviously interested in helping the gov process and the more people involved the better the proposals will (theoretically) become.

[keefertaylor]

Yeah IMO github is that thing so an additional contact info feels extraneous, but I don't feel strongly about that.

I think it's plausible that someone may open a proposal, who isn't a dev and who doesn't really use Github, keep it up to date etc. I can also imagine a group of folks submitting a proposal, and wanting to credit them as well?

Yeah I think this repo can serve as a source of truth for this off-chain process, but I also think that in general KIPs will generally lead to DAO proposals, even if they fail on-chain (so maybe we should add a link to the on-chain proposal when it happens).

I think it's worth capturing historical discussion on proposals. I realize that they're captured inside of closed un-merged PRs, but those aren't indexable and searchable.