Contributors have no shared floor — where should it start? #1612
jpawlowski
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
You closed #1587, #1589 and #1595 for two reasons: shipping a script means standing behind it, and tooling is something each developer should assemble themselves. Both are fair — #1606 takes the first one seriously, documentation only.
What I keep running into is something else. A project with a devcontainer hands every contributor the same starting point, and nobody reads that as being told how to work — it just takes the setup off your plate. vutuv has none, so there is no starting point at all: everyone rebuilds the same few things, on every machine they use, and none of it is visible or reviewable by anyone else.
Two pieces of that floor do exist here:
precommit-before-push.shandscripts/bump_version.exs. I don't think anyone objects to those, because they protect the repository rather than dictate taste. Keeping a fork current feels like the same kind of thing — the work lands on the contributor, but the consequences land here: a version number claimed twice, a diff against a base that is already gone.So where would you draw the line? Is documentation the whole answer, or is there a class of shared tooling you would be willing to carry?
All reactions