acarapetis
Repository transfer
Hi @acarapetis,
I've published your theme in my github account and it already received some contributions, but I don't have enough time to review the issues and pull-requests: https://github.com/endel/vim-github-colorscheme
Do you still have interest on this project? May I transfer the repository to your account? Thanks
I could take it over - I have the time, but I'm pretty out of touch when it comes to good practice in terms of both vim and git. Perhaps it would make more sense to somehow merge it with the other popular copy https://github.com/croaky/vim-colors-github ?
Nice! I didn't noticed that there is a version from @croaky too. :)
My version received a pull-request refactoring the entire colorscheme, and a new dark theme (which was not merged yet)
Maybe it's a good idea to me and @croaky to update our README's pointing to your repository when yours get up-to-date. What do you guys think?
Hey folks!
I use the GitHub light theme every day in Vim. Love it!
Maybe we transfer the croaky/ repo to acarapetis/ so @acarapetis gets the primary credit for it via the name of the project?
Then, reference that acarapetis/ repo from this endel/ repo's README? Turn off PRs and Issues in endel/. Handle any pull requests over at acarapetis/. All three of us with contributor access at acarapetis/ so we can share the maintenance load.
I'm not very experienced writing Vimscript, either, but happy to learn as I go. I personally don't have a need for the dark theme so would look to y'all to decide whether you want the dark theme, and if not, whether it is worth us supporting or instead asking the contributor to manage the dark theme as a separate project.
Just got a transfer request from @endel as well. How exactly are we handling this? Endel's version (with contributions from @lucastadeu) is longer, though neither is a strict superset of the other. It also has the most stars on github. I'm guessing there's no procedure on github for "merging" two different repositories in this sense - which should we stick with? How best to signpost the others? @croaky
Ah, interesting. I doubt there's a procedure on GitHub for merging two repositories but maybe there's a procedure for moving watchers / star-ers to a different repo?
It looks like The vim.org version is based off the croaky version at this point and there's only a handful of commits to pull in from the endel version? Maybe we try to pull those changes into the current acarapetic version?
- 256 color support
- License - MIT or same as Vim?
- Fix TODO highlighting
- Fix invisible cursor in GVim
- Search highlights in yellow
- ColorColumn highlight - same thing as https://github.com/acarapetis/vim-colors-github/pull/1?