-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Status of this project? #27
Comments
See #21 for a PR at least fixing the URL in |
The project is still alive, though I'll admit it's not as actively developed as would be ideal. This is the correct repo (I tried using GitLab, but frankly GitHub is better in every way that matters — UI, performance, community etc), and issues and PRs will eventually be moved over here instead.
I do that for some of my other projects, but it's basically just this repo and one for https://buble.surge.sh, so I don't think there's any value in an org. I've added a note to the README on GitLab making it clear that it's an abandoned repo! Thanks |
Could you fix the links in https://buble.surge.sh/guide/ as well? Or at least post a link to the repository so that I can send a PR? |
We could also move over |
I found this Bublé as a light-weight alternative to babel and I like the concept. However I'm very confused about the GitLab and GitHub repos. From the FAQ It looks like you prefer GitLab?
From the status of the GitLab repo I thought the project was dead with the last commit being 9 months old. I only found this repository here by chance. Since there is a newer release here I take it the project is not dead after all and you sometime recently changed your mind about GitLab vs GitHub?
If this repo is the intended future of this project could you add a note to readme of the old repo and update the guide to link here and remove confusing question from FAQ? Or is there some repository for the guide where I could send a PR?
And maybe you should consider creating a buble organization on GH. It's generally a better practice for open-source projects than to have the repo under your personal account.
The text was updated successfully, but these errors were encountered: