On 18 Feb 2016 16:19, Sahil Shekhawat wrote: > I just joined this mailing list and am interested in contributing but I am > wondering why we are still submitting patches on mailing lists and not > shift to Github already? Is there any specific reason to not do that? > I am asking this since I am new and couldn't see what issues are there or > read code review discussion on PRs.
low level projects often have developers that eschew web-only or web-centric flows like github. today, in order to contribute to strace, all you need is git and command line tools. if we did things via github, now you'd need a web browser that supports JS. so instead of forking strace into your own github acct, pushing changes there, and then sending a PR, you use `git send-email`. typically the flow of patches here is low enough that if your changes don't get merged soonish, you'll need to ping/resend anyways as the code changes underneath you. of course it's hard to say whether we aren't getting more contributors because we aren't lowering the barrier via GH, or just because strace is a fairly low-level esoteric tool. it's not like we've seen a large # of people complaining on the list so far. -mike
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________ Strace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/strace-devel
