WebReflection / WebReflection/linkedom
Anyone willing to help this project forward?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 2.1k
- Forks
- 104
- PR merge metrics
- No merged PRs in 30d
Description
I think this project works awesomely for anything I need it to do, but I am afraid I am a full time contractor and, before that, a full time dad of a 21 months old child that leaves me pretty much zero extra time to deal with bugs, PRs reviews, publish, release related things, and so on ... I also don't want to abandon this project because I think it's pretty cool and robust enough for SSR related tasks, but it's clear that many keep trying to use this to test things or pretend this project is like JSDOM and behave like a browser ... I have two options:
- make this project "locked" for its own users (no issues, no PRs, nothing, I just work on it when and if I have time)
- find other maintainers that just stick with the contribution docs and don't waste time with stuff that ain't needed (like change linter rules, make everything
.tsor anything that is not moving really the project further, just churn no current issue needs)
As summary: is anyone willing to jump in? All I can do is to guarantee that any question around any current decision can be answered, while maintainers can help this project forward while I do completely different things in my daily job which has nothing to do with LinkeDOM improvements ... what do you think? Any volunteer?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
This is a project-maintenance and governance request, not a scoped code change. Start by reviewing the contribution docs and current open issues, then determine whether you can take on maintainer responsibilities. Done means the project has an agreed maintenance plan and someone follows through.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100