testing-library/preact-testing-library

Join testing-library org?

kentcdodds opened this issue Β· 13 comments

Hi πŸ‘‹ would you like to join @testing-library and move this over to that org? May help make this more official and you could also rename the module to @testing-library/preact if you're interested. Let me know!

As a user of this project, I'm hugely in favour of that -- partly from an ease-of-discovery point of view, but also because I think it would encourage more independent contributions. Thanks to @antsmartian for everything so far, in any case!

Ping. Would you like some help @antsmartian?

@kentcdodds Sorry, was completely busy with my works. I will be moving this by next week for sure!

What's the status on this? Any update @antsmartian ? Thanks!

@kentcdodds I tried to transfer this project as it is to testing-library. But I got the following error:
You don’t have the permission to create repositories on testing-library. Not sure, what is the mistake here.

@kentcdodds I have given you the collaborator access to this repo. I believe, now you should be able to transfer this to testing-library. I would love to be part of testing-library as well, so that I can look into issues anything related to preact-testing-library. Hope you are ok with that :)

Just added you. You should be able to transfer it

@kentcdodds Thanks. Transferred. (Sorry for making it so long, given the fact its so simple). Happy to be part of @testing-library πŸŽ‰ πŸŽ‰ πŸŽ‰ πŸŽ‰

Great! Would you like to publish preact-testing-library as @testing-library/preact? If so, I'll add you to the npm org and you can follow what I did for my libraries.

@kentcdodds I would be happy to. Can you please add me to the npm org, then will follow up on the instructions and do a npm publish.

I'd prefer to see a little more movement on #19 before we start publishing to the @testing-library scope. Also, I think it would be wise to have Rahim join as a co-maintainer of the package as it seems like you're not able to be as responsive as some of the community would like.

@kentcdodds Totally agree. I would close that thread with the recent changes of Rahim. Then we can take this forward.

Closing this since we've already moved ahead in #19.