Our Team

The development of Nexios is guided by an experienced team of developers who are passionate about building fast, clean, and developer-friendly web frameworks. The project thrives thanks to contributions from our amazing community.

Core Team

The core development team behind Nexios.

Dunamix

Creator | Lead Developer

Core architect and maintainer of Nexios. Focused on async performance and clean architecture.

Sponsor

Maintainers

Active maintainers helping to ensure Nexios's continued development and success.

Mohammed Al-Ameen

Core Developer

Leads database integration and authentication systems development.

Team & Community ​

Core Team ​

The Nexios framework is maintained by a dedicated team of developers committed to building a modern, high-performance Python web framework.

Core Maintainers ​

Working Groups ​

Contributing ​

Getting Started ​

1. Fork the repository
2. Clone your fork
3. Create a virtual environment
4. Install dependencies
5. Create a branch
6. Make changes
7. Run tests
8. Submit PR

Development Setup ​

# Clone repository
git clone https://github.com/your-username/nexios.git
cd nexios

# Create virtual environment
python -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate

# Install dependencies
pip install -e ".[dev]"

# Clone repository
git clone https://github.com/your-username/nexios.git
cd nexios

# Install dependencies
poetry install

# Activate environment
poetry shell

Running Tests ​

# Run all tests
pytest

# Run specific test file
pytest tests/test_routing.py

# Run with coverage
pytest --cov=nexios

# Run with parallel execution
pytest -n auto

Code Style ​

We use:

• Black for code formatting
• isort for import sorting
• flake8 for linting
• mypy for type checking

# Format code
black nexios tests

# Sort imports
isort nexios tests

# Run linter
flake8 nexios tests

# Type check
mypy nexios

Git Workflow ​

1. Create feature branch

git checkout -b feature/your-feature

2. Make changes and commit

git add .
git commit -m "feat: add new feature"

3. Push changes

git push origin feature/your-feature

4. Create pull request

Commit Messages ​

We follow the Conventional Commits specification:

• feat: New feature
• fix: Bug fix
• docs: Documentation
• style: Code style
• refactor: Code refactoring
• perf: Performance
• test: Tests
• chore: Maintenance

Community ​

Communication Channels ​

• Discord Server
• GitHub Discussions
• Stack Overflow
• Twitter

Support ​

Code of Conduct ​

We are committed to providing a welcoming and inclusive environment. All participants must follow our Code of Conduct.

Key points:

• Be respectful
• Be inclusive
• Be collaborative
• Be professional
• Report issues

Recognition ​

Contributors ​

Thank you to all our contributors! See the Contributors page.

Sponsors ​

Support Nexios development:

• GitHub Sponsors
• Open Collective

Events ​

Community Calls ​

• Monthly community calls
• Project updates
• Feature discussions
• Q&A sessions
• Live coding

Workshops ​

We regularly organize workshops:

• Getting started
• Advanced features
• Best practices
• Performance tuning
• Security

Project Governance ​

Decision Making ​

1. RFC Process

   • Submit proposal
   • Community discussion
   • Core team review
   • Implementation

2. Issue Tracking

   • Bug reports
   • Feature requests
   • Enhancements
   • Documentation

3. Release Process

   • Version planning
   • Release candidates
   • Testing
   • Documentation
   • Announcement

Working Groups ​

Security ​

The security working group:

• Reviews security issues
• Implements security features
• Conducts audits
• Manages vulnerabilities
• Updates best practices

Documentation ​

The documentation working group:

• Maintains docs
• Creates tutorials
• Reviews contributions
• Updates examples
• Improves accessibility

Performance ​

The performance working group:

• Conducts benchmarks
• Optimizes code
• Improves scalability
• Monitors metrics
• Updates guidelines

Roadmap ​

Current Focus ​

1. Performance Optimization

   • Request handling
   • Database operations
   • Caching system
   • Memory usage

2. Security Enhancements

   • Authentication options
   • Authorization system
   • Security headers
   • CSRF protection

3. Developer Experience

   • CLI improvements
   • Debug tools
   • Error messages
   • Documentation

Future Plans ​

1. Short Term (3-6 months)

   • GraphQL support
   • WebSocket improvements
   • Database integrations
   • Testing tools

2. Medium Term (6-12 months)

   • Serverless support
   • gRPC integration
   • Plugin system
   • Admin interface

3. Long Term (12+ months)

   • Edge computing
   • AI integration
   • Cloud native features
   • Enterprise features

Get Involved ​

Ways to Contribute ​

1. Code Contributions

   • Fix bugs
   • Add features
   • Improve performance
   • Write tests

2. Documentation

   • Fix errors
   • Add examples
   • Write tutorials
   • Improve clarity

3. Community Support

   • Answer questions
   • Review PRs
   • Report bugs
   • Share knowledge

4. Advocacy

   • Write blog posts
   • Give talks
   • Share experiences
   • Create content

Contact ​

• Email: team@nexios.dev
• Discord: Join Server
• Twitter: @nexiosframework
• GitHub: nexios/nexios