Skip to content
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

Closed
kimmobrunfeldt opened this issue May 18, 2020 · 8 comments
Closed

New organisation / owner for the repository #222

kimmobrunfeldt opened this issue May 18, 2020 · 8 comments

Comments

@kimmobrunfeldt
Copy link
Contributor

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 ?

@gustavohenke
Copy link
Member

How do you feel about moving this repository into its own organization? I haven't had time to contribute lately

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.

feel like just being a blocker for some CI etc setup

are you? 🤔

@kimmobrunfeldt
Copy link
Contributor Author

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.

@cjbarth
Copy link

cjbarth commented Nov 2, 2020

In that case, why not just put a banner on this project directing people to npm-run-all?

@tfrijsewijk
Copy link

@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

@cjbarth
Copy link

cjbarth commented Apr 18, 2021

@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.

@gustavohenke
Copy link
Member

👋 @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 😕

@akauppi
Copy link

akauppi commented Jun 29, 2021

If this is the most urgent need for maintaining concurrently, would you consider pinning it to get more publicity?

@kimmobrunfeldt kimmobrunfeldt pinned this issue Jul 28, 2021
@kimmobrunfeldt
Copy link
Contributor Author

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.

@gustavohenke gustavohenke unpinned this issue Sep 27, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants