Thank you for your interest in contributing! This community resource depends on contributions to stay current and comprehensive.
New documents:
- Federal or state/territory AI security policies
- Sector-specific guidance
- International frameworks for comparison
Updates:
- New versions of existing documents
- Changed URLs or broken links
- Corrections to dates or descriptions
- Identify connections between frameworks
- Document dependencies and references
- Map compliance pathways
- Additional jurisdictions
- Updates to existing comparisons
- Emerging international standards
- Compliance checklists
- Assessment tools
- Visualisations
- Query interfaces for knowledge graph
Best for:
- Reporting errors
- Suggesting additions
- Requesting clarification
Process:
- Check existing issues for duplicates
- Create new issue with descriptive title
- Use appropriate label:
document-update- New or updated documentscorrection- Errors in existing contentenhancement- New features or sectionsquestion- Clarification needed
Best for:
- Adding content
- Fixing errors
- Improving documentation
Process:
- Fork the repository
- Create feature branch (
git checkout -b feature/add-new-framework) - Make changes following style guide below
- Commit with clear message
- Push to your fork
- Create Pull Request
When adding a new document to the inventory:
| **[Document Title](URL)** | Month Year | Status | Scope | Key requirements or focus |Status indicators:
- Mandatory - Legal or policy requirement
- Sector-Specific - Binding for specific industries
- Voluntary - Guidance/best practice
- Use Month Year format (e.g., "December 2025")
- For ongoing/updated documents, note "Updated Month Year"
- Link directly to official source
- Prefer .gov.au over third-party summaries
- Check links work before submitting
Use consistent abbreviations:
- Federal (no abbreviation)
- NSW, VIC, QLD, SA, WA, TAS, NT, ACT
- Use ATX-style headers (
#,##,###) - One blank line between sections
- Tables should be properly formatted
- Code blocks with appropriate language tags
When adding a new jurisdiction or major section:
## [Jurisdiction/Topic Name]
### Overview
Brief description of the framework/approach.
### Key Documents
| Document | Date | Status | Scope | Key Requirements |
|----------|------|--------|-------|------------------|
| **[Name](URL)** | Date | Status | Scope | Description |
### Governance Bodies
**[Body Name]:**
- Role and function
- Contact information
### Notes
Any additional context or considerations.Before submitting:
- Accuracy - Verify against official sources
- Currency - Check for newer versions
- Links - Ensure URLs work
- Format - Follow style guide
- Completeness - Include all relevant details
- Constructive feedback only
- No personal attacks
- Assume good intent
- Cite sources
- Verify before submitting
- Acknowledge uncertainty
- Answer questions when you can
- Share knowledge generously
- Welcome newcomers
- Triage - Maintainers review within 1 week
- Review - Content checked for accuracy
- Feedback - Changes requested if needed
- Merge - Approved contributions merged
- Credit - Contributors acknowledged
Contributors are recognised in:
- Commit history
- Release notes
- Annual acknowledgements (for significant contributions)
- Open an issue with
questionlabel - Contact maintainers via LinkedIn
- Join discussions in Issues
Ben Kereopa-Yorke
Senior AI Security Specialist | OWASP ML Security Top 10 Co-Lead
Thank you for helping make Australian AI Security more visible and accessible!