We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In the Freakshow podcast episode 196, @hukl asked for suggestions to make contributions simpler and also ease the maintenance burden for him.
I would like to propose a new GitHub organization with a separate repo for each application:
smyck-color-scheme (github org) ├── meta (repo) │ ├── README.markdown │ ├── colors ├── web │ ├── index.html │ ├── css │ │ ├── style.css │ │ └── colors │ ├── fonts │ ├── ... ├── Terminal.app │ ├── README.markdown │ └── Smyck.terminal ├── iTerm2 │ ├── README.markdown │ └── Smyck.itermcolors ├── Vim │ ├── README.markdown │ └── smyck.vim ├── Textmate │ ├── README.markdown │ └── Smyck.tmTheme ├── Eclipse │ ├── README.markdown │ ├── Eclipse Color Theme Plugin │ └── Eclipse Preferences
For a user only interested in the Vim color scheme, the command becomes:
git clone https://github.com/smyck-color-scheme/Vim
and she is not bothered with other stuff.
I guess @hukl would be owning at least smyck-color-scheme/meta, and assign additional collaborators and owners to the application repositories.
smyck-color-scheme/meta
The text was updated successfully, but these errors were encountered:
No branches or pull requests
In the Freakshow podcast episode 196, @hukl asked for suggestions to make contributions simpler and also ease the maintenance burden for him.
I would like to propose a new GitHub organization with a separate repo for each application:
For a user only interested in the Vim color scheme, the command becomes:
and she is not bothered with other stuff.
I guess @hukl would be owning at least
smyck-color-scheme/meta
, and assign additional collaborators and owners to the application repositories.The text was updated successfully, but these errors were encountered: