I mean at the very least we should have a http://CONTRIBUTING.md and a bot that redirects PRs to the CF docs. But, then we'd need to actually have useful docs about contributing and the development workflow. What we have is a bunch of outdated and contradictory wiki pages.
-
-
Replying to @AndresFreundTec @d_gustafsson and
I've serious doubts about moving to github or somesuch, but I do believe that there's an actual problem here.
2 replies 0 retweets 1 like -
Replying to @AndresFreundTec @d_gustafsson and
Moving? I don't think anyone suggests moving everything to GH (I certainly don't want that). It's rather about making small contributions easier for people who are already there. Or do you think that's problematic too? Why?
1 reply 0 retweets 0 likes -
Replying to @fuzzycz @d_gustafsson and
Even if it's just a partial move, it'll split review. And I think it's extremely unlikely that we'll manage to very clearly separate what's allowed to happen in github PRs, and what on the list.
2 replies 0 retweets 0 likes -
Replying to @AndresFreundTec @fuzzycz and
I have to agree. I think that having an expedited review process for small changes (definition TBD) makes sense, but having multiple streams into the codebase would be a major headache.
1 reply 0 retweets 0 likes -
Replying to @Xof @AndresFreundTec and
Obviously, it's not without risks. I agree changes that are not obviously correct should be funneled to the list, and committers / reviewers should not be expected to watch GH. If there are volunteers willing to curate the GH queue, why not to give it a try?
1 reply 0 retweets 0 likes -
Outside of typo-fixes etc there's just about no obviously correct contribution by first timers. It's possible that those would suddenly appear, but I doubt it. And if there's any discussion, how would we guarantee it's archived somewhere under our control?
1 reply 0 retweets 2 likes -
Replying to @AndresFreundTec @fuzzycz and
And why are we discouraging even the small drive-by patches by making the process unnecessary complicated for people not familiar with the PostgreSQL development process?
2 replies 0 retweets 0 likes -
Replying to @ascherbaum @AndresFreundTec and
There's an unspoken premise in the OP's original essay, which is, "A project benefits from making it very easy to submit code contributions." Most FOSS maintainers would agree that making it easy to submit PRs has not always been a good thing.
1 reply 0 retweets 0 likes -
Replying to @Xof @ascherbaum and
Sure, it may very well turn out to be useless. But we'll never know unless we give it a try.
1 reply 0 retweets 0 likes
Well, I could possibly be convinced that it's a worthwhile thing to try. But I'd really like to see a proposal that actually deals with how the process would deal with the issues I point out nearby.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.