Help getting to 1.0

[benmccann]

Describe the problem

We're actively working towards getting SvelteKit 1.0 out! But there's a lot to do. Just reviewing incoming PRs, prioritizing issues for 1.0, suggesting solutions for important issues, etc. is nearly a fulltime job.

We've knocked out over 500 issues that were on the 1.0 milestone, but there's still a couple dozen left

Describe the proposed solution

If you'd like to help, please consider working on any of these issues:

https://github.com/sveltejs/kit/issues?q=is%3Aopen+is%3Aissue+milestone%3A1.0

The most straightforward items have been labeled with "help wanted"

For those, or any other tickets, we're happy to help get to a consensus on what the solution should be if it's not clear. Feel free to ping the ticket or find me on Discord under this same username. Take a look at the contributor's guide to get started, but feel free to ask if additional pointers would be helpful

Alternatives considered

The maintainers do everything and 1.0 never happens 😄

Importance

blocking an upgrade

Additional Information

No response

[krisalcordo]

How can a noob like me contribute?

[denny64]

Is there a backlog of things to do and their priorities? Happy to contribute wherever I can 😊

[benmccann]

How can a noob like me contribute?

Helping to answer people's questions on Discord or StackOverflow can be a good way to contribute as a beginner since you'll often learn a lot in the process

Is there a backlog of things to do and their priorities?

https://github.com/sveltejs/kit/issues basically. A few ways to find important things to work on:

• filter by the 1.0 milestone
• filter by p1 label
• sort by thumbs up

[joglomedia]

Willing to help, but I am still n00b 😁

[lamualfa]

For anyone who feel noob, there are many other things you can do.

For example like give a little donation to Svelte team in https://opencollective.com/svelte. Whatever donation you give, it will help the team to maintain many awesome Svelte projects now and future 🎉.

❤️❤️❤️

---

Edit

Oh wow!

Do you maintainers do not get paid at all 🥺? They only use 86 dollars of all incoming donations. What?! that kind of money is just enough to pay for the server or some cups of coffe and snacks.

From Svelte Open Collective

---

I am indebted to you all when I succeed later 🙏. Thanks for all your contributions.

[antony]

n00bs - we all benefit from writing tests. Good tests are always welcome.

If you think you are too n00b to contribute (you're not), then add tests, or write tests for the feature you want to add, before you add it! Start small, and learn the codebase that way.

That being said, reviewing existing contributions, investigating and testing bugs, and helping us housekeep issues and PRs is extremely valuable right now. This is where a lot of our current time is spent.

If you need help, or want to discuss how to contribute, it's better discussed in the svelte kit contributing channel on discord. It's much easier to get a realtime answer there and chat to us and other contributors directly.

We always welcome donations but time is the most valuable thing. We'd love your help no matter how small a contribution you think you may be making.

[rchrdnsh]

I contributed on open collective XD

[gg187on]

I'm thinking about writing tests and maybe fix some issue on millestone. As n00b I would like to know where to start and what is best way to start contributing. I see repo is missing "Good first issue" label, so a lot of new users/contributors don't know what are good issues to work on.

[benmccann]

From the issue description:

The most straightforward items have been labeled with "help wanted"

[lordvcs]

Can I suggest something like what nextjs does for their issues, on visiting the nextjs issues section you are greeted with this header section,

Clicking on the we've collected some good first issues for you takes you to the list of issues which have been tagged as good first issue. This can potentially bring in a lot of contributors becuase getting started is the hard part, especially for so-called noobs(like me).

[ghost]

Congrats on almost reaching v1! 🎉 I would also recommend changing the warning on the docs as follows (or I can submit a PR for the edit):

- SvelteKit is in early development, and some things may change before we hit version 1.0. . . .
+ SvelteKit is in its release candidate phase. . . .

[benmccann]

I'm going to close this as we don't have all that many issues left anymore