Upstreaming to BitBake?

[mostthingsweb]

More of a question than an issue I guess. This repo fixes a number of problems with the vim scripts in upstream BitBake. Also, I implemented an indent plugin in upstream, not here.

Should this repo be the "official" location for vim scripting, or upstream BitBake?

[kergoth]

Originally this repository was intended to just provide the files in an easier to consume form, as it can be used with vim plugin managers, but eventually over time they got out of sync with the bitbake repository content. We definitely need a canonical version of the content, and I think the version in the bitbake repository isn't an ideal form.

Either bitbake is canonical and we could automate the maintenance of an official vim-bitbake based on that, locking down the issues/pullrequests on it, or we should have an official vim-bitbake that's canonical and remove it from the bitbake repository. I don't feel too strongly either way on that.

[mostthingsweb]

Eventually it could be nice to have the plugins in vim upstream itself. So we may want to consider making this repo the canonical location, as a stepping-stone. Just a thought.