Re:Swift open source – let the revolution begin
by elwell on Wednesday December 09, 2015 @07:16PM
(#10707916)
Yeah, it's looks good on your GitHub profile to be a 'contributor' to Swift.
Re:Swift open source – let the revolution begin
by edgyswingset on Wednesday December 09, 2015 @07:21PM
(#10707957)
This brings up an interesting problem to solve:
How to tell if something is a "real" contributor rather than someone who sends the occasional spelling fix. I imagine recruiters would be interested in some way to easily tell this.
Re:Swift open source – let the revolution begin
by mikeash on Wednesday December 09, 2015 @08:45PM
(#10708298)
Is it too much to ask that they actually look at the content of the pull requests?
Re:Swift open source – let the revolution begin
by TheDrizzle43 on Wednesday December 09, 2015 @07:26PM
(#10707978)
All they have to do is ask them in the phone screen "So what did you contribute to Swift?"
Re:Swift open source – let the revolution begin
by dvcrn on Thursday December 10, 2015 @05:37AM
(#10709946)
"I analysed the swift codebase for character sequence problems and actively contributed in reducing these. My contributions were responsible for eliminating hundreds of possible issue reports to the project."
Re:Swift open source – let the revolution begin
by krig on Thursday December 10, 2015 @02:43AM
(#10709407)
How is that a problem? If you really want to know the details, they are a single git query away.
Re:Swift open source – let the revolution begin
by gmac on Thursday December 10, 2015 @09:06AM
(#10710616)
My suspicion is that someone who's smart, engaged and motivated enough to have figured out a way to be able to say they're a Swift contributor by fixing typos is probably in the top 10% of candidates anyway.
Re:Swift open source – let the revolution begin
by feelix on Thursday December 10, 2015 @07:26AM
(#10710279)
One solution would be to implement upvotes/downvotes on github pull requests.
Re:Swift open source – let the revolution begin
by bechampion on Thursday December 10, 2015 @04:44AM
(#10709773)
good point , but it applied to every open source project too
The people contributing those fixes are doing so because they want to contribute, and typo fixes are very easy to be certain about that it's an improvement (without a chance of introducing regressions, etc.).
Of course, as the easy-to-fix problems are eliminated, focus will shift to finding more meaningful ways to make improvements, or just using the language which has fewer problems as a result.