Add Code Formatting section to README

.editorconfig

@@ -0,0 +1,10 @@
+root = true
+
+[*]
+end_of_line = lf
+insert_final_newline = true
+charset = utf-8
+indent_style = space
+indent_size = 2
+trim_trailing_whitespace = true
+max_line_length = off

.gitattributes

@@ -0,0 +1 @@
+* text eol=lf

.github/pull_request_template.md

@@ -0,0 +1,10 @@
+<!--
+Please read the CONTRIBUTING.md first. The most important parts regarding the actual entry:
+
+- Write about it's unique selling point compared to other projects.
+- If it's a commercial project, then mark it as such, e.g. `[Title ![c]](URL)`.
+- Ensure that you provide concise and informative descriptions.
+- Do not use a description like "A library/project/tool/framework for JSON processing in Java" since all of this is implied.
+- Finish the description with a dot.
+- Try to order it alphabetically.
+-->

.github/workflows/update-readme.yml

@@ -0,0 +1,67 @@
+name: Update README
+
+on:
+  schedule:
+    # Run once a week on Monday at 00:00 UTC
+    - cron: "0 0 * * 1"
+  workflow_dispatch: # Allow manual triggering
+  push:
+    branches:
+      - master
+      - test
+    paths:
+      - "CONTRIBUTE_README.md"
+      - "scripts/**"
+
+jobs:
+  update-readme:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v6
+        with:
+          fetch-depth: 0 # Fetch all history for git operations
+
+      - name: Set up Java
+        uses: actions/setup-java@v5
+        with:
+          distribution: "temurin"
+          java-version: "25"
+
+      - name: Restore stats cache
+        run: |
+          mkdir -p .tmp
+          # On scheduled runs, refresh all stats by not restoring cache
+          # On manual/push runs, use cache to avoid unnecessary API calls
+          if [ "${{ github.event_name }}" == "schedule" ]; then
+            echo "Scheduled run detected - will fetch fresh data for all repositories"
+            # Don't restore cache, let script fetch everything fresh
+          else
+            # Try to restore stats cache from previous run
+            if git show HEAD:.tmp/github-stats.txt > .tmp/github-stats.txt 2>/dev/null; then
+              echo "Restored existing stats cache from previous commit"
+            else
+              echo "No existing stats cache found, will fetch all data"
+            fi
+          fi
+
+      - name: Run README generation workflow
+        env:
+          PAT: ${{ secrets.PAT }}
+        run: |
+          java --enable-preview --source 25 scripts/run_workflow.java
+
+      - name: Commit updated README and stats cache
+        run: |
+          git config --local user.email "action@github.com"
+          git config --local user.name "GitHub Action"
+          git add -f README.md
+          # Always commit the stats cache so it persists for next run
+          git add -f .tmp/github-stats.txt || true
+          if git diff --staged --quiet; then
+            echo "No changes to commit"
+          else
+            git commit -m "Update README with latest GitHub stats [skip ci]"
+            git push
+          fi

.gitignore

@@ -0,0 +1 @@
+.idea/

CONTRIBUTING.md

@@ -1,30 +1,51 @@
 # Contribution Guidelines
 
-Unfortunately, not every library/tool/framework can be considered. The aim of the list is to provide a concise list of noteworthy modern software. This means that suggested software is either
+Unfortunately, not every library/tool/framework can be considered. This list aims to provide a concise list of noteworthy modern software. This means that suggested software is:
 
-(a) widely recommended regardless of personal opinion
+(a) widely recommended, regardless of personal opinion
 
 (b) highly discussed in the community due to its innovative nature
 
 (c) absolutely unique in its approach and function
 
 (d) a niche product that fills a gap
 
-Self-promotion is frowned upon and will be reviewed critically but the suggestion will of course be approved if they criteria match.
+Suggested software must also be developer-friendly, which means it meets the following criteria:
 
-If a certain entry does not get accepted, you should first look if there has been a discussion before. These discussions are in the issue section and normally marked with the question tag. If there hasn't been such a topic, you are free to create a new issue tagged as question.
+(i) If an open source _application_, it is licensed under one of the open source licenses listed on https://opensource.org/licenses.
 
+(ii) If an open source _library_, it is licensed under one of the open source licenses listed on https://opensource.org/licenses, with the exception of GPL and AGPL (due to their viral nature).
+
+(iii) If commercial, it has clear pricing and at least one free tier.
+
+(iv) It has a documentation in the English language.
+
+## Pull Requests
+
+There are two required criteria for a pull request:
+
+1. If an entry has a similar scope as other entries in the same category, the description must state the unique features that distinguishes it from the other entries.
+
+2. If an entry does not meet conditions _(a)_ to _(d)_ there has to be an explanation either in the description or the pull request why it should be added to the list.
+
+3. If an entry doesn't fit any of the pre-existing specialized sections, it should go under Miscellaneous.
+
+4. If two or more entries in Miscellaneous are in the same domain, then they can be moved to a new specialized section.
+
+Self-promotion is frowned upon and viewed critically, but your suggestion will of course be approved if the criteria match.
+
+If your entry isn't accepted, please check the [Issues](https://github.com/akullpp/awesome-java/issues) for items marked with the "question" tag to see if it had been previously discussed. If nothing comes up, feel free to create a new issue, adding the "question" tag.
 
 Furthermore, please ensure your pull request follows the following guidelines:
 
-* Please search previous suggestions before making a new one, as yours may be a duplicate.
-* Please make an individual pull request for each suggestion.
-* Use the following format for libraries: \[LIBRARY\]\(LINK\) - DESCRIPTION.
-* Entries should be sorted in ascending alphabetical order, i.e. a to z.
-* New categories, or improvements to the existing categorization are welcome.
-* Keep descriptions short, simple and unbiased. 
-* End all descriptions with a full stop/period.
-* Check your spelling and grammar.
-* Make sure your text editor is set to remove trailing whitespace.
+- Please search previous suggestions before making a new one, as yours may be a duplicate.
+- Please make an individual pull request for each suggestion.
+- Use the following format for libraries: \[LIBRARY\]\(LINK\) - DESCRIPTION.
+- Entries should be sorted in ascending alphabetical order, i.e. a to z.
+- New categories or improvements to the existing categorization are welcome.
+- Keep descriptions short, simple and unbiased.
+- End all descriptions with a full stop/period.
+- Check your spelling and grammar.
+- Make sure your text editor is set to remove trailing whitespace.
 
 Thank you for your suggestions!

LICENSE.md

@@ -0,0 +1 @@
+[CC-BY-SA-4.0](https://creativecommons.org/licenses/by-sa/4.0/legalcode)