Include AI usage policy in application guidelines

[koppor]

User description

Twin PR: JabRef/jabref#14889

---

PR Type

Enhancement, Documentation

---

Description

• Add AI usage policy section referencing JabRef's AI_USAGE_POLICY.md

• Clarify that AI-generated proposals will be rejected

• Improve proposal guidance with clearer section headers

• Enhance personal information and biographical sections

---

Diagram Walkthrough

flowchart LR
  A["Application Guidelines"] --> B["AI Usage Policy Section"]
  B --> C["Reference AI_USAGE_POLICY.md"]
  B --> D["Reject AI-generated proposals"]
  A --> E["Enhanced Section Headers"]
  E --> F["Personal Information"]
  E --> G["Biographical Information"]

Loading

File Walkthrough

Relevant files

Documentation

2025-12-24-application.md Add AI usage policy and improve section clarity                    _posts/2025-12-24-application.md Added new "AI usage" section with policy reference and rejection criteria Clarified that proposals predominantly generated by AI will be rejected Added introductory text to "Personal Information" section Added introductory text to "Biographical information" section Refined proposal quality language to emphasize understanding and project completion +11/-1

---

[qodo-free-for-open-source-projects]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-free-for-open-source-projects]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	Improve professionalism and clarity of text Rephrase the "AI usage" section to be more professional and welcoming by removing confrontational language and improving clarity. _posts/2025-12-24-application.md [32-34] -See [AI_USAGE_POLICY.md](https://github.com/JabRef/jabref/blob/main/AI_USAGE_POLICY.md) of JabRef for the AI usage policy in place for JabRef. -You need to follow that policy. If you don't want, JabRef is not the right place to be. -If a proposal is predominantly generated by AI, it will be rejected. +Please review JabRef's [AI Usage Policy](https://github.com/JabRef/jabref/blob/main/AI_USAGE_POLICY.md). +Adherence to this policy is mandatory. +Proposals that are predominantly generated by AI will be rejected. Apply / Chat Suggestion importance[1-10]: 6 __ Why: The suggestion correctly identifies a confrontational tone and repetitive phrasing in the newly added text, proposing a more professional and welcoming alternative which improves the quality of the document for prospective applicants.	Low
	Improve sentence conciseness and clarity Improve conciseness by replacing the redundant phrase "to both work on the project and finish it" with "to successfully complete the project". _posts/2025-12-24-application.md [36] -All in all, your proposal should reflect that you know what you are talking about and that you have the sufficient knowledge, interest and energy to both work on the project and finish it. +All in all, your proposal should reflect that you know what you are talking about and that you have the sufficient knowledge, interest, and energy to successfully complete the project. Apply / Chat Suggestion importance[1-10]: 4 __ Why: The suggestion correctly identifies a redundancy in the phrase "to both work on the project and finish it" and offers a more concise and impactful alternative, improving the overall quality of the text.	Low
More