It would be nice to add a dictionary of acronyms or symbols frequently used in comments

[agcolom]

e.g. LGTM, :+1: , \o/, etc...

[ashleygwilliams]

WIP: work in progress WFM: works for me +1: agree/support r?: review please r+: reviewed + approved RTFM: read the fucking manual <-- never say this LGTM: looks good to me \o/: person raising hands in happy excitement

[agcolom]

Should we also add those used on IRC as well? (e.g. IMO: in my opinion, IMHO: in my humble opinion , AFAIK: As far as I know, AFK: Away from keyboard BRB: be right back, BBL: be back later, JK just kidding, STFW search the f***ing web <-- never say this MIA: Missing in action any others??

[jzaefferer]

CLA: Contributor License Agreement PR: Pull Request

xxx: Issue or pull request reference

[gibson042]

xxx: Issue or pull request reference

gh-xxx, trac-xxx: tracker-specific issue reference (preferred over #xxx)

[danielle-b]

FWIW: For What It's Worth -1: Disagree :point_up: Previous comment CLDR: Common Locale Data Repository :boom: Denotes that something is important SCM: Source Code Management Octopus: To merge more than two branches NaN: Not a Number :see_no_evil: See no evil WYSIWYG: What You See Is What You Get IRC: Internet Relay Chat (chat client) IIRC: If I Recall/Remember Correctly IDR: I Don't Remember ICR: I Can't Rememeber IIUC: If I Understand Correctly IDK: I Don't Know SUIT: Simple User Interface Toolkit npm: package manager for Javascript GUI: Graphical User Interface BEM: Block, Element, Modify(naming convention for classes in HTML and CSS) API: Application Program Interface ( set of tool and protocols used for building software applications) ES6: ECMAScript, a language specification standard that defines the standard for Javascript implementation

[kborchers]

IANAL: I Am Not A Lawyer (mostly used when discussing licenses, copyrights, etc)

[gibson042]

bikeshedding: giving disproportionate weight to trivial issues (ref) yak shaving: seemingly pointless activities which are necessary (often recursively) to accomplish an original goal (ref)

[aperala]

np: no problem EOD: End of Day

[jaspermdegroot]

tl;dr: too long, didn't read

[gibson042]

http://www.itexico.com/blog/bid/99765/Software-Development-KISS-YAGNI-DRY-3-Principles-to-simplify-your-life

KISS: Keep It Simple, Stupid ("simplicity should be a key goal in design and unnecessary complexity should be avoided") YAGNI: You Aren't Gonna Need It ("always implement things when you actually need them, never when you just foresee that you need them") DRY: Don't Repeat Yourself

[tienit150198]

https://www.freecodecamp.org/news/what-do-cryptic-github-comments-mean-9c1912bcc0a4/

ACK — acknowledgement, i.e. agreed/accepted change NACK/NAK —negative acknowledgement, i.e. disagree with change and/or concept RFC — request for comments, i.e. I think this is a good idea, lets discuss

example: Concept ACK — agree with the concept, but haven’t reviewed the changes utACK (aka. Untested ACK) — agree with the changes and reviewed them, but didn’t test Tested ACK — agree with the changes, reviewed and tested

[shwetankdeshmukh]

This discussion from the 2015 jQuery Developer Summit raises some really important points about improving the healthcare developer experience. As someone working in tech, I can relate to the challenges of managing open-source projects and ensuring that they remain accessible to both new and experienced developers. The suggestions around documentation and better onboarding processes are crucial for maintaining engagement and fostering community growth. It’s great to see these topics being addressed in such a collaborative environment."

More info

https://www.osplabs.com/custom-healthcare-software-development/