├── .gitignore
├── _config.yml
├── assets
└── css
│ └── style.scss
├── .github
├── pull_request_template.md
└── workflows
│ ├── markdown-from-json.yml
│ └── pages.yml
├── data
├── design-patterns.json
├── organizations.json
├── stacks.json
├── chat-acronyms.json
└── acronyms.json
├── CONTRIBUTING.md
├── CODE_OF_CONDUCT.md
├── LICENSE
└── README.md
/.gitignore:
--------------------------------------------------------------------------------
1 | .idea
--------------------------------------------------------------------------------
/_config.yml:
--------------------------------------------------------------------------------
1 | theme: jekyll-theme-cayman
2 |
--------------------------------------------------------------------------------
/assets/css/style.scss:
--------------------------------------------------------------------------------
1 | ---
2 | ---
3 |
4 | @import "{{ site.theme }}";
5 |
6 | .page-header {
7 | background-color: #734074;
8 | background-image: radial-gradient(ellipse farthest-side at 50% 180%, #734074 0%, #3a2363 140%);
9 | }
10 |
11 | .main-content h1, .main-content h2, .main-content h3, .main-content h4, .main-content h5, .main-content h6 {
12 | color: #3a2363;
13 | }
14 |
--------------------------------------------------------------------------------
/.github/pull_request_template.md:
--------------------------------------------------------------------------------
1 | ## If you want to add or update an acronym
2 |
3 | Keep in mind that the [readme.md] is generated. It is useless to edit it directly.
4 | If you want to add or update an acronym, edit the correct file in the [data] folder
5 | (e.g. [acronyms.json])
6 |
7 | ## Checklist before merging
8 |
9 | - [ ] The title says what this PR do
10 | - [ ] The description includes an issue ticket number if any
11 | - [ ] Only a `json` is changed if you want to add or update an acronym
12 |
13 | [readme.md]: https://github.com/d-edge/foss-acronyms/blob/main/README.md
14 | [data]: https://github.com/d-edge/foss-acronyms/tree/main/data
15 | [acronyms.json]: https://github.com/d-edge/foss-acronyms/blob/main/data/acronyms.json
16 |
--------------------------------------------------------------------------------
/data/design-patterns.json:
--------------------------------------------------------------------------------
1 | [
2 | {
3 | "Abbreviation": "MVC",
4 | "Definition": "Model View Controller",
5 | "Usage": "A commonly used software design architecture based around the Model (data), the View (user interface), and the Controller (logic to handle requests).",
6 | "Example": "Medium"
7 | },
8 | {
9 | "Abbreviation": "MVVM",
10 | "Definition": "Model View ViewModel",
11 | "Usage": "A front-end software design architecture based around the Model (data), the View (user interface), and the ViewModel (logic that handles view data and interactions).",
12 | "Example": "Knockout MVVM Explanation"
13 | }
14 | ]
--------------------------------------------------------------------------------
/.github/workflows/markdown-from-json.yml:
--------------------------------------------------------------------------------
1 | name: markdown-from-json
2 |
3 | on: [push]
4 |
5 | jobs:
6 | auto-update-readme:
7 | runs-on: ubuntu-latest
8 | steps:
9 | - name: Checkout
10 | uses: actions/checkout@v2
11 | - name: Order objects by a given property from a json file
12 | uses: aloisdg/order-by-json@v0.3
13 | with:
14 | pattern: './data/*.json'
15 | property: 'Abbreviation'
16 |
17 | - name: setup git config
18 | run: |
19 | if [ $(git diff | wc -l) -gt 0 ]; then
20 | git config user.name "d-edge automation"
21 | git config user.email "<>"
22 | git add ./data/*.json
23 | git commit -m "Order JSON"
24 | git push origin main
25 | else
26 | echo Order is respected
27 | fi
28 |
29 | - name: Markdown autodocs
30 | uses: dineshsonachalam/markdown-autodocs@v1.0.3
31 | with:
32 | # Optional output file paths, defaults to '[./README.md]'.
33 | output_file_paths: '[./README.md]'
34 |
35 | # Categories to automatically sync or transform its contents in the markdown files.
36 | # Defaults to '[code-block,json-to-html-table,workflow-artifact-table]'
37 | categories: 'json-to-html-table'
38 |
--------------------------------------------------------------------------------
/.github/workflows/pages.yml:
--------------------------------------------------------------------------------
1 | # Sample workflow for building and deploying a Jekyll site to GitHub Pages
2 | name: Deploy Jekyll with GitHub Pages dependencies preinstalled
3 |
4 | on:
5 | workflow_run:
6 | workflows: ["markdown-from-json"]
7 | types:
8 | - completed
9 |
10 | # Allows you to run this workflow manually from the Actions tab
11 | workflow_dispatch:
12 |
13 | # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
14 | permissions:
15 | contents: read
16 | pages: write
17 | id-token: write
18 |
19 | # Allow one concurrent deployment
20 | concurrency:
21 | group: "pages"
22 | cancel-in-progress: true
23 |
24 | jobs:
25 | # Build job
26 | build:
27 | runs-on: ubuntu-latest
28 | if: ${{ github.event.workflow_run.conclusion == 'success' }}
29 | steps:
30 | - name: Checkout
31 | uses: actions/checkout@v3
32 | - name: Setup Pages
33 | uses: actions/configure-pages@v2
34 | - name: Build with Jekyll
35 | uses: actions/jekyll-build-pages@v1
36 | with:
37 | source: ./
38 | destination: ./_site
39 | - name: Upload artifact
40 | uses: actions/upload-pages-artifact@v1
41 |
42 | # Deployment job
43 | deploy:
44 | environment:
45 | name: github-pages
46 | url: ${{ steps.deployment.outputs.page_url }}
47 | runs-on: ubuntu-latest
48 | needs: build
49 | steps:
50 | - name: Deploy to GitHub Pages
51 | id: deployment
52 | uses: actions/deploy-pages@v1
53 |
--------------------------------------------------------------------------------
/data/organizations.json:
--------------------------------------------------------------------------------
1 | [
2 | {
3 | "Abbreviation": "AWS",
4 | "Meaning": "Amazon web Services",
5 | "URL": "https://aws.amazon.com/",
6 | "What they do": "Amazon Web Services offers reliable, scalable, and inexpensive cloud computing services."
7 | },
8 | {
9 | "Abbreviation": "FSF",
10 | "Meaning": "Free Software Foundation",
11 | "URL": "https://www.fsf.org",
12 | "What they do": "Oversee a number of open source organizations"
13 | },
14 | {
15 | "Abbreviation": "GH",
16 | "Meaning": "GitHub",
17 | "URL": "https://github.com",
18 | "What they do": "Source code host, owned by Microsoft"
19 | },
20 | {
21 | "Abbreviation": "GNU",
22 | "Meaning": "Collection of free software, a license",
23 | "URL": "https://gnu.org",
24 | "What they do": "program of FSF, develops many linux tools and a commonly used license"
25 | },
26 | {
27 | "Abbreviation": "MS",
28 | "Meaning": "Microsoft",
29 | "URL": "https://microsoft.com",
30 | "What they do": "Makers of windows, azure, vscode, and other tools that might be relevent to developers"
31 | },
32 | {
33 | "Abbreviation": "OSI",
34 | "Meaning": "Open Source Initiative",
35 | "URL": "https://opensource.org",
36 | "What they do": "Defining 'Open Source'"
37 | },
38 | {
39 | "Abbreviation": "SO",
40 | "Meaning": "StackOverflow",
41 | "URL": "https://stackoverflow.com",
42 | "What they do": "Popular question and answer website"
43 | },
44 | {
45 | "Abbreviation": "YT",
46 | "Meaning": "YouTube",
47 | "URL": "https://www.youtube.com/",
48 | "What they do": "YouTube is online video sharing and social media platform"
49 | }
50 | ]
--------------------------------------------------------------------------------
/data/stacks.json:
--------------------------------------------------------------------------------
1 | [
2 | {
3 | "Abbreviation": "EFK",
4 | "Definition": "Elasticsearch, Fluentd, and Kibana",
5 | "Example": "How To Set Up an Elasticsearch, Fluentd and Kibana (EFK) Logging Stack on Kubernetes"
6 | },
7 | {
8 | "Abbreviation": "ELK",
9 | "Definition": "Elasticsearch, Logstash, and Kibana",
10 | "Example": "What is the ELK Stack?"
11 | },
12 | {
13 | "Abbreviation": "LAMP",
14 | "Definition": "Linux, Apache, MySQL, PHP (Perl or Python)",
15 | "Example": "IBM Cloud, Wikipedia"
16 | },
17 | {
18 | "Abbreviation": "LEMP",
19 | "Definition": "Linux, Nginx Server, MySQL, PHP (Perl or Python)",
20 | "Example": ""
21 | },
22 | {
23 | "Abbreviation": "MEAN",
24 | "Definition": "MongoDB, Express.js, Angular.js, Node.js",
25 | "Example": ""
26 | },
27 | {
28 | "Abbreviation": "MERN",
29 | "Definition": "MongoDB, Express.js, React.js, Node.js",
30 | "Example": ""
31 | },
32 | {
33 | "Abbreviation": "MEVN",
34 | "Definition": "MongoDB, Express.js, Vue.js, Node.js",
35 | "Example": "What is MEVN stack?"
36 | },
37 | {
38 | "Abbreviation": "SAFE",
39 | "Definition": "Suave (or Saturn), Azure, Fable, Elmish",
40 | "Example": "/r/fsharp"
41 | }
42 | ]
--------------------------------------------------------------------------------
/data/chat-acronyms.json:
--------------------------------------------------------------------------------
1 | [
2 | {
3 | "Abbreviation": "AFK",
4 | "Definition": "Away From Keyboard"
5 | },
6 | {
7 | "Abbreviation": "BRB",
8 | "Definition": "Be Right Back"
9 | },
10 | {
11 | "Abbreviation": "CMIIW",
12 | "Definition": "Correct me if i'm wrong"
13 | },
14 | {
15 | "Abbreviation": "IKR",
16 | "Definition": "I know, right"
17 | },
18 | {
19 | "Abbreviation": "ILY",
20 | "Definition": "I love you"
21 | },
22 | {
23 | "Abbreviation": "IRL",
24 | "Definition": "In Real Life"
25 | },
26 | {
27 | "Abbreviation": "IYKYK",
28 | "Definition": "If You Know You Know"
29 | },
30 | {
31 | "Abbreviation": "LFG",
32 | "Definition": "let's freaking go"
33 | },
34 | {
35 | "Abbreviation": "LMFAO",
36 | "Definition": "Laughing my freaking *a* off"
37 | },
38 | {
39 | "Abbreviation": "LMK",
40 | "Definition": "Let me know"
41 | },
42 | {
43 | "Abbreviation": "LOL",
44 | "Definition": "Laugh out loud"
45 | },
46 | {
47 | "Abbreviation": "LTR",
48 | "Definition": "Left To Right"
49 | },
50 | {
51 | "Abbreviation": "NVM",
52 | "Definition": "Never mind"
53 | },
54 | {
55 | "Abbreviation": "OFC",
56 | "Definition": "Of course"
57 | },
58 | {
59 | "Abbreviation": "ROFL",
60 | "Definition": "Rolling on floor laughing"
61 | },
62 | {
63 | "Abbreviation": "RTL",
64 | "Definition": "Right To Left"
65 | },
66 | {
67 | "Abbreviation": "SMH",
68 | "Definition": "Shaking my head"
69 | },
70 | {
71 | "Abbreviation": "STFU",
72 | "Definition": "Shut the *freak* up"
73 | },
74 | {
75 | "Abbreviation": "TTYL",
76 | "Definition": "Talk to you later"
77 | },
78 | {
79 | "Abbreviation": "TYSM",
80 | "Definition": "Thank You So Much",
81 | "Usage": "",
82 | "Example": "Cyber Definitions"
83 | },
84 | {
85 | "Abbreviation": "TYVM",
86 | "Definition": "Thank you very much"
87 | },
88 | {
89 | "Abbreviation": "YOLO",
90 | "Definition": "You only live once"
91 | }
92 | ]
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contributing to FOSS Acronyms
2 |
3 | :+1::tada: First off, thanks for taking the time to contribute! :tada::+1:
4 |
5 | The following is a set of guidelines for contributing to this project, which are hosted in the [D-EDGE Organization](https://github.com/d-edge) on GitHub. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
6 |
7 | ## Code of Conduct
8 |
9 | This project and everyone participating in it is governed by the [D-EDGE Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to [softwarecraft@d-edge.com](mailto:softwarecraft@d-edge.com).
10 |
11 | ## Working on your first Pull Request?
12 |
13 | You can learn how from this *free* series [How to Contribute to an Open Source Project on GitHub](https://kcd.im/pull-request)
14 |
15 | ## Git Commit Messages
16 |
17 | This project follows a subset of [Conventional commits specification](https://www.conventionalcommits.org/en/v1.0.0/).
18 | No type, no scope. Only description and so upper case the first letter.
19 |
20 | ## What to contribute?
21 |
22 | ### Fill gap
23 |
24 | FOSS-Acronyms has a lot of blank space waiting to be filled. Find an empty string in one of the [JSON](https://github.com/d-edge/foss-acronyms/tree/main/data) and fix it!
25 |
26 | 
27 |
28 | Pro-tips: Open [acronyms.json](https://github.com/d-edge/foss-acronyms/blob/main/data/acronyms.json) and search for `""` 😄
29 |
30 | ### Add new acronym
31 |
32 | You can contribute by adding new entries to the list of acronyms.
33 |
34 | - Find a good missing acronym
35 | - Grab one in the [issues](https://github.com/d-edge/foss-acronyms/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22). Issues are filled with good missing acronyms.
36 | - Submit your own. A missing acronym is an acronym not in the list nor in the issues. A good acronym is any acronym used by the FOSS community.
37 | - Fork the project. [You can use this shortcut](https://github.com/d-edge/foss-acronyms/fork).
38 | - Edit the JSON. A good acronym need
39 | - an `Abbreviation` like "FOSS"
40 | - a `Definition` like "Free & Open Source Software"
41 | - a `Usage` like "That is both free software and open-source software where anyone is freely licensed to use, copy, study, and change the software in any way, and the source code is openly shared so that people are encouraged to voluntarily improve the design of the software"
42 | - an `Example` wich is a collection of html link like `FOSS/FLOSS`. Don't forget to escape all the quote (e.g. `\"`).
43 | - Submit a PR
44 |
45 | Finally here is an example of a [merged PR](https://github.com/d-edge/foss-acronyms/pull/63/files). Have fun hacking this project 😸
46 |
47 | Thank you for contributing!
48 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Contributor Covenant Code of Conduct
2 |
3 | ## Our Pledge
4 |
5 | We as members, contributors, and leaders pledge to make participation in our
6 | community a harassment-free experience for everyone, regardless of age, body
7 | size, visible or invisible disability, ethnicity, sex characteristics, gender
8 | identity and expression, level of experience, education, socio-economic status,
9 | nationality, personal appearance, race, religion, or sexual identity
10 | and orientation.
11 |
12 | We pledge to act and interact in ways that contribute to an open, welcoming,
13 | diverse, inclusive, and healthy community.
14 |
15 | ## Our Standards
16 |
17 | Examples of behavior that contributes to a positive environment for our
18 | community include:
19 |
20 | * Demonstrating empathy and kindness toward other people
21 | * Being respectful of differing opinions, viewpoints, and experiences
22 | * Giving and gracefully accepting constructive feedback
23 | * Accepting responsibility and apologizing to those affected by our mistakes,
24 | and learning from the experience
25 | * Focusing on what is best not just for us as individuals, but for the
26 | overall community
27 |
28 | Examples of unacceptable behavior include:
29 |
30 | * The use of sexualized language or imagery, and sexual attention or
31 | advances of any kind
32 | * Trolling, insulting or derogatory comments, and personal or political attacks
33 | * Public or private harassment
34 | * Publishing others' private information, such as a physical or email
35 | address, without their explicit permission
36 | * Other conduct which could reasonably be considered inappropriate in a
37 | professional setting
38 |
39 | ## Enforcement Responsibilities
40 |
41 | Community leaders are responsible for clarifying and enforcing our standards of
42 | acceptable behavior and will take appropriate and fair corrective action in
43 | response to any behavior that they deem inappropriate, threatening, offensive,
44 | or harmful.
45 |
46 | Community leaders have the right and responsibility to remove, edit, or reject
47 | comments, commits, code, wiki edits, issues, and other contributions that are
48 | not aligned to this Code of Conduct, and will communicate reasons for moderation
49 | decisions when appropriate.
50 |
51 | ## Scope
52 |
53 | This Code of Conduct applies within all community spaces, and also applies when
54 | an individual is officially representing the community in public spaces.
55 | Examples of representing our community include using an official e-mail address,
56 | posting via an official social media account, or acting as an appointed
57 | representative at an online or offline event.
58 |
59 | ## Enforcement
60 |
61 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
62 | reported to the community leaders responsible for enforcement at
63 | softwarecraft@d-edge.com.
64 | All complaints will be reviewed and investigated promptly and fairly.
65 |
66 | All community leaders are obligated to respect the privacy and security of the
67 | reporter of any incident.
68 |
69 | ## Enforcement Guidelines
70 |
71 | Community leaders will follow these Community Impact Guidelines in determining
72 | the consequences for any action they deem in violation of this Code of Conduct:
73 |
74 | ### 1. Correction
75 |
76 | **Community Impact**: Use of inappropriate language or other behavior deemed
77 | unprofessional or unwelcome in the community.
78 |
79 | **Consequence**: A private, written warning from community leaders, providing
80 | clarity around the nature of the violation and an explanation of why the
81 | behavior was inappropriate. A public apology may be requested.
82 |
83 | ### 2. Warning
84 |
85 | **Community Impact**: A violation through a single incident or series
86 | of actions.
87 |
88 | **Consequence**: A warning with consequences for continued behavior. No
89 | interaction with the people involved, including unsolicited interaction with
90 | those enforcing the Code of Conduct, for a specified period of time. This
91 | includes avoiding interactions in community spaces as well as external channels
92 | like social media. Violating these terms may lead to a temporary or
93 | permanent ban.
94 |
95 | ### 3. Temporary Ban
96 |
97 | **Community Impact**: A serious violation of community standards, including
98 | sustained inappropriate behavior.
99 |
100 | **Consequence**: A temporary ban from any sort of interaction or public
101 | communication with the community for a specified period of time. No public or
102 | private interaction with the people involved, including unsolicited interaction
103 | with those enforcing the Code of Conduct, is allowed during this period.
104 | Violating these terms may lead to a permanent ban.
105 |
106 | ### 4. Permanent Ban
107 |
108 | **Community Impact**: Demonstrating a pattern of violation of community
109 | standards, including sustained inappropriate behavior, harassment of an
110 | individual, or aggression toward or disparagement of classes of individuals.
111 |
112 | **Consequence**: A permanent ban from any sort of public interaction within
113 | the community.
114 |
115 | ## Attribution
116 |
117 | This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118 | version 2.0, available at
119 | https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120 |
121 | Community Impact Guidelines were inspired by [Mozilla's code of conduct
122 | enforcement ladder](https://github.com/mozilla/diversity).
123 |
124 | [homepage]: https://www.contributor-covenant.org
125 |
126 | For answers to common questions about this code of conduct, see the FAQ at
127 | https://www.contributor-covenant.org/faq. Translations are available at
128 | https://www.contributor-covenant.org/translations.
129 |
--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
1 | Creative Commons Legal Code
2 |
3 | CC0 1.0 Universal
4 |
5 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE
6 | LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN
7 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS
8 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES
9 | REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS
10 | PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM
11 | THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED
12 | HEREUNDER.
13 |
14 | Statement of Purpose
15 |
16 | The laws of most jurisdictions throughout the world automatically confer
17 | exclusive Copyright and Related Rights (defined below) upon the creator
18 | and subsequent owner(s) (each and all, an "owner") of an original work of
19 | authorship and/or a database (each, a "Work").
20 |
21 | Certain owners wish to permanently relinquish those rights to a Work for
22 | the purpose of contributing to a commons of creative, cultural and
23 | scientific works ("Commons") that the public can reliably and without fear
24 | of later claims of infringement build upon, modify, incorporate in other
25 | works, reuse and redistribute as freely as possible in any form whatsoever
26 | and for any purposes, including without limitation commercial purposes.
27 | These owners may contribute to the Commons to promote the ideal of a free
28 | culture and the further production of creative, cultural and scientific
29 | works, or to gain reputation or greater distribution for their Work in
30 | part through the use and efforts of others.
31 |
32 | For these and/or other purposes and motivations, and without any
33 | expectation of additional consideration or compensation, the person
34 | associating CC0 with a Work (the "Affirmer"), to the extent that he or she
35 | is an owner of Copyright and Related Rights in the Work, voluntarily
36 | elects to apply CC0 to the Work and publicly distribute the Work under its
37 | terms, with knowledge of his or her Copyright and Related Rights in the
38 | Work and the meaning and intended legal effect of CC0 on those rights.
39 |
40 | 1. Copyright and Related Rights. A Work made available under CC0 may be
41 | protected by copyright and related or neighboring rights ("Copyright and
42 | Related Rights"). Copyright and Related Rights include, but are not
43 | limited to, the following:
44 |
45 | i. the right to reproduce, adapt, distribute, perform, display,
46 | communicate, and translate a Work;
47 | ii. moral rights retained by the original author(s) and/or performer(s);
48 | iii. publicity and privacy rights pertaining to a person's image or
49 | likeness depicted in a Work;
50 | iv. rights protecting against unfair competition in regards to a Work,
51 | subject to the limitations in paragraph 4(a), below;
52 | v. rights protecting the extraction, dissemination, use and reuse of data
53 | in a Work;
54 | vi. database rights (such as those arising under Directive 96/9/EC of the
55 | European Parliament and of the Council of 11 March 1996 on the legal
56 | protection of databases, and under any national implementation
57 | thereof, including any amended or successor version of such
58 | directive); and
59 | vii. other similar, equivalent or corresponding rights throughout the
60 | world based on applicable law or treaty, and any national
61 | implementations thereof.
62 |
63 | 2. Waiver. To the greatest extent permitted by, but not in contravention
64 | of, applicable law, Affirmer hereby overtly, fully, permanently,
65 | irrevocably and unconditionally waives, abandons, and surrenders all of
66 | Affirmer's Copyright and Related Rights and associated claims and causes
67 | of action, whether now known or unknown (including existing as well as
68 | future claims and causes of action), in the Work (i) in all territories
69 | worldwide, (ii) for the maximum duration provided by applicable law or
70 | treaty (including future time extensions), (iii) in any current or future
71 | medium and for any number of copies, and (iv) for any purpose whatsoever,
72 | including without limitation commercial, advertising or promotional
73 | purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each
74 | member of the public at large and to the detriment of Affirmer's heirs and
75 | successors, fully intending that such Waiver shall not be subject to
76 | revocation, rescission, cancellation, termination, or any other legal or
77 | equitable action to disrupt the quiet enjoyment of the Work by the public
78 | as contemplated by Affirmer's express Statement of Purpose.
79 |
80 | 3. Public License Fallback. Should any part of the Waiver for any reason
81 | be judged legally invalid or ineffective under applicable law, then the
82 | Waiver shall be preserved to the maximum extent permitted taking into
83 | account Affirmer's express Statement of Purpose. In addition, to the
84 | extent the Waiver is so judged Affirmer hereby grants to each affected
85 | person a royalty-free, non transferable, non sublicensable, non exclusive,
86 | irrevocable and unconditional license to exercise Affirmer's Copyright and
87 | Related Rights in the Work (i) in all territories worldwide, (ii) for the
88 | maximum duration provided by applicable law or treaty (including future
89 | time extensions), (iii) in any current or future medium and for any number
90 | of copies, and (iv) for any purpose whatsoever, including without
91 | limitation commercial, advertising or promotional purposes (the
92 | "License"). The License shall be deemed effective as of the date CC0 was
93 | applied by Affirmer to the Work. Should any part of the License for any
94 | reason be judged legally invalid or ineffective under applicable law, such
95 | partial invalidity or ineffectiveness shall not invalidate the remainder
96 | of the License, and in such case Affirmer hereby affirms that he or she
97 | will not (i) exercise any of his or her remaining Copyright and Related
98 | Rights in the Work or (ii) assert any associated claims and causes of
99 | action with respect to the Work, in either case contrary to Affirmer's
100 | express Statement of Purpose.
101 |
102 | 4. Limitations and Disclaimers.
103 |
104 | a. No trademark or patent rights held by Affirmer are waived, abandoned,
105 | surrendered, licensed or otherwise affected by this document.
106 | b. Affirmer offers the Work as-is and makes no representations or
107 | warranties of any kind concerning the Work, express, implied,
108 | statutory or otherwise, including without limitation warranties of
109 | title, merchantability, fitness for a particular purpose, non
110 | infringement, or the absence of latent or other defects, accuracy, or
111 | the present or absence of errors, whether or not discoverable, all to
112 | the greatest extent permissible under applicable law.
113 | c. Affirmer disclaims responsibility for clearing rights of other persons
114 | that may apply to the Work or any use thereof, including without
115 | limitation any person's Copyright and Related Rights in the Work.
116 | Further, Affirmer disclaims responsibility for obtaining any necessary
117 | consents, permissions or other rights required for any use of the
118 | Work.
119 | d. Affirmer understands and acknowledges that Creative Commons is not a
120 | party to this document and has no duty or obligation with respect to
121 | this CC0 or use of the Work.
122 |
--------------------------------------------------------------------------------
/data/acronyms.json:
--------------------------------------------------------------------------------
1 | [
2 | {
3 | "Abbreviation": "ACK",
4 | "Definition": "ACKnowledgement",
5 | "Usage": "Agreed/accepted change. A loose ACK can be confusing. It's best to avoid them unless it's a documentation/comment only change in which case there is nothing to test/verify; therefore the tested/untested distinction is not there",
6 | "Example": "Humanizer, Bitcoin"
7 | },
8 | {
9 | "Abbreviation": "AD",
10 | "Definition": "Architectural Decision",
11 | "Usage": "",
12 | "Example": "https://en.wikipedia.org/wiki/Architectural_decision"
13 | },
14 | {
15 | "Abbreviation": "ADR",
16 | "Definition": "Architectural Decision Record",
17 | "Usage": "",
18 | "Example": "https://adr.github.io/"
19 | },
20 | {
21 | "Abbreviation": "AFAICT",
22 | "Definition": "As Far As I Can Tell",
23 | "Usage": "",
24 | "Example": "aiohttp"
25 | },
26 | {
27 | "Abbreviation": "AFAIK",
28 | "Definition": "As Far As I Know",
29 | "Usage": "AFAIK, he will be away for three months.",
30 | "Example": "Diffract"
31 | },
32 | {
33 | "Abbreviation": "AFK",
34 | "Definition": "Away From Keyboard",
35 | "Usage": "I'm going afk, dinner's ready.",
36 | "Example": "Cambridge Dictionary"
37 | },
38 | {
39 | "Abbreviation": "AKM",
40 | "Definition": "Architectural Knowledge Management",
41 | "Usage": "Architectural Decisions, Architectural Decision Records, and Architecturally Significant Requirements all fall under the umbrella of Architectural Knowledge Management",
42 | "Example": ""
43 | },
44 | {
45 | "Abbreviation": "AOA",
46 | "Definition": "Analysis of Alternatives",
47 | "Usage": "",
48 | "Example": "/r/programming"
49 | },
50 | {
51 | "Abbreviation": "ASAP",
52 | "Definition": "As Soon As Possible",
53 | "Usage": "It is an informal way to say that who wrote it is busy at the moment and will reply as soon as he can.",
54 | "Example": "Britannica"
55 | },
56 | {
57 | "Abbreviation": "ASR",
58 | "Definition": "Architecturally Significant Requirements",
59 | "Usage": "",
60 | "Example": "https://en.wikipedia.org/wiki/Architecturally_significant_requirements"
61 | },
62 | {
63 | "Abbreviation": "BBL",
64 | "Definition": "Brown Bag Lunch",
65 | "Usage": "It is an informal training meeting usually performed during lunch. It is a nice way to share knowledge, train on technical, business or any kind of skills. The speaker does not have to be an expert of the topic.",
66 | "Example": "brownbaglunch on Github (French)"
67 | },
68 | {
69 | "Abbreviation": "CCW",
70 | "Definition": "Comment and Criticism Welcome",
71 | "Usage": "",
72 | "Example": ""
73 | },
74 | {
75 | "Abbreviation": "CFP",
76 | "Definition": "A Call For Papers (CFP) is an announcement conference organizers to speakers and scientists to submit their manuscript for review and publication in the conference journal.",
77 | "Usage": "Conferences set a deadlines for their CFP so authors know when to have their publication ready for review.",
78 | "Example": "Wiki for Calls For Papers"
79 | },
80 | {
81 | "Abbreviation": "CJK",
82 | "Definition": "Chinese-Japanese-Korean",
83 | "Usage": "Usually used in the context of localization or internationalization, because all of them include Chinese characters and derivatives in their writing systems. Often included are Hànzì in Chinese, Kanji and Kana in Japanese and Hanja and Hangul in Korean.",
84 | "Example": "Wikipedia page for CJK characters, a remark plugin to remove extra space between CJK Characters"
85 | },
86 | {
87 | "Abbreviation": "CLA",
88 | "Definition": "Contributor License Agreement",
89 | "Usage": "",
90 | "Example": "Play Framework, Microsoft"
91 | },
92 | {
93 | "Abbreviation": "CLI",
94 | "Definition": "Command Line Interface",
95 | "Usage": "I prefer using the CLI because it is faster.",
96 | "Example": "Wikipedia page for CLI"
97 | },
98 | {
99 | "Abbreviation": "CMV",
100 | "Definition": "Change My View",
101 | "Usage": "",
102 | "Example": ""
103 | },
104 | {
105 | "Abbreviation": "CoC",
106 | "Definition": "Code of Conduct",
107 | "Usage": "",
108 | "Example": "Our Code of Conduct"
109 | },
110 | {
111 | "Abbreviation": "Concept ACK",
112 | "Definition": "Concept ACKnowledgement",
113 | "Usage": "Agree with the idea and overall direction, but haven't reviewed the code changes or tested them",
114 | "Example": "Bitcoin"
115 | },
116 | {
117 | "Abbreviation": "DAE",
118 | "Definition": "Does Anyone Else",
119 | "Usage": "DAE think this language is confusing?",
120 | "Example": "https://www.reddit.com/r/ProgrammerHumor/comments/y6959z/comment/issuua9/?context=3"
121 | },
122 | {
123 | "Abbreviation": "DAG",
124 | "Definition": "In graph theory and computer science a Directed Acyclic Graph consists of vertices and directed edges between vertices such as following the direction of the edges will never form a closed loop.",
125 | "Usage": "Data flow diagrams and many many tree data structures are directed acyclic graphs. In DAGs topological sort algorithms work in linear time.",
126 | "Example": "Wikipedia page for DAG"
127 | },
128 | {
129 | "Abbreviation": "DevOps",
130 | "Definition": "Devlopment Operations",
131 | "Usage": "",
132 | "Example": ""
133 | },
134 | {
135 | "Abbreviation": "DI/DIP",
136 | "Definition": "Dependency Inversion Principle",
137 | "Usage": "The higher-level orchestrating components should not have to know the details of their dependencies",
138 | "Example": "Hacker Laws"
139 | },
140 | {
141 | "Abbreviation": "DoD",
142 | "Definition": "Definition of Done",
143 | "Usage": "When all conditions, or acceptance criteria, that a software product must satisfy are met and ready to be accepted by a user, customer, team, or consuming system.",
144 | "Example": "DEFINITION OF DONE"
145 | },
146 | {
147 | "Abbreviation": "DRY",
148 | "Definition": "Don't Repeat Yourself",
149 | "Usage": "This is used in couple with modular programming, and emphasize on code reusability",
150 | "Example": "Wikipedia"
151 | },
152 | {
153 | "Abbreviation": "DTO",
154 | "Definition": "Data Transfer Object",
155 | "Usage": "",
156 | "Example": "DTO Wikipedia"
157 | },
158 | {
159 | "Abbreviation": "DX",
160 | "Definition": "Developer Experience",
161 | "Usage": "Guidelines to make onboarding and development of a project easy to get into and maintain",
162 | "Example": "Near (Github)"
163 | },
164 | {
165 | "Abbreviation": "EBKAC",
166 | "Definition": "Error Between Keyboard And Chair",
167 | "Usage": "It's an error made by the human user of a complex system, usually a computer system, in interacting with it.",
168 | "Example": "User error"
169 | },
170 | {
171 | "Abbreviation": "ETA",
172 | "Definition": "Estimated Time of Arrival",
173 | "Usage": "To ask when something will be ready",
174 | "Example": "/r/fsharp"
175 | },
176 | {
177 | "Abbreviation": "FOMO",
178 | "Definition": "Fear Of Missing Out",
179 | "Usage": "The feeling of apprehension that one is either not in the know or missing out on information, events, experiences, or life decisions that could make one's life better",
180 | "Example": "Hacker News"
181 | },
182 | {
183 | "Abbreviation": "FOSS/FLOSS",
184 | "Definition": "Free & Open Source Software",
185 | "Usage": "That is both free software and open-source software where anyone is freely licensed to use, copy, study, and change the software in any way, and the source code is openly shared so that people are encouraged to voluntarily improve the design of the software",
186 | "Example": "FOSS/FLOSS"
187 | },
188 | {
189 | "Abbreviation": "FOUC",
190 | "Definition": "Flash Of Unstyled Content",
191 | "Usage": "When a web page appears briefly with the browser's default styles prior to loading an external CSS stylesheet",
192 | "Example": "md-block, Wikipedia"
193 | },
194 | {
195 | "Abbreviation": "FP",
196 | "Definition": "Functional Programming",
197 | "Usage": "",
198 | "Example": ""
199 | },
200 | {
201 | "Abbreviation": "FYA",
202 | "Definition": "For Your Action",
203 | "Usage": "When you ask someone to do something usually on an email or correspondence",
204 | "Example": ""
205 | },
206 | {
207 | "Abbreviation": "FYI",
208 | "Definition": "For Your Information",
209 | "Usage": "",
210 | "Example": "ArduPilot, F#'s slack"
211 | },
212 | {
213 | "Abbreviation": "GATs",
214 | "Definition": "Generic Associated Types",
215 | "Usage": "they allow you to define type, lifetime, or const generics on associated types",
216 | "Example": "Reddit, rust-lang"
217 | },
218 | {
219 | "Abbreviation": "GUI",
220 | "Definition": "Graphical User Interface",
221 | "Usage": "The GUI makes it very simple for beginners to use",
222 | "Example": "Wikipedia page for GUI"
223 | },
224 | {
225 | "Abbreviation": "IANAL",
226 | "Definition": "I Am Not A Lawyer",
227 | "Usage": "Used often before talking about licensing issues",
228 | "Example": "HackerNews, CUPS"
229 | },
230 | {
231 | "Abbreviation": "ICYMI",
232 | "Definition": "In Case You Missed It",
233 | "Usage": "",
234 | "Example": ""
235 | },
236 | {
237 | "Abbreviation": "IIRC",
238 | "Definition": "If I Recall Correctly",
239 | "Usage": "",
240 | "Example": ""
241 | },
242 | {
243 | "Abbreviation": "IMO",
244 | "Definition": "In My Opinion",
245 | "Usage": "",
246 | "Example": ""
247 | },
248 | {
249 | "Abbreviation": "ITT",
250 | "Definition": "In This Thread",
251 | "Usage": "",
252 | "Example": ""
253 | },
254 | {
255 | "Abbreviation": "KBD",
256 | "Definition": "Keyboard",
257 | "Usage": "",
258 | "Example": "https://github.com/zestedesavoir/zmarkdown/tree/HEAD/packages/remark-kbd#readme"
259 | },
260 | {
261 | "Abbreviation": "KISS",
262 | "Definition": "Keep It Simple, Stupid",
263 | "Usage": "KISS is a design principle stating that most systems work fine if it is built/kept simple than making the system complex.",
264 | "Example": "Wikipedia"
265 | },
266 | {
267 | "Abbreviation": "KPI",
268 | "Definition": "Key Performance Indicator",
269 | "Usage": "KPI is a type of performance indicator, which measures the success of an organisation or an activity.",
270 | "Example": "Wikipedia"
271 | },
272 | {
273 | "Abbreviation": "KYB",
274 | "Definition": "Know Your Business",
275 | "Usage": "Abbreviation is mostly used in these categories : customer, banking, business, technology",
276 | "Example": "Identify blog"
277 | },
278 | {
279 | "Abbreviation": "KYC",
280 | "Definition": "Know Your Customer",
281 | "Usage": "Abbreviation is mostly used in these categories : customer, banking, business, technology",
282 | "Example": "Identify blog"
283 | },
284 | {
285 | "Abbreviation": "LGTM",
286 | "Definition": "Looks Good To Me",
287 | "Usage": "See ACK",
288 | "Example": "Cardidy, Simple Icons, proposal-array-grouping, /r/webdev"
289 | },
290 | {
291 | "Abbreviation": "LOC/SLOC",
292 | "Definition": "(Source) Lines Of Code",
293 | "Usage": "Above each file on GitHub you can find something like `50 lines (43 sloc)`. The difference is the empty lines.",
294 | "Example": "GitHub"
295 | },
296 | {
297 | "Abbreviation": "MCVE",
298 | "Definition": "Minimal Complete Valid/Verfiable Example",
299 | "Usage": "When asking a question, people will be better able to provide help if you provide code that they can easily understand and use to reproduce the problem. Such a question will be to the point, include just the information that what is necessary, be valid, and be accompanied by a clear example of your problem which leaves no room for guesswork. This is referred to by community members as MCVE",
300 | "Example": "Stack Exchange"
301 | },
302 | {
303 | "Abbreviation": "MPA",
304 | "Definition": "Multi-Page Application",
305 | "Usage": "",
306 | "Example": "/r/web_design"
307 | },
308 | {
309 | "Abbreviation": "MR",
310 | "Definition": "Merge Request",
311 | "Usage": "See PR",
312 | "Example": ""
313 | },
314 | {
315 | "Abbreviation": "MRE",
316 | "Definition": "Minimal Reproducible Example",
317 | "Usage": "In computing, a minimal reproducible example (abbreviated MRE) is a collection of source code and other data files which allow a bug or problem to be demonstrated and reproduced.",
318 | "Example": "Stack Overflow"
319 | },
320 | {
321 | "Abbreviation": "MVP",
322 | "Definition": "Minimum Viable Product",
323 | "Usage": "A prototype version of a product with the minimum required feature set",
324 | "Example": "Wikipedia"
325 | },
326 | {
327 | "Abbreviation": "NACK/NAK",
328 | "Definition": "Negative ACKnowledgement",
329 | "Usage": "Disagree with the code changes/concept. Should be accompanied by an explanation",
330 | "Example": "Bitcoin"
331 | },
332 | {
333 | "Abbreviation": "NIH",
334 | "Definition": "Not Invented Here",
335 | "Usage": "NIH Syndrome is a decision-making error where we tend to value our own ideas above those conceived by people outside of our group",
336 | "Example": "learnosity"
337 | },
338 | {
339 | "Abbreviation": "NP",
340 | "Definition": "No Problem",
341 | "Usage": "No stress, it is fine",
342 | "Example": ""
343 | },
344 | {
345 | "Abbreviation": "OOP",
346 | "Definition": "Object Oriented Programming",
347 | "Usage": "",
348 | "Example": ""
349 | },
350 | {
351 | "Abbreviation": "OP",
352 | "Definition": "Original Post/Original Poster",
353 | "Usage": "Original Poster (who started a thread) or Original Post (the message that started it)",
354 | "Example": "/r/ProgrammerHumor, StackExchange"
355 | },
356 | {
357 | "Abbreviation": "PEBCAK",
358 | "Definition": "Problem Exists Between Chair And Keyboard",
359 | "Usage": "It is a user error, not a problem / bug in the program",
360 | "Example": "Humanizer, Community"
361 | },
362 | {
363 | "Abbreviation": "PEBKAC",
364 | "Definition": "Problem Exists Between Keyboard And Chair",
365 | "Usage": "It is a user error, not a problem / bug in the program",
366 | "Example": "Humanizer, Community"
367 | },
368 | {
369 | "Abbreviation": "PEBMAC",
370 | "Definition": "Problem Exists Between Monitor And Chair",
371 | "Usage": "It's an error made by the human user of a complex system, usually a computer system, in interacting with it.",
372 | "Example": "User error"
373 | },
374 | {
375 | "Abbreviation": "PEBUAK",
376 | "Definition": "Problem Exists Between User and Keyboard",
377 | "Usage": "It's an error made by the human user of a complex system, usually a computer system, in interacting with it.",
378 | "Example": "User error"
379 | },
380 | {
381 | "Abbreviation": "PICNIC",
382 | "Definition": "Problem In Chair Not In Computer",
383 | "Usage": "It's an error made by the human user of a complex system, usually a computer system, in interacting with it.",
384 | "Example": "User error"
385 | },
386 | {
387 | "Abbreviation": "POBCAK",
388 | "Definition": "a US government/military acronym for Problem Occurs Between Chair And Keyboard",
389 | "Usage": "It's an error made by the human user of a complex system, usually a computer system, in interacting with it.",
390 | "Example": "User error, List of U.S. government and military acronyms"
391 | },
392 | {
393 | "Abbreviation": "POCO",
394 | "Definition": "In software engineering, a Plain Old CLR Object, or plain old class object is a simple object created in the .NET Common Language Runtime (CLR) that is not using inheritance nor attributes.",
395 | "Usage": "This abbreviation is often used when discussing library APIs or interfaces in which data is exchanged to denote that the object is simple to use.",
396 | "Example": "POCO Definition"
397 | },
398 | {
399 | "Abbreviation": "POJO",
400 | "Definition": "In software engineering, a Plain Old Java Object is an ordinary Java object, not bound by any special restrictions (extends, implements, prespecified annocations).",
401 | "Usage": "This abbreviation is often used when discussing library APIs or interfaces in which data is exchanged to denote that the object is simple to interact with.",
402 | "Example": "POJO Definition"
403 | },
404 | {
405 | "Abbreviation": "PR",
406 | "Definition": "Pull Request",
407 | "Usage": "Tell others about changes you've pushed to a branch in a repository",
408 | "Example": "/r/vuejs"
409 | },
410 | {
411 | "Abbreviation": "RACI",
412 | "Definition": "Responsible, Accountable, Consulted, and Informed",
413 | "Usage": "A responsibility assignment matrix, also known as RACI matrix or linear responsibility chart, describes the participation by various roles in completing tasks or deliverables for a project or business process.",
414 | "Example": "IBM"
415 | },
416 | {
417 | "Abbreviation": "RCE",
418 | "Definition": "Remote Code Execution",
419 | "Usage": "Remote code execution is a cyber-attack whereby an attacker can remotely execute commands on someone else’s computing device. Remote code executions (RCEs) usually occur due to malicious malware downloaded by the host and can happen regardless of the device’s geographic location. Remote Code Execution (RCE) is also referred to as Remote Code Evaluation.",
420 | "Example": "RCE"
421 | },
422 | {
423 | "Abbreviation": "ReprEx ",
424 | "Definition": "Reproducible Example",
425 | "Usage": "A reprex facilitates easier conversations about your code by presenting it in a concise and repeatable way. A simple copy-paste should be all that’s needed to run the reprex, and running it shouldn’t generate errors except for those that the reprex is intended to exemplify",
426 | "Example": "Tidyverse, University of Virginia Library"
427 | },
428 | {
429 | "Abbreviation": "RFC",
430 | "Definition": "Request For Comments",
431 | "Usage": "",
432 | "Example": ""
433 | },
434 | {
435 | "Abbreviation": "RFI",
436 | "Definition": "Request for Information",
437 | "Usage": "An RFI (request for information) is a formal process for gathering information from potential suppliers of a good or service. RFIs are intended to be written by customers and sent to potential suppliers. An RFI is typically the first and most broad series of requests intended to narrow down a list of potential vendor candidates.",
438 | "Example": "RFI"
439 | },
440 | {
441 | "Abbreviation": "RFP",
442 | "Definition": "Request for Proposal",
443 | "Usage": "A request for proposal (RFP) is a document that an organization, often a government agency or large enterprise, posts to elicit a response -- a formal bid -- from potential vendors for a desired IT solution. The RFP specifies what the customer is looking for and describes each evaluation criterion on which a vendor's proposal will be assessed.",
444 | "Example": "RFP"
445 | },
446 | {
447 | "Abbreviation": "RICE",
448 | "Definition": "Race Inspired Cosmetic Enhancements",
449 | "Usage": "In the context of FOSS it is usually a customised Desktop Environment in Linux, such as Arch users who will config every component of their OS to look and behave how they wish and to suit their particular workflow",
450 | "Example": "Reddit comment, Urban Dictionary, r/Unixporn"
451 | },
452 | {
453 | "Abbreviation": "RTFA",
454 | "Definition": "Read The 'Fine' Article aka Read The 'F*****g' Article",
455 | "Usage": "A sarcastic way to indicate that it would help to read the full article before asking questions. Many synonyms with different adverbs and different document types exists. See also RTFM.",
456 | "Example": "Similar Abbreviations"
457 | },
458 | {
459 | "Abbreviation": "RTFM",
460 | "Definition": "Read The 'Fine' Manual aka Read The 'F*****g' Manual",
461 | "Usage": "Originally a way for the _gurus_ to get rid of trivial questions from newbies, now a humble way to state that a mistake or a waste of time can be avoided by reading the freaking manual first (assuming it exists).",
462 | "Example": "XKCD comic, Github commits"
463 | },
464 | {
465 | "Abbreviation": "SCM",
466 | "Definition": "Source Code Management",
467 | "Usage": "See VCS",
468 | "Example": ""
469 | },
470 | {
471 | "Abbreviation": "SE",
472 | "Definition": "Software Engineer or System Engineer",
473 | "Usage": "",
474 | "Example": ""
475 | },
476 | {
477 | "Abbreviation": "SOLID",
478 | "Definition": "Single responsibility, Open-closed, Liskov substitution, Interface segregation and Dependency inversion",
479 | "Usage": "5 (of many) software design principles, promoted by Robert \"Uncle Bob\" Martin",
480 | "Example": "Wikipedia"
481 | },
482 | {
483 | "Abbreviation": "SPA",
484 | "Definition": "Single-Page Application",
485 | "Usage": "",
486 | "Example": "/r/web_design"
487 | },
488 | {
489 | "Abbreviation": "SRE",
490 | "Definition": "Site Reliability Engineer",
491 | "Usage": "",
492 | "Example": "How They SRE"
493 | },
494 | {
495 | "Abbreviation": "SRP",
496 | "Definition": "Single-Responsibility Principle",
497 | "Usage": "The single-responsibility principle is a computer-programming principle that states that every module, class or function in a computer program should have responsibility over a single part of that program's functionality, and it should encapsulate that part. wikipedia",
498 | "Example": "/r/csharp/"
499 | },
500 | {
501 | "Abbreviation": "SSOC",
502 | "Definition": "Social Summer of Code",
503 | "Usage": "Social foundation offers this two-month long summer program for students to learn about the open-source culture and get involved in the community. Participants contribute to real-life projects under the guidance of experienced mentors.",
504 | "Example": "Social Summer of Code"
505 | },
506 | {
507 | "Abbreviation": "SWE",
508 | "Definition": "SoftWare Engineer",
509 | "Usage": "",
510 | "Example": ""
511 | },
512 | {
513 | "Abbreviation": "TBD",
514 | "Definition": "To Be Defined/Done",
515 | "Usage": "",
516 | "Example": "Software Craft Website"
517 | },
518 | {
519 | "Abbreviation": "tested ACK",
520 | "Definition": "Tested ACKnowledgment",
521 | "Usage": "Reviewed the code changes and have verified the functionality or bug fix",
522 | "Example": "Bitcoin"
523 | },
524 | {
525 | "Abbreviation": "TFA",
526 | "Definition": "The 'Fine' Article aka The 'F*****g' Article (in chat lingo), or in signal processing Time Frequency Analysis indicating the simultaneous analysis of a signal in time and frequency domains.",
527 | "Usage": "A sarcastic way to refer to an article. Or a way to refer to the analysis of repeating patterns in data over time.",
528 | "Example": "Wikipedia RTFM - Similar Abbreviations, Wikipedia on Time-Frequency Analysis"
529 | },
530 | {
531 | "Abbreviation": "TIL",
532 | "Definition": "Today I Learned",
533 | "Usage": "TIL that TIL is Today I Learned",
534 | "Example": "/r/ProgrammerTIL/"
535 | },
536 | {
537 | "Abbreviation": "UML",
538 | "Definition": "Unified Modeling Language",
539 | "Usage": "A language for visualizing system design with all its classes, objects, and components, etc.",
540 | "Example": "Geeks for Geeks UML"
541 | },
542 | {
543 | "Abbreviation": "utACK",
544 | "Definition": "UnTested ACKnowledgment",
545 | "Usage": "Reviewed and agree with the code changes but haven't actually tested them",
546 | "Example": "Bitcoin"
547 | },
548 | {
549 | "Abbreviation": "VCS",
550 | "Definition": "Version Control Software",
551 | "Usage": "A way to keep a track of the changes in the code so that if something goes wrong, we can make comparisons in different code versions and revert to any previous version that we want. Git, SVN or Mercurial are VCS",
552 | "Example": "/r/ProgrammerHumor, softwaretestinghelp.com"
553 | },
554 | {
555 | "Abbreviation": "WDYT",
556 | "Definition": "What Do You Think",
557 | "Usage": "",
558 | "Example": "Bitrise Workflow Editor"
559 | },
560 | {
561 | "Abbreviation": "WIP",
562 | "Definition": "Work In Progress",
563 | "Usage": "Do not merge yet",
564 | "Example": "GitLab's blog"
565 | },
566 | {
567 | "Abbreviation": "WRT",
568 | "Definition": "With Respect to",
569 | "Usage": "In reference to a particular thing or situation",
570 | "Example": "Tailwind Blog, Hacker News"
571 | },
572 | {
573 | "Abbreviation": "WYSIWYG",
574 | "Definition": "What You See Is What You Get",
575 | "Usage": "It is a system in which editing software allows content to be edited in a form that resembles its appearance when printed or displayed as a finished product. It is typically used an arbitrary markup language to define the codes/tags",
576 | "Example": "WYSIWYG"
577 | },
578 | {
579 | "Abbreviation": "XP",
580 | "Definition": "Extreme Programming",
581 | "Usage": "",
582 | "Example": "Wikipedia"
583 | },
584 | {
585 | "Abbreviation": "YAGNI",
586 | "Definition": "You Ain't Gonna Need It",
587 | "Usage": "",
588 | "Example": "Tech Excellence"
589 | },
590 | {
591 | "Abbreviation": "YMMV",
592 | "Definition": "Your Mileage May Vary",
593 | "Usage": "",
594 | "Example": "Whisper"
595 | }
596 | ]
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # FOSS Community Acronyms
2 |
3 | [](http://makeapullrequest.com)
4 |
5 | List of abbreviations used within the FOSS community, and their definitions and usages. This list inludes more common english acronyms popular on internet.
6 |
7 | Maintained by folks at [D-EDGE](https://www.d-edge.com/).
8 |
9 | ## Contributing
10 |
11 | If you have a GitHub account, you can submit a pull request to any json in the data folder.
12 |
13 | ## Tip
14 |
15 | Write out the full name when you want to introduce a term (with the acronym in brackets). Use only the acronym after this.
16 | Example:
17 |
18 | > Companies don’t usually talk about FOMO (Fear Of Missing Out). Instead, they use phrases such as “shiny object syndrome” and “market expectations.” Google is a great example of how FOMO can creep in.
19 |
20 | [FOMO Is Disastrous for Company Strategies](https://rubenugarte.com/fomo-is-disastrous-for-company-strategies/) by [Ruben Ugarte](https://rubenugarte.com/)
21 |
22 | If you are only going to use the acronym once, maybe don't use it at all and rely on the whole expression instead.
23 |
24 | ## Acronyms
25 |
26 |
27 |
28 |
| Abbreviation | Definition | Usage | Example |
|---|
| ACK | ACKnowledgement | Agreed/accepted change. A loose ACK can be confusing. It's best to avoid them unless it's a documentation/comment only change in which case there is nothing to test/verify; therefore the tested/untested distinction is not there | Humanizer, Bitcoin |
29 | | AD | Architectural Decision | | https://en.wikipedia.org/wiki/Architectural_decision |
30 | | ADR | Architectural Decision Record | | https://adr.github.io/ |
31 | | AFAICT | As Far As I Can Tell | | aiohttp |
32 | | AFAIK | As Far As I Know | AFAIK, he will be away for three months. | Diffract |
33 | | AFK | Away From Keyboard | I'm going afk, dinner's ready. | Cambridge Dictionary |
34 | | AKM | Architectural Knowledge Management | Architectural Decisions, Architectural Decision Records, and Architecturally Significant Requirements all fall under the umbrella of Architectural Knowledge Management | |
35 | | AOA | Analysis of Alternatives | | /r/programming |
36 | | ASAP | As Soon As Possible | It is an informal way to say that who wrote it is busy at the moment and will reply as soon as he can. | Britannica |
37 | | ASR | Architecturally Significant Requirements | | https://en.wikipedia.org/wiki/Architecturally_significant_requirements |
38 | | BBL | Brown Bag Lunch | It is an informal training meeting usually performed during lunch. It is a nice way to share knowledge, train on technical, business or any kind of skills. The speaker does not have to be an expert of the topic. | brownbaglunch on Github (French) |
39 | | CCW | Comment and Criticism Welcome | | |
40 | | CFP | A Call For Papers (CFP) is an announcement conference organizers to speakers and scientists to submit their manuscript for review and publication in the conference journal. | Conferences set a deadlines for their CFP so authors know when to have their publication ready for review. | Wiki for Calls For Papers |
41 | | CJK | Chinese-Japanese-Korean | Usually used in the context of localization or internationalization, because all of them include Chinese characters and derivatives in their writing systems. Often included are Hànzì in Chinese, Kanji and Kana in Japanese and Hanja and Hangul in Korean. | Wikipedia page for CJK characters, a remark plugin to remove extra space between CJK Characters |
42 | | CLA | Contributor License Agreement | | Play Framework, Microsoft |
43 | | CLI | Command Line Interface | I prefer using the CLI because it is faster. | Wikipedia page for CLI |
44 | | CMV | Change My View | | |
45 | | CoC | Code of Conduct | | Our Code of Conduct |
46 | | Concept ACK | Concept ACKnowledgement | Agree with the idea and overall direction, but haven't reviewed the code changes or tested them | Bitcoin |
47 | | DAE | Does Anyone Else | DAE think this language is confusing? | https://www.reddit.com/r/ProgrammerHumor/comments/y6959z/comment/issuua9/?context=3 |
48 | | DAG | In graph theory and computer science a Directed Acyclic Graph consists of vertices and directed edges between vertices such as following the direction of the edges will never form a closed loop. | Data flow diagrams and many many tree data structures are directed acyclic graphs. In DAGs topological sort algorithms work in linear time. | Wikipedia page for DAG |
49 | | DevOps | Devlopment Operations | | |
50 | | DI/DIP | Dependency Inversion Principle | The higher-level orchestrating components should not have to know the details of their dependencies | Hacker Laws |
51 | | DoD | Definition of Done | When all conditions, or acceptance criteria, that a software product must satisfy are met and ready to be accepted by a user, customer, team, or consuming system. | DEFINITION OF DONE |
52 | | DRY | Don't Repeat Yourself | This is used in couple with modular programming, and emphasize on code reusability | Wikipedia |
53 | | DTO | Data Transfer Object | | DTO Wikipedia |
54 | | DX | Developer Experience | Guidelines to make onboarding and development of a project easy to get into and maintain | Near (Github) |
55 | | EBKAC | Error Between Keyboard And Chair | It's an error made by the human user of a complex system, usually a computer system, in interacting with it. | User error |
56 | | ETA | Estimated Time of Arrival | To ask when something will be ready | /r/fsharp |
57 | | FOMO | Fear Of Missing Out | The feeling of apprehension that one is either not in the know or missing out on information, events, experiences, or life decisions that could make one's life better | Hacker News |
58 | | FOSS/FLOSS | Free & Open Source Software | That is both free software and open-source software where anyone is freely licensed to use, copy, study, and change the software in any way, and the source code is openly shared so that people are encouraged to voluntarily improve the design of the software | FOSS/FLOSS |
59 | | FOUC | Flash Of Unstyled Content | When a web page appears briefly with the browser's default styles prior to loading an external CSS stylesheet | md-block, Wikipedia |
60 | | FP | Functional Programming | | |
61 | | FYA | For Your Action | When you ask someone to do something usually on an email or correspondence | |
62 | | FYI | For Your Information | | ArduPilot, F#'s slack |
63 | | GATs | Generic Associated Types | they allow you to define type, lifetime, or const generics on associated types | Reddit, rust-lang |
64 | | GUI | Graphical User Interface | The GUI makes it very simple for beginners to use | Wikipedia page for GUI |
65 | | IANAL | I Am Not A Lawyer | Used often before talking about licensing issues | HackerNews, CUPS |
66 | | ICYMI | In Case You Missed It | | |
67 | | IIRC | If I Recall Correctly | | |
68 | | IMO | In My Opinion | | |
69 | | ITT | In This Thread | | |
70 | | KBD | Keyboard | | https://github.com/zestedesavoir/zmarkdown/tree/HEAD/packages/remark-kbd#readme |
71 | | KISS | Keep It Simple, Stupid | KISS is a design principle stating that most systems work fine if it is built/kept simple than making the system complex. | Wikipedia |
72 | | KPI | Key Performance Indicator | KPI is a type of performance indicator, which measures the success of an organisation or an activity. | Wikipedia |
73 | | KYB | Know Your Business | Abbreviation is mostly used in these categories : customer, banking, business, technology | Identify blog |
74 | | KYC | Know Your Customer | Abbreviation is mostly used in these categories : customer, banking, business, technology | Identify blog |
75 | | LGTM | Looks Good To Me | See ACK | Cardidy, Simple Icons, proposal-array-grouping, /r/webdev |
76 | | LOC/SLOC | (Source) Lines Of Code | Above each file on GitHub you can find something like `50 lines (43 sloc)`. The difference is the empty lines. | GitHub |
77 | | MCVE | Minimal Complete Valid/Verfiable Example | When asking a question, people will be better able to provide help if you provide code that they can easily understand and use to reproduce the problem. Such a question will be to the point, include just the information that what is necessary, be valid, and be accompanied by a clear example of your problem which leaves no room for guesswork. This is referred to by community members as MCVE | Stack Exchange |
78 | | MPA | Multi-Page Application | | /r/web_design |
79 | | MR | Merge Request | See PR | |
80 | | MRE | Minimal Reproducible Example | In computing, a minimal reproducible example (abbreviated MRE) is a collection of source code and other data files which allow a bug or problem to be demonstrated and reproduced. | Stack Overflow |
81 | | MVP | Minimum Viable Product | A prototype version of a product with the minimum required feature set | Wikipedia |
82 | | NACK/NAK | Negative ACKnowledgement | Disagree with the code changes/concept. Should be accompanied by an explanation | Bitcoin |
83 | | NIH | Not Invented Here | NIH Syndrome is a decision-making error where we tend to value our own ideas above those conceived by people outside of our group | learnosity |
84 | | NP | No Problem | No stress, it is fine | |
85 | | OOP | Object Oriented Programming | | |
86 | | OP | Original Post/Original Poster | Original Poster (who started a thread) or Original Post (the message that started it) | /r/ProgrammerHumor, StackExchange |
87 | | PEBCAK | Problem Exists Between Chair And Keyboard | It is a user error, not a problem / bug in the program | Humanizer, Community |
88 | | PEBKAC | Problem Exists Between Keyboard And Chair | It is a user error, not a problem / bug in the program | Humanizer, Community |
89 | | PEBMAC | Problem Exists Between Monitor And Chair | It's an error made by the human user of a complex system, usually a computer system, in interacting with it. | User error |
90 | | PEBUAK | Problem Exists Between User and Keyboard | It's an error made by the human user of a complex system, usually a computer system, in interacting with it. | User error |
91 | | PICNIC | Problem In Chair Not In Computer | It's an error made by the human user of a complex system, usually a computer system, in interacting with it. | User error |
92 | | POBCAK | a US government/military acronym for Problem Occurs Between Chair And Keyboard | It's an error made by the human user of a complex system, usually a computer system, in interacting with it. | User error, List of U.S. government and military acronyms |
93 | | POCO | In software engineering, a Plain Old CLR Object, or plain old class object is a simple object created in the .NET Common Language Runtime (CLR) that is not using inheritance nor attributes. | This abbreviation is often used when discussing library APIs or interfaces in which data is exchanged to denote that the object is simple to use. | POCO Definition |
94 | | POJO | In software engineering, a Plain Old Java Object is an ordinary Java object, not bound by any special restrictions (extends, implements, prespecified annocations). | This abbreviation is often used when discussing library APIs or interfaces in which data is exchanged to denote that the object is simple to interact with. | POJO Definition |
95 | | PR | Pull Request | Tell others about changes you've pushed to a branch in a repository | /r/vuejs |
96 | | RACI | Responsible, Accountable, Consulted, and Informed | A responsibility assignment matrix, also known as RACI matrix or linear responsibility chart, describes the participation by various roles in completing tasks or deliverables for a project or business process. | IBM |
97 | | RCE | Remote Code Execution | Remote code execution is a cyber-attack whereby an attacker can remotely execute commands on someone else’s computing device. Remote code executions (RCEs) usually occur due to malicious malware downloaded by the host and can happen regardless of the device’s geographic location. Remote Code Execution (RCE) is also referred to as Remote Code Evaluation. | RCE |
98 | | ReprEx | Reproducible Example | A reprex facilitates easier conversations about your code by presenting it in a concise and repeatable way. A simple copy-paste should be all that’s needed to run the reprex, and running it shouldn’t generate errors except for those that the reprex is intended to exemplify | Tidyverse, University of Virginia Library |
99 | | RFC | Request For Comments | | |
100 | | RFI | Request for Information | An RFI (request for information) is a formal process for gathering information from potential suppliers of a good or service. RFIs are intended to be written by customers and sent to potential suppliers. An RFI is typically the first and most broad series of requests intended to narrow down a list of potential vendor candidates. | RFI |
101 | | RFP | Request for Proposal | A request for proposal (RFP) is a document that an organization, often a government agency or large enterprise, posts to elicit a response -- a formal bid -- from potential vendors for a desired IT solution. The RFP specifies what the customer is looking for and describes each evaluation criterion on which a vendor's proposal will be assessed. | RFP |
102 | | RICE | Race Inspired Cosmetic Enhancements | In the context of FOSS it is usually a customised Desktop Environment in Linux, such as Arch users who will config every component of their OS to look and behave how they wish and to suit their particular workflow | Reddit comment, Urban Dictionary, r/Unixporn |
103 | | RTFA | Read The 'Fine' Article aka Read The 'F*****g' Article | A sarcastic way to indicate that it would help to read the full article before asking questions. Many synonyms with different adverbs and different document types exists. See also RTFM. | Similar Abbreviations |
104 | | RTFM | Read The 'Fine' Manual aka Read The 'F*****g' Manual | Originally a way for the _gurus_ to get rid of trivial questions from newbies, now a humble way to state that a mistake or a waste of time can be avoided by reading the freaking manual first (assuming it exists). | XKCD comic, Github commits |
105 | | SCM | Source Code Management | See VCS | |
106 | | SE | Software Engineer or System Engineer | | |
107 | | SOLID | Single responsibility, Open-closed, Liskov substitution, Interface segregation and Dependency inversion | 5 (of many) software design principles, promoted by Robert "Uncle Bob" Martin | Wikipedia |
108 | | SPA | Single-Page Application | | /r/web_design |
109 | | SRE | Site Reliability Engineer | | How They SRE |
110 | | SRP | Single-Responsibility Principle | The single-responsibility principle is a computer-programming principle that states that every module, class or function in a computer program should have responsibility over a single part of that program's functionality, and it should encapsulate that part. wikipedia | /r/csharp/ |
111 | | SSOC | Social Summer of Code | Social foundation offers this two-month long summer program for students to learn about the open-source culture and get involved in the community. Participants contribute to real-life projects under the guidance of experienced mentors. | Social Summer of Code |
112 | | SWE | SoftWare Engineer | | |
113 | | TBD | To Be Defined/Done | | Software Craft Website |
114 | | tested ACK | Tested ACKnowledgment | Reviewed the code changes and have verified the functionality or bug fix | Bitcoin |
115 | | TFA | The 'Fine' Article aka The 'F*****g' Article (in chat lingo), or in signal processing Time Frequency Analysis indicating the simultaneous analysis of a signal in time and frequency domains. | A sarcastic way to refer to an article. Or a way to refer to the analysis of repeating patterns in data over time. | Wikipedia RTFM - Similar Abbreviations, Wikipedia on Time-Frequency Analysis |
116 | | TIL | Today I Learned | TIL that TIL is Today I Learned | /r/ProgrammerTIL/ |
117 | | UML | Unified Modeling Language | A language for visualizing system design with all its classes, objects, and components, etc. | Geeks for Geeks UML |
118 | | utACK | UnTested ACKnowledgment | Reviewed and agree with the code changes but haven't actually tested them | Bitcoin |
119 | | VCS | Version Control Software | A way to keep a track of the changes in the code so that if something goes wrong, we can make comparisons in different code versions and revert to any previous version that we want. Git, SVN or Mercurial are VCS | /r/ProgrammerHumor, softwaretestinghelp.com |
120 | | WDYT | What Do You Think | | Bitrise Workflow Editor |
121 | | WIP | Work In Progress | Do not merge yet | GitLab's blog |
122 | | WRT | With Respect to | In reference to a particular thing or situation | Tailwind Blog, Hacker News |
123 | | WYSIWYG | What You See Is What You Get | It is a system in which editing software allows content to be edited in a form that resembles its appearance when printed or displayed as a finished product. It is typically used an arbitrary markup language to define the codes/tags | WYSIWYG |
124 | | XP | Extreme Programming | | Wikipedia |
125 | | YAGNI | You Ain't Gonna Need It | | Tech Excellence |
126 | | YMMV | Your Mileage May Vary | | Whisper |
127 |
128 |
129 | ## Common chat acronyms
130 |
131 |
132 |
133 | | Abbreviation | Definition |
|---|
| AFK | Away From Keyboard |
134 | | BRB | Be Right Back |
135 | | CMIIW | Correct me if i'm wrong |
136 | | IKR | I know, right |
137 | | ILY | I love you |
138 | | IRL | In Real Life |
139 | | IYKYK | If You Know You Know |
140 | | LFG | let's freaking go |
141 | | LMFAO | Laughing my freaking *a* off |
142 | | LMK | Let me know |
143 | | LOL | Laugh out loud |
144 | | LTR | Left To Right |
145 | | NVM | Never mind |
146 | | OFC | Of course |
147 | | ROFL | Rolling on floor laughing |
148 | | RTL | Right To Left |
149 | | SMH | Shaking my head |
150 | | STFU | Shut the *freak* up |
151 | | TTYL | Talk to you later |
152 | | TYSM | Thank You So Much |
153 | | TYVM | Thank you very much |
154 | | YOLO | You only live once |
155 |
156 |
157 | ## Communities, Companies, Organizations
158 |
159 |
160 |
161 | | Abbreviation | Meaning | URL | What they do |
|---|
| AWS | Amazon web Services | https://aws.amazon.com/ | Amazon Web Services offers reliable, scalable, and inexpensive cloud computing services. |
162 | | FSF | Free Software Foundation | https://www.fsf.org | Oversee a number of open source organizations |
163 | | GH | GitHub | https://github.com | Source code host, owned by Microsoft |
164 | | GNU | Collection of free software, a license | https://gnu.org | program of FSF, develops many linux tools and a commonly used license |
165 | | MS | Microsoft | https://microsoft.com | Makers of windows, azure, vscode, and other tools that might be relevent to developers |
166 | | OSI | Open Source Initiative | https://opensource.org | Defining 'Open Source' |
167 | | SO | StackOverflow | https://stackoverflow.com | Popular question and answer website |
168 | | YT | YouTube | https://www.youtube.com/ | YouTube is online video sharing and social media platform |
169 |
170 |
171 | ## Stacks
172 |
173 |
174 |
175 | | Abbreviation | Definition | Example |
|---|
| EFK | Elasticsearch, Fluentd, and Kibana | How To Set Up an Elasticsearch, Fluentd and Kibana (EFK) Logging Stack on Kubernetes |
176 | | ELK | Elasticsearch, Logstash, and Kibana | What is the ELK Stack? |
177 | | LAMP | Linux, Apache, MySQL, PHP (Perl or Python) | IBM Cloud, Wikipedia |
178 | | LEMP | Linux, Nginx Server, MySQL, PHP (Perl or Python) | |
179 | | MEAN | MongoDB, Express.js, Angular.js, Node.js | |
180 | | MERN | MongoDB, Express.js, React.js, Node.js | |
181 | | MEVN | MongoDB, Express.js, Vue.js, Node.js | What is MEVN stack? |
182 | | SAFE | Suave (or Saturn), Azure, Fable, Elmish | /r/fsharp |
183 |
184 |
185 |
186 | ## Related document
187 |
188 | - [The Jargon File](http://www.catb.org/jargon/html/index.html)
189 | - [Bitcoin's CONTRIBUTING.md](https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#peer-review)
190 | - [Bitcoin hacker lingo (stolen from TCP)](https://nitter.vxempire.xyz/jgarzik/status/601815506291531776)
191 | - [What do cryptic Github comments mean?](https://www.freecodecamp.org/news/what-do-cryptic-github-comments-mean-9c1912bcc0a4/)
192 |
193 | ## Want to support us?
194 |
195 | * Don't forget to give a ⭐ to this repo on GitHub!
196 | * Share your feedback and ideas to improve the collection!
197 | * Share the collection on your favorite social media and your friends!
198 | * Help us to improve the collection!
199 |
200 | ## License
201 |
202 | [CC0 1.0 Universal](./LICENSE)
203 |
--------------------------------------------------------------------------------