Skip to content
This repository has been archived by the owner on Sep 28, 2020. It is now read-only.

LOOKING FOR A MAINTAINER #264

Closed
ThomasKientz opened this issue Jan 25, 2019 · 25 comments
Closed

LOOKING FOR A MAINTAINER #264

ThomasKientz opened this issue Jan 25, 2019 · 25 comments

Comments

@ThomasKientz
Copy link

From previous maintainer :

Please please please, #webpack community, please take control on eslint-loader. Nobody is maintaining it. I do whatever I can because I don’t like to let things rot… but I am about to let it rot (I don’t use eslint-loader for months…) and will ignore its notifications soon.

https://twitter.com/MoOx/status/1044577532815855616

@MoOx
Copy link
Contributor

MoOx commented Jan 25, 2019

@ThomasKientz stop acting like a consumer. You can maintain this package just by asking.

@MoOx MoOx changed the title PACKAGE NOT MAINTAINED ANYMORE LOOKING FOR A MAINTAINER Jan 25, 2019
@ThomasKientz
Copy link
Author

@MoOx I would love to but I have never maintained one before ! Please add me, I will see what can I do.

@MoOx
Copy link
Contributor

MoOx commented Jan 25, 2019

Sadly I don’t have the right to add contributors since the package is under webpack .org.
Can @TheLarkInn or @ooflorent help us?
After that I could answer to your technical questions around the workflow to fix and release if necessary.

@alexander-akait
Copy link
Member

@MoOx i can help with permissions and rights

@alexander-akait
Copy link
Member

@ThomasKientz I can give you rights, except npm, we need to work with you for a while to avoid something illegal. I would also like to ask you how much time you can spend? Sometimes developers say what they will be maintain repo, but don't do this.

@ThomasKientz
Copy link
Author

@evilebottnawi I would guess between 1 to 5 hours a week. But I am not sure that this repo needs this amount of time, right now (from what I understand) it needs to merge one pull request to fix an issue affecting a relatively large amont of people. To be clear I have never maintained an open source repo before but I would love to start contributing. I have 3 years of experience in web dev.

@MoOx Would be very nice !

@alexander-akait
Copy link
Member

@ThomasKientz 👍
@MoOx ping me again (just make sure everything is right) and i will add rights to @ThomasKientz

@MoOx
Copy link
Contributor

MoOx commented Jan 25, 2019 via email

@alexander-akait
Copy link
Member

@ThomasKientz invite was sent

@ThomasKientz
Copy link
Author

@evilebottnawi thanks ! Will look into this tomorrow ;)

@MoOx
Copy link
Contributor

MoOx commented Jan 25, 2019 via email

@ThomasKientz
Copy link
Author

@MoOx Can I merge #262 directly or do I need to do something first ?

@MoOx
Copy link
Contributor

MoOx commented Jan 26, 2019

@ThomasKientz if the fix seems ok, and proven by tests this time, you need to

This last step, thanks to npmpub, will create a tag with the version specified in the package.json, push it on github, publish on npm, and create a release on github with the changelog section you added previously.

@ThomasKientz
Copy link
Author

@MoOx #262 seems ok and passed all tests.

But there is a review #262 (review). What is the best practice if I want to modify the pull request accordingly and avoid changes in readme.md ? Do I create a new commit by my side by copying only the desired changes (here : index.js) (thus spoiling credits of the author) ?

Whom do I ask the npm rights ?

@MoOx
Copy link
Contributor

MoOx commented Jan 29, 2019

@ThomasKientz it's good to have additional tests, especially when it come to a bugfix (to ensure it's actually doing something).

For this comment, I guess that's seems to be a normal change from prettier (via pretty-quick) so you can safely merge it this time.

You can ask me npm rights as soon as you are ready to publish (I will just take a look to master, assuming you are going to publish master without any weird trick - to avoid this kind of problem
https://blog.npmjs.org/post/180565383195/details-about-the-event-stream-incident)

@ThomasKientz
Copy link
Author

@MoOx Ready to push to npm ! 02c1e76

@MoOx
Copy link
Contributor

MoOx commented Jan 31, 2019

@ThomasKientz What is your npm login?

@ThomasKientz
Copy link
Author

ThomasKientz commented Feb 1, 2019

@MoOx blaydator

@MoOx
Copy link
Contributor

MoOx commented Feb 4, 2019

@ThomasKientz You have been invited.

@MoOx
Copy link
Contributor

MoOx commented Jul 2, 2019

Reopening as it seems that this package is clearly not maintained at this time.

@MoOx MoOx reopened this Jul 2, 2019
@MoOx MoOx pinned this issue Jul 2, 2019
@ricardogobbosouza
Copy link
Collaborator

@MoOx i can help with this.
This package does not need a lot of time, but attention when needed

@MoOx
Copy link
Contributor

MoOx commented Jul 2, 2019

@evilebottnawi can you help us to add @ricardogobbosouza ?

@alexander-akait
Copy link
Member

Yes

@ricardogobbosouza for releases ping me

@ricardogobbosouza
Copy link
Collaborator

@evilebottnawi
I think we can release,
At least to have support for eslint 6

@alexander-akait
Copy link
Member

@ricardogobbosouza in todo, release will be tomorrow

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants