-
-
Notifications
You must be signed in to change notification settings - Fork 121
LOOKING FOR A MAINTAINER #264
Comments
@ThomasKientz stop acting like a consumer. You can maintain this package just by asking. |
@MoOx I would love to but I have never maintained one before ! Please add me, I will see what can I do. |
Sadly I don’t have the right to add contributors since the package is under webpack .org. |
@MoOx i can help with permissions and rights |
@ThomasKientz I can give you rights, except |
@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 ! |
@ThomasKientz 👍 |
Lgtm.
Will review code change before giving npm rights.
|
@ThomasKientz invite was sent |
@evilebottnawi thanks ! Will look into this tomorrow ;) |
Feel free to continue discussion here if you need anything.
|
@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. |
@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 Whom do I ask the npm rights ? |
@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 |
@ThomasKientz What is your npm login? |
@ThomasKientz You have been invited. |
Reopening as it seems that this package is clearly not maintained at this time. |
@MoOx i can help with this. |
@evilebottnawi can you help us to add @ricardogobbosouza ? |
Yes @ricardogobbosouza for releases ping me |
@evilebottnawi |
@ricardogobbosouza in todo, release will be tomorrow |
From previous maintainer :
https://twitter.com/MoOx/status/1044577532815855616
The text was updated successfully, but these errors were encountered: