That should be read as "if (... And ...)" So I'm not recommending to force
anyone to use a public VCS, I only wanted to express that revisions should
be fine if there is no way to contact upstream devs (no public VCS was just
an example here)
MarLinn
At the very least, we should make sure that each revision is accompanied by an upstream PR if it is for the latest release (or any other still supported branch) and the project is hosted on some VCS service that supports PRs.
Why "and" instead of "if"?
A VCS is certainly a good idea. But a (public) VCS service? Why? Keep in mind that Github and its clones are only one of many options for software management. So why force maintainers to keep up with yet another service if they don't really want or need it? That only reduces the number of willing contributers and forces people into systems that they won't really use, so it wouldn't even solve the problem.
I get the sentiment, but if email is good enough as a last-stage PR-queue for the Linux Kernel, we should allow package maintainers the same. If that makes it harder for them to integrate changes, that's their problem. (But one could always use a format that's easy to parse.)
Bonus: automatic "PR's" via email should be dead-easy to implement and maintain compared to all alternatives.
Cheers, MarLinn
_______________________________________________ Haskell-Cafe mailing list To (un)subscribe, modify options or view archives go to: http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe Only members subscribed via the mailman list are allowed to post.