New issue
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
Would you like some help clearing up the back PRs? #262
Comments
I think it's best if you merge the pull requests into your own repo and then create one big pull request. |
@nodiscc you could always consider contributing to http://www.github.com/n1trux/awesome-sysadmin :) |
Yep, I think I'll contribute to that :) Nice to see an active fork. |
Hey guys Nice to see that you are backing @kahun in maintaining this project which really requires a lot of maintenance. Currently it seems to me that @kahun can not keep up with maintaining it alone and @n1trux is doing a good job in maintaining his fork. To improve this situation a little future I am proposing that one of us creates an organization and @kahun moves https://github.com/kahun/awesome-sysadmin to this organization (since it is the most popular repo). When moving it, GitHub will redirect to the new URL (as long as @kahun does not create a new kahun/awesome-sysadmin after moving). Then @n1trux and others can be made contributors. This should help us all in the long run. Also, as there are similar projects like awesome-sysadmin I think this org could be a good home for them as well. Thoughts? Proposals for the org name (all currently available): |
I don't care if that repository is on my resume, so if you think that creating a new org for this will ensure continued maintenance, do it. I think just moving my repo into the new org would be easier, because else there'd be a small merging hassle. Is that a dumb idea? There should be at least 2 or 3 people in charge of the new org, too, not only multiple contributors for the projects. 👍 for awesome-foss. We could ask @awesome to rename himself for this – if he'd be so kind, we could have a nice, short URL (maybe /awesome/sysadmin?). |
Thanks for your feedback.
You can still do that with GitHub’ possibility to pin repositories on your profile page. Check: https://github.com/ypid
Not necessarily. We can still switch to your branch. I recommend that we move https://github.com/kahun/awesome-sysadmin to the new org as primary repository. @n1trux You can still keep your fork this way. After the new org has been set up, I think it would be save to start with your fork (you can open a PR and instead of merging, use something like
We are at least four people who care enough about this to offer their help here 😉 So I hope that works out.
That would be awesome 😄 but I am not sure if @awesome would do that. Not sure if I would. I think if we don’t here from Mr. @awesome we can go with awesome-foss. @n1trux As you already have experience with maintaining this project (and your related project awesome-donations which I would suggest to also move then) would you like to create the org? I could also do it if you want but I am not as much involved with this project as you are. @kahun What do you think about this? |
I'm willing to be a contributor. I'm a contributor for dotfiles.github.com and am the primary author for awesome-zsh-plugins. |
Someone active on g+ or knows enough Spanish to find another way to contact @kahun? |
Happy to reach out to him in Spanish if we think it'd help. Although the issue is likely not language and more just that like everyone his github notifications are super noisy/spammy. |
@kahun, would you like some help getting these PRs triaged and merged?
The text was updated successfully, but these errors were encountered: