And of course, most drive-by developers are too lazy to bother posting any PRs at all, even if their fixes are awesome. I obviously don't know why, but I strongly suspect it is because they see that previous PR's rarely gets merged and completed, nor closed if they are not accepted. If you look at the Network for this repo, you will see it is very fragmented with loads of people making improvements and (in many cases) rather important such, but they never even see the daylight of a PR here. That said, to keep operations moving, I suggest we try to minimize trivial PR's to the favored convenience of the maintainers ) to do these 3 click operations, rather than having people have to first fork the repo, then fix the files then post a PR (preferably with descriptive text), then wait for feedback, then wait for merge. I'm a great fan 4 space TABs, but nobody (incl Google) else is, so they'd hate reading my stuff in their generally misconfigured text editors. If you would be happy with that, we can just move the Wiki entry (from above) into a file. Since most users are reading and forking this stuff on Github or various other markup supported likes, that would save a lot of effort in trying to pretty format text files, in whatever people find convenient in terms of TABs, markups and col lengths etc. However, I suggest to use *.md markups instead of these old ugly.
0 Comments
Leave a Reply. |