-
-
Notifications
You must be signed in to change notification settings - Fork 229
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
New organisation / owner for the repository #222
Comments
I really don't mind changing much 🤷 I also don't have much time to respond/fix issues these days. If you feel strongly about it, then yeah maybe an org is better.
are you? 🤔 |
Ok thanks for the comments. Let's see if some other parties would benefit from the organisation changes. We can keep things as is and move to a new org if more contributors are interested. Probably not a huge blocker now but just thinking about future: if I don't check this repo for a few months and critical updates are needed. |
In that case, why not just put a banner on this project directing people to npm-run-all? |
@cjbarth Could you explain why I should install npm-run-all over concurrently? One the indicators I use is the last published date, npm-run-all hasn't been updated in 2 years, concurrently 5 days at the time of writing.. I was about to use concurrently for a project, and then I saw this issue |
@tfrijsewijk I was more commenting on how the maintainer of this project would seemingly prefer not to maintain it. I found another thread, which I linked to in my previous comment, which discusses this very problem. That thread includes more options that just concurrently and npm-run-all. |
👋 @kimmobrunfeldt, it may be a good time to think about the handover. I'm not a fan of changing URLs (despite GitHub handling the redirects nicely), but would like to tune some settings - which unfortunately GitHub doesn't let me unless I'm the owner 😕 |
If this is the most urgent need for maintaining concurrently, would you consider pinning it to get more publicity? |
I moved the repo under a new organisation to get things moving immediately. The links etc will be updated once the owner details are locked. |
How do you feel about moving this repository into its own organization? I haven't had time to contribute lately and feel like just being a blocker for some CI etc setup. What do you think @gustavohenke ?
The text was updated successfully, but these errors were encountered: