-
Notifications
You must be signed in to change notification settings - Fork 298
Let users know of module rename #929
Comments
I am working on this today. |
Ok so, I made a little script to convert the data from the snapshot into a list of repos that still depend on the old version. It also contains info about which github user we consider to be the maintainer for the repo as well as the paths to the Caveats:
@mikeal @pkafei do you have any bandwidth to help turn this data into PRs or maybe just mention all these people in a comment? I feel the former might be more effective though 😅. Here's the current data:
|
I think you can also query release authors, which might give a more up to date representation of who is currently managing the repos, but that may end up being unnecessary due to the age of the projects. |
Folks, any updates here? |
I may be interrupting here a bit(it seems to be a core dev discussion)...But do you just need to mention the maintainers of the repos in a comment here? (for informing them about the name change?) |
@vasa-develop you are welcome to participate and help! The main question here is how to do this in a way that is effective and non necessarily intrusive. We can do this by going from the less loud to the more direct, creating a timeline in which we try (by order)
There are still ~8000 downloads weekly for the old module name: |
I just reviewed this again today. We still have 199 dependents but the majority of them haven't been updated for over a year and have <20 downloads/week. One of the few deps that actually has some usage is 20 (downloads) x 199 (dependents) = 3,980 Which is basically the current weekly downloads for At this point I feel it'll be low value to spend any more time on this so I'm going to close it. @daviddias if you feel differently then please re-open and I'll get it sorted. |
Following up on #897 (comment), we need to let users know of the module rename.
@mikeal proposed that a PR is submitted to each repo to update the name on the package.json. @mikeal, @pkafei is this something you can handle sometime soon?
The text was updated successfully, but these errors were encountered: