Closed ArmorDarks closed 6 years ago
@yaniswang there are likely members of this community that can assist as collaborators.
@yaniswang If you do not plan to maintain this project that's fine, but please do not leave the community hanging, we can help with the maintenance as many of us depend on this package.
Absolutely no. ^_^
Very disappointing. Especially seeing that VSCode was looking to recommend this project. There's so many open PRs too, lots of people interested in helping. At the least, it would be nice to see the existing work migrated to another project that enables more community participation.
Some alternatives can be found here
@AndrewCraswell Just needs someone willing to take it on. =]
I know the issue is old, but I just wanted to tell you that I sent an email to the owner of the repo to ask if he could add me as a collaborator or give the ownership of the project. I'm willing to help the project to go further and work as everyone is expecting! 😉
Hi everyone!
After few tentatives, I didn't receive any response from Yanis... I'm thinking in migrating the source code from HTMLHint to another repo with a new name. I know all the depend projects that are based on HTMLHint but I think we can't wait for more time if we want to move forward.
In opposition of the current repo, I think the project should contain various administrators to avoid being just one person in maintaining the project (we never know what can happen to one person).
Thanks to my current projects, I suppose that I can give a big visibility to the project and have people involved to help migrating and optimizing the current project.
What do you think? I created a doodle (https://doodle.com/poll/hn7gh4h56estzs8w) with few possible names, don't hesitate to suggest others. I hope to start working on a next version soon!
First of all, it could stay with HTMLHint and become a fork of this repo. Then you can ask at npm if the old package can be replaced: https://docs.npmjs.com/misc/disputes
I would be very interested in helping to build a new HTMLHint or HTMLLint (hobby time) Whereby a Hinter only provides annotations and a Linter also fixes and offers more configuration. I would not call it HTML5, because HTML could be synonymous for HTML4 XHTML or HTML6, why directly limiting?
In a new Repo we can create new Proposals and build up from stretch maybe
I totally agree with having a "Linter" and not just a "Hinter". About HTML5, I thought about that too... Let see what other people think about.
Regarding the fact to build up from scratch, I would rather to start with something existing and updating it because it could take less time I think... but I may be wrong.
Ok, I reviewed GitHub a bit and found an existing Linter https://github.com/htmllint/htmllint I do not know this linter and have not tried it
I think we now have 3 options:
In all 3 options I would like to rewrite it in TypeScript because I think that helps to find bugs and it is easier to maintain in the long term
@ArmorDarks I think the goal is not going too far in a first time, but upgrading the existing. So the option 2 seems the most reasonable. And regarding TypeScript, even I love it too, plain JavaScript is the best in a first time, small steps for a biggest impact.
Agreed Let me know when you start, so that I can help
Seems like no one mentioned markuplint so I guess I'll just leave it here in case it's helpful.
@hacknug, I evaluated markuplint for my angular application and it didn't go well when I plugged it in. It did not seem to care for custom angular components, and had some indecipherable error messages, even with translation services, and it had a number of seemingly false positives for overlapping tags.
@vort3xxx @hacknug I experienced the same thing markuplint seems not to be ready in any way, it is heavily under construction
Hi @everyone!
In 8 days, if we don't have any news from @yaniswang, I'll be added to the list of contributors for HTMLHint! 🍾
It's going to be a lot of work, going through all bugs and PR... But I still believe, for now, this is the best thing to do. Moving to something else is probably too soon. First, reduce the among of issues, after, we can all decide the best direction to take!
@thedaviddias have you talked to Github?
I'm sorry, i have no time for it.
Who can take over HTMLHint?
Hi @yaniswang - great to hear from you! I'd love to be a contributor. I've been a HTMLHint user for many years and I'm very active on GitHub and manage and contribute to many open source projects.
Who can be the owner of the project?
I'd be very happy to be the project owner, but I'm fine with @thedaviddias being project owner if I can be on the projects team. :-)
Welcome @yaniswang! I would vote for @thedaviddias as well given his enthusiasm and action thus far.
Hey @yaniswang! Awesome to hear from you, NPM and I were sending you various emails since a month. You can put me as owner of the project, and I'll add people that have been around to help in correcting bugs and issues we have today. @coliff and @tdmalone, thanks for the support, I'm eager to work with you on that project!
Probably last message on this issue, @yaniswang just transferred to me the ownership of the project. I'm going to create a Gitter channel for us to be able to exchange and update "Projects" on Github to see what needs to be done, prioritize etc... @ArmorDarks I think that you can close this ticket 🤗
@thedaviddias please give me your npm account
This is my NPM account: https://www.npmjs.com/~thedaviddias
Done
Do you have godaddy account? i transfer the domain htmlhint.com to you
I don't have but you can eventually send me by email the code for the transfer I think... (my email: thedaviddias@gmail.com)
i had send you the transefer code from email.
this issue can be closed
Glad to see so much love here and that HTMLHint finally moving somewhere! 👍
Hi @yaniswang!
Thanks for that library, I think it solved a lot of issue for many people.
But for now it seems to be mostly abandoned, with lots of unclosed PRs and issues, outdated dependencies.
Is HTMLHint dead?