Closed rootwork closed 2 years ago
Meant to add on number 5 - one of the reasons I think a contributing document would be useful is the DCO test, which most people seem not to see (or know what to do about) when they first submit a PR.
0.1
or something else?Gentlemen,
I agree with 👍🏼 2 ~ 5.
As far as the first (1) and last (6) points go, I'm not quite sure how they would work since we're not an organization. We're merely 3 guys plus other individuals who volunteer to work on an open source theme. That said, I get the sense that the first point is more approachable.
OK, I'll work on PRs for 3-5, and see if there are any good examples of setting up a planning section of discussions for item 1.
For item 6, I don't know what funding would look like for a group of individuals; maybe that's too much to try to navigate.
On 2: I think it might depend on how "complete" you think the theme is @chipzoller. Is it what you originally envisioned, and now we're just adding new features? Then that sounds like 1.0.0
(at least). But if there are still big parts left to do from your original plan, then yes I'd say 0.x.0
, and I guess making x
anything other than 1
would probably be confusing. Then again, we all use Hugo which has been around for 9 years and still doesn't have a 1.x
release, so... 🤷🏽
@chipzoller @onweru When you get a chance, wanted your feedback on some project ideas. I can do PRs, but I don't want to invest in work before knowing if these seem like good ideas for Hugo Clarity.
FUNDING.yml
file. You can offer tiers and/or rewards, like mentions in the readme. If that's not a path you want to go down, though, that's fine.👍🏽 / 👎🏽 / ❓ on any of these?