Why Contribute?
Security is an ever-evolving field. What works today might not be sufficient tomorrow. By contributing, you help:Keep it Current
Security best practices change as new threats emerge and tools evolve
Share Knowledge
Your experience and expertise can help others secure their servers
Fill Gaps
No single person knows everything - collaborative knowledge is stronger
Support the Community
Help fellow system administrators and security-conscious users
How to Contribute
This guide is hosted on GitHub, which makes collaboration easy. There are several ways you can contribute:Option 1: Submit a Pull Request
For substantial contributions like new sections, improvements to existing content, or code corrections:Option 2: Open an Issue
For bug reports, questions, suggestions, or if you’re not comfortable with Git:Navigate to the issues page
Go to the repository issues
Provide details
Include:
- A clear, descriptive title
- What you found or what you’re suggesting
- Steps to reproduce (for bugs)
- Your environment details (distro, version, etc.)
Even if you’re not sure something is a bug or if your idea is good, open an issue anyway! Discussion helps improve the guide.
What to Contribute
Contributions can take many forms:Content Improvements
- New sections - Cover security topics not yet in the guide
- Expanded explanations - Add more detail to existing sections
- Updated information - Keep content current with latest best practices
- Distribution-specific content - Add commands for other distros (RedHat, Arch, etc.)
Technical Updates
- Tested configurations - Share working configs for specific use-cases
- Code corrections - Fix errors in commands or scripts
- New tools - Introduce security tools not currently covered
- Alternative approaches - Suggest different ways to accomplish the same goal
Documentation Quality
- Fix typos - Grammar, spelling, and formatting corrections
- Clarify instructions - Make steps easier to follow
- Add warnings - Note potential issues or gotchas
- Better examples - Provide clearer or more relevant examples
References and Resources
- Add references - Link to official documentation or authoritative sources
- Cite best practices - Reference industry standards (CIS, NIST, etc.)
- Link to related guides - Connect to complementary resources
Contribution Guidelines
To ensure quality and consistency:Technical Accuracy
Test your contributions
Test your contributions
If you’re adding commands or configurations:
- Test them on a clean system when possible
- Note which distribution(s) you tested on
- Include any prerequisites or dependencies
- Document any potential side effects
Follow existing patterns
Follow existing patterns
Match the guide’s structure and style:
- Use the same section headings (Why, How It Works, Goals, Steps, etc.)
- Maintain consistent code formatting
- Follow the established tone (clear, practical, educational)
Explain the 'why'
Explain the 'why'
Don’t just show how to do something:
- Explain why it’s important for security
- Describe what threat or risk it addresses
- Include context for when it should or shouldn’t be used
Content Quality
Be clear and concise
Be clear and concise
- Use simple language when possible
- Break complex topics into digestible chunks
- Provide examples to illustrate concepts
- Define technical terms when first used
Cite your sources
Cite your sources
- Link to official documentation
- Reference security standards or guidelines
- Credit others’ work appropriately
- Avoid making unsubstantiated claims
Consider the audience
Consider the audience
Remember that readers:
- May be new to Linux server administration
- Come from diverse technical backgrounds
- Need practical, actionable guidance
- Want to understand, not just copy-paste
Code and Commands
- Provide working examples - All code should be tested and functional
- Include comments - Explain what complex commands do
- Show output - Include example output where helpful
- Note variations - Document how commands differ across distributions
- Backup first - Always include backup steps before destructive changes
What Makes a Good Contribution?
The best contributions:- Solve a real problem - Address actual security concerns or usability issues
- Are well-explained - Provide context and reasoning, not just commands
- Are tested - Work as described and don’t break existing functionality
- Fit the guide’s scope - Focus on practical server security for at-home/small deployments
- Are accessible - Can be understood and implemented by the target audience
Don’t worry if your contribution isn’t perfect! Maintainers can help refine it through the review process.
Repository Information
- Repository: How-To-Secure-A-Linux-Server
- Issues: Submit new issue
- License: CC-BY-SA (Creative Commons Attribution-ShareAlike)
By contributing, you agree that your contributions will be licensed under the same CC-BY-SA license as the rest of the guide.
Community Etiquette
When contributing:- Be respectful - Treat other contributors with courtesy
- Be patient - Reviews take time, especially for large contributions
- Be open to feedback - Maintainers may suggest changes to your contribution
- Be collaborative - Work together to find the best solutions
Recognition
All contributors are valued members of the community. While there’s no formal rewards program, contributors:- Are credited in pull requests and commits
- Help shape a resource used by thousands of people
- Build their knowledge and skills
- Give back to the open source community
Thank You!
Every contribution, no matter how small, makes this guide better. Your time and expertise help countless others secure their Linux servers.