-
Notifications
You must be signed in to change notification settings - Fork 71
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
Help Wanted / Making This A Community Effort #206
Comments
@dummdidumm Thanks for opening the project again. I believe a good starting point would be to evaluate and add labels to all of the open issues. For example, a lot of issues appear to be questions (e.g., #196). It might be best to close those issues and open up a GitHub Discussions forum. That would be my personal preference anyway. Some other issues appear to have been resolved or contain stale/incomplete information (e.g., #187, #115). Let me know if you want me to start looking through these. |
Doing issue triaging is greatly appreciated! Just comment on the issues and I'll add labels and/or close them. Not sure about closing "question" issues yet so I'll leave them open for now. |
Sounds good. I'll start going through some issues and leaving comments over the coming days. |
I'd be happy to help test/review any PRs here. |
Great to hear this. I'm new in this codebase, but I am interested to help writing/test/review any PRs here. |
The Svelte team is busy working on SvelteKit and Svelte itself, and unfortunately we didn't have much time looking into
svelte-loader
. This very likely won't change in the foreseeable future, so we ask you, the community, to help us out maintain this project. My goal is to remain in a kind of organizer role, merging PRs that have been opened and approved/cross tested by community members and release new versions. If you would like to contribute, feel free to express your interest here, so other community members opening PRs can ping you for reviews etc.The text was updated successfully, but these errors were encountered: