On 11/30/2016 05:17 PM, Rich Freeman wrote:
On Wed, Nov 30, 2016 at 4:23 PM, Andrey Utkin <andrey_ut...@fastmail.com> wrote:

I beg affiliated Gentoo developers to stay sane and be thinking not just
about numbers of your commits, but also about community spirit and
relationships. Of course inexperienced contributor gets things not right
first. In such cases, great maintainers fix that and retain original
authorship; good maintainers request for changes and resubmission.


I'd have to hunt for where it is written down, but it can't be said
enough.  We should definitely be trying to acknowledge the
contributions of others whenever possible.  It is really the only
recognition a lot of "external" contributors get, and it is the least
we can do.  This isn't about copyright or policy or anything like
that, but just a nice thing to do, and there is no "threshold" that
external contributors need to make.

I wouldn't ascribe to malice what is probably just the result of
oversight, but it is a good reminder whatever the case may be...


As an old 'C' hack, 99.999% of what I've written is hardware centric and not publically published. A good 95% of it is covered by NDAs and ownership/rights as transferred codes. Often I can only speak to potential negotiators of opportunity, in a generic way about a variety of codes and technologies.

Many of today's potential employers want to see the open source contributions of potential employees/contractors; I get that. So it is quintessentially important that these sorts of contributors have a list of easy to review works and contributions to show potential employers. Perhaps their own overlay where their works and contributions are duplicated for easy viewing by a potential employer? (I'm certainly not a git-architect) but there is a valid need and this documentation trail would only serve to attract more potential to gentoo's projects.

Me, I have a lab full of home-made prototypes and who's who list of EE/CS developers and leaders that I can tap, if I feel the need. I can talk deeply about chipsets and the sorry codes developed by the OEMs (sorry_moto) which were directly embedded into compromise-able routers (like cisco) and such juicy tidbits. Or, I have deeply secretive stories (antidotes) of stories behind the story, than can curl the ear-hairs of most CIO/CT0. But for the youthful devs, it would be very cool if a mechanism/system was deployed at Gentoo for those aspiring devs to enhance their resumes, kinda like a personally attributable changelog or such.

Story telling comes with age and wisdom..... knowing when to give the credit to another......


Reply via email to