dbzero 0.6.1__tar.gz → 0.6.2__tar.gz

dbzero-0.6.2/CLA.md

@@ -0,0 +1,133 @@
+# Contributor License Agreement (CLA)
+
+## dbzero Contributor License Agreement
+
+This Contributor License Agreement ("Agreement") is entered into by the party signing below ("You" or "Contributor"), and conveys certain license rights to the dbzero project maintainers ("We," "Us," or "Project") for Your contributions to dbzero.
+
+### 1. Definitions
+
+**"We," "Us," "Our"** means Wojciech Sebastian Kozlowski and his successors or assigns
+
+**"Contribution"** means any original work of authorship, including any modifications or additions to an existing work, that You intentionally submit to Us for inclusion in the dbzero project, in any form (source code, documentation, configuration files, etc.).
+
+**"Submit"** means any form of electronic, verbal, or written communication sent to Us or our representatives, including but not limited to communication on electronic mailing lists, source code control systems, issue tracking systems, and pull requests.
+
+**"dbzero"** means the dbzero Community Edition software project and all associated repositories, documentation, and materials.
+
+### 2. Grant of Rights
+
+#### 2.1 Copyright License
+You hereby grant to Us and to recipients of software distributed by Us a perpetual, worldwide, non-exclusive, royalty-free, irrevocable copyright license to:
+- Reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works in source code or object code form
+- Sublicense the above rights to third parties under any license terms, including proprietary or commercial licenses
+
+#### 2.2 Patent License
+You hereby grant to Us and to recipients of software distributed by Us a perpetual, worldwide, non-exclusive, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer Your Contributions, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the work to which such Contribution(s) was submitted.
+
+If any entity institutes patent litigation against You, Us, or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that Your Contribution, or the work to which You have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or work shall terminate as of the date such litigation is filed.
+
+#### 2.3 Outbound License
+Based on the grants of rights in Sections 2.1 and 2.2, if We include Your Contribution in the dbzero project:
+- Your Contribution will be licensed to the public under LGPL-2.1-or-later as part of the dbzero project
+- We reserve the right to also license Your Contribution under alternative licenses without any additional compensation to You, including proprietary licenses for commercial or other purposes
+
+#### 2.4 Moral Rights
+To the fullest extent permitted under applicable law, You waive and agree not to assert any moral rights You may have in Your Contributions. In jurisdictions where moral rights cannot be waived, You agree not to assert such rights in a manner that would interfere with Our exercise of the licensed rights.
+
+### 3. Representations and Warranties
+
+You represent and warrant that:
+
+#### 3.1 Authority
+You are legally entitled to grant the above licenses. If You are an individual and Your employer(s) has rights to intellectual property that You create that includes Your Contributions, You represent that:
+- You have received permission from Your employer to make Contributions on behalf of that employer, OR
+- Your employer has waived such rights for Your Contributions to the dbzero project, OR
+- Your Contributions were created entirely on Your own time using Your own equipment and do not relate to Your employer's business
+
+#### 3.2 Originality
+Each of Your Contributions is Your original creation. You represent that Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which You are personally aware and which are associated with any part of Your Contributions.
+
+#### 3.3 No Conflicts
+To Your knowledge, Your Contribution does not violate any third party's copyrights, trademarks, patents, or other intellectual property rights.
+
+### 4. No Obligation to Use
+
+You understand and agree that:
+- The Project has no obligation to accept, include, or use any Contribution
+- The decision to include any Contribution in any Project release is entirely at the discretion of the Project maintainers
+- Your Contribution may be modified, replaced, or removed from the Project codebase at any time for any reason as a result of future changes or technical decisions
+- If We do not include Your Contribution, all rights granted under Section 2 revert to You, except for any derivatives that were created during review
+
+### 5. Disclaimer of Warranty
+
+Your Contributions are provided "as is," without warranties or conditions of any kind, either express or implied, including, without limitation, any warranties or conditions of title, non-infringement, merchantability, or fitness for a particular purpose.
+
+### 6. Copyright Ownership and Reuse
+
+You retain ownership of the copyright in Your Contributions. Nothing in this Agreement transfers copyright ownership to the Project. You are free to use Your Contributions for any purpose, including in projects outside of dbzero.
+
+### 7. Notification and Remediation
+
+**7.1 Duty to Notify**
+You agree to notify Us promptly in writing if:
+- You become aware that any representation in Section 3 was inaccurate when made, OR
+- A third party makes a claim against Your Contribution
+
+Such notification should include credible evidence supporting the claim.
+
+**7.2 Consequences of Inaccuracy**
+If the Project determines that a representation in Section 3 was materially inaccurate:
+- The licenses granted in Section 2 for affected Contributions may be revoked prospectively upon written notice
+- The Project will remove affected Contributions from future releases
+- You agree to cooperate in remediation, including potentially re-licensing corrected Contributions
+- This does not affect licenses already granted for past releases that included the Contribution in good faith
+- You remain responsible for any damages caused by breach of Your warranties
+
+### 8. Scope of Agreement
+
+This Agreement applies to all Contributions You submit to the dbzero project on or after the date You accept this Agreement. Each Contribution You submit is subject to the terms of this Agreement.
+
+### 9. Effective Date and Duration
+
+This Agreement becomes effective on the date You accept it. You may stop making Contributions at any time. However, the licenses granted in Section 2 for Contributions You have already made are irrevocable and will remain in effect even if You stop contributing.
+
+### 10. Limitation of Liability
+
+To the maximum extent permitted by applicable law:
+
+**For Contributors:**
+In no event shall You be liable for any indirect, incidental, special, consequential, or punitive damages arising from this Agreement, except for:
+- Willful misconduct or gross negligence
+- Fraudulent misrepresentation in Section 3
+- Breach of confidentiality obligations (if any)
+
+**For the Project:**
+In no event shall the Project be liable to You or other parties for any damages arising from acceptance, rejection, modification, or removal of Your Contributions.
+
+This does not limit liability that cannot be excluded or limited under applicable law.
+
+### 11. Severability
+
+If any provision of this Agreement is held to be invalid or unenforceable, the remaining provisions shall remain in full force and effect, and the invalid provision shall be modified to the minimum extent necessary to make it valid and enforceable.
+
+---
+
+## How to Accept This Agreement
+
+This CLA is accepted when you click "I Agree" through CLA Assistant on your first pull request.
+
+By accepting this Agreement, you acknowledge that you have read, understood, and agree to be bound by its terms and conditions for all your current and future Contributions to dbzero.
+
+---
+
+## Contact
+
+**Questions?** If you have questions about this CLA, please open an issue on GitHub before contributing.
+
+**Corporate CLA:** If you need a Corporate Contributor License Agreement, please contact the project maintainers.
+
+---
+
+**Version:** 1.0  
+**Last Updated:** December 29, 2025
+**Maintained by:** Wojciech Sebastian Kozlowski

dbzero-0.6.2/CONTRIBUTING.md

@@ -0,0 +1,371 @@
+# Contributing to dbzero
+
+Thank you for your interest in contributing to dbzero! We welcome contributions from the community and are grateful for your support.
+
+## Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Getting Started](#getting-started)
+- [Development Setup](#development-setup)
+- [How to Contribute](#how-to-contribute)
+- [Coding Standards](#coding-standards)
+- [Testing Guidelines](#testing-guidelines)
+- [Commit Message Guidelines](#commit-message-guidelines)
+- [Pull Request Process](#pull-request-process)
+- [Reporting Bugs](#reporting-bugs)
+- [Suggesting Enhancements](#suggesting-enhancements)
+- [Documentation](#documentation)
+- [Contributor License Agreement](#contributor-license-agreement)
+- [License](#license)
+
+## Code of Conduct
+
+This project adheres to a code of conduct that all contributors are expected to follow. Please be respectful, inclusive, and considerate in all interactions.
+
+## Getting Started
+
+1. **Fork the repository** on GitHub
+2. **Clone your fork** locally:
+   ```bash
+   git clone https://github.com/YOUR_USERNAME/dbzero.git
+   cd dbzero
+   ```
+3. **Add the upstream repository** as a remote:
+   ```bash
+   git remote add upstream https://github.com/dbzero-software/dbzero.git
+   ```
+
+## Development Setup
+
+### Prerequisites
+
+- C++ compiler (GCC 13+ or Microsoft C/C++ Optimizing Compiler 19.41+)
+- Meson
+- Ninja build system
+- Git
+- Python 3.9 or higher (for Python components and tooling)
+- A virtual environment tool (venv, virtualenv, or conda) for Python dependencies
+
+### Setting Up Your Environment
+
+1. **Build the C++ components**:
+   ```bash
+   # Build debug version without tests
+   ./scripts/build.sh
+   
+   # Build debug version with tests
+   ./scripts/build.sh -t
+   
+   # Build release version
+   ./scripts/build.sh -r
+   
+   # Build release version with tests
+   ./scripts/build.sh -r -t
+   ```
+   
+   Alternatively, you can use Meson directly:
+   ```bash
+   meson setup build
+   meson compile -C build
+   ```
+
+2. **Create a Python virtual environment** (for Python components):
+   ```bash
+   python -m venv venv
+   source venv/bin/activate  # On Windows: venv\Scripts\activate
+   ```
+
+3. **Install Python dependencies**:
+   ```bash
+   pip install -r requirements.txt  # Install dependencies
+   ```
+
+4. **Verify the installation**:
+   ```bash
+   # Run C++ tests (debug build)
+   ./build/debug/testsD.x
+   
+   # Run C++ tests (release build)
+   ./build/release/tests.x
+   
+   # Or use Meson test runner
+   meson test -C build
+   
+   # Run Python tests (excludes stress tests)
+   ./scripts/run_tests.sh
+   
+   # Run Python tests in parallel
+   ./scripts/run_tests.sh -j 6
+   
+   # Run specific Python test
+   ./scripts/run_tests.sh -k=test_name
+   
+   # Run stress tests only (takes longer)
+   ./scripts/run_stress_tests.sh
+   
+   # Run specific stress test
+   ./scripts/run_stress_tests.sh -k=test_name
+   ```
+
+## How to Contribute
+
+### Types of Contributions
+
+We welcome various types of contributions:
+
+- **Bug fixes** - Fix issues and improve stability
+- **New features** - Add new functionality
+- **Documentation** - Improve or add documentation
+- **Tests** - Add or improve test coverage
+- **Performance improvements** - Optimize existing code
+- **Code refactoring** - Improve code quality and maintainability
+
+### Finding Something to Work On
+
+- Check the [issue tracker](https://github.com/dbzero-software/dbzero/issues) for open issues
+- Look for issues labeled `good first issue` or `help wanted`
+- Review the roadmap and feature requests
+- If you have a new idea, open an issue to discuss it first
+
+## Coding Standards
+
+### C++ Style Guide (Primary)
+
+Since the project is predominantly C++ (85%), these are our primary coding standards:
+
+- Follow **Modern C++** best practices
+- Use **meaningful variable and function names** with clear intent
+- Follow **RAII principles** for resource management
+- Prefer **smart pointers** over raw pointers
+- Use **const correctness** throughout
+- Keep functions small and focused on a single task
+- Maximum line length: 120 characters
+
+#### C++ Code Quality
+
+- **Naming Conventions**:
+  - Classes/Structs: `PascalCase`
+  - Functions/Methods: `camelCase`
+  - Variables: `snake_case`
+  - Constants: `UPPER_SNAKE_CASE`
+  - Namespaces: `lowercase`
+
+- **Documentation**: Use Doxygen-style comments for all public APIs
+  ```cpp
+  /**
+   * @brief Brief description of the function
+   * @param param1 Description of parameter
+   * @return Description of return value
+   */
+  ```
+
+- **Error Handling**: Use exceptions for exceptional cases, return values for expected errors
+- **Comments**: Write clear comments for complex logic, algorithms, and non-obvious decisions
+- **DRY Principle**: Extract common code into reusable functions and templates
+
+### Python Style Guide (Additional)
+
+For the Python components (~15% of the project):
+
+- Follow [PEP 8](https://www.python.org/dev/peps/pep-0008/) style guidelines
+- Use meaningful variable and function names
+- Keep functions small and focused on a single task
+- Maximum line length: 100 characters
+
+#### Python Code Quality
+
+- **Type hints**: Use type annotations where appropriate
+- **Docstrings**: Document all public modules, functions, classes, and methods using NumPy style
+- **Comments**: Write clear comments for complex logic
+- **DRY principle**: Extract common code into reusable functions
+
+## Testing Guidelines
+
+### Writing Tests
+
+- Write tests for all new features and bug fixes
+- Aim for high test coverage (>80%)
+- Use descriptive test names that explain what is being tested
+- Keep tests independent and isolated
+
+### C++ Testing
+
+We use Google Test (gtest) for C++ unit tests:
+
+```cpp
+TEST(TestSuiteName, TestName) {
+    // Arrange
+    auto test_data = SetupTestData();
+    
+    // Act
+    auto result = FunctionUnderTest(test_data);
+    
+    // Assert
+    EXPECT_EQ(result, expected_value);
+    ASSERT_TRUE(condition) << "Error message if fails";
+}
+```
+
+## Commit Message Guidelines
+
+Write clear and meaningful commit messages explaining scope and purpose of changes you are making.
+If your contributions are related to a submitted issue on the github repository, please include issue number(s) at the beginning of the commit message.
+
+## Pull Request Process
+
+### Before Submitting
+
+1. **Update your fork** with the latest upstream changes:
+   ```bash
+   git fetch upstream
+   git rebase upstream/main
+   ```
+
+2. **Create a feature branch**:
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+
+3. **Make your changes** following the coding standards
+
+4. **Add tests** for your changes
+
+5. **Run the test suite** to ensure everything passes
+
+6. **Update documentation** if needed
+
+### Submitting the Pull Request
+
+1. **Push your branch** to your fork:
+   ```bash
+   git push origin feature/your-feature-name
+   ```
+
+2. **Open a Pull Request** on GitHub with:
+   - Clear title describing the change
+   - Description of what and why
+   - Reference to related issues (e.g., "Closes #123")
+   - Screenshots or examples if applicable
+
+3. **Respond to feedback** - Be open to suggestions and make requested changes promptly
+
+### PR Review Criteria
+
+Your PR will be reviewed for:
+
+- Code quality and style compliance
+- Test coverage
+- Documentation completeness
+- Backward compatibility
+- Performance implications
+- Security considerations
+
+## Reporting Bugs
+
+### Before Reporting
+
+- Check if the bug has already been reported in the issue tracker
+- Verify the bug exists in the latest version
+- Collect relevant information about your environment
+
+### Bug Report Template
+
+When reporting bugs, please include:
+
+- **Description**: Clear description of the issue
+- **Steps to Reproduce**: Minimal steps to reproduce the problem
+- **Expected Behavior**: What you expected to happen
+- **Actual Behavior**: What actually happened
+- **Environment**:
+  - C++ compiler and version (e.g., GCC 13.3.0)
+  - dbzero version
+  - Operating system
+  - Python version (if relevant)
+  - Relevant dependencies
+- **Code Sample**: Minimal code that reproduces the issue
+- **Error Messages**: Full error messages and stack traces
+- **Screenshots**: If applicable
+
+## Suggesting Enhancements
+
+We welcome feature suggestions! When proposing enhancements:
+
+1. **Check existing issues** to avoid duplicates
+2. **Open an issue** with the `enhancement` label
+3. **Provide context**:
+   - What problem does this solve?
+   - Who would benefit from this feature?
+   - How should it work?
+   - Are there alternative approaches?
+4. **Be open to discussion** about implementation details
+
+## Documentation
+
+Good documentation is crucial. When contributing:
+
+### Code Documentation
+
+- Add docstrings to all public APIs
+- Include examples in docstrings where helpful
+- Keep documentation up-to-date with code changes
+
+### User Documentation
+
+- Update README.md for user-facing changes
+- Add tutorials or guides for new features
+- Update API reference documentation
+
+### Documentation Style
+
+- Use clear, concise language
+- Provide practical examples
+- Explain both the "how" and the "why"
+- Keep formatting consistent
+
+## Contributor License Agreement
+
+**Important**: Before your start contributing please make sure you read and agree to our Contributor License Agreement (CLA): [CLA.md](./CLA.md)
+
+### Why We Have a CLA
+
+dbzero is primarily licensed under LGPL-2.1-or-later, but we want to reserve the right to offer the software under alternative licenses to support different use cases and our business model.
+
+To enable this flexible licensing approach while maintaining our commitment to open source, we need contributors to grant us additional rights to use their contributions.
+
+### What You're Agreeing To
+
+By contributing to dbzero, you agree that:
+
+1. **Your contribution will be licensed under LGPL-2.1-or-later** in the open-source dbzero Community Edition
+2. **You grant the dbzero project maintainers** a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license to:
+   - Use, modify, and distribute your contributions in any form
+   - Include your contributions in the open-source project and any alternative licensing options we may offer
+   - Sublicense your contributions under different license terms, including proprietary licenses
+   - Create derivative works based on your contributions
+3. **You retain full copyright** to your contributions and can use them in your own projects
+4. **You confirm** that:
+   - You have the legal right to grant this license
+   - Your contribution is your original work (or properly attributed if based on others' work)
+   - Your contribution doesn't violate any third-party intellectual property rights
+
+### How It Works
+
+When you submit your first pull request:
+1. Our CLA Assistant bot will prompt you to review and accept the CLA
+2. Your acceptance is recorded (this is a one-time process)
+3. Your PR will be marked as ready for review
+4. All future contributions will be covered under the same agreement
+
+### Questions About the CLA?
+
+If you have questions or concerns about the CLA, please open an issue to discuss before contributing. We're happy to clarify any points.
+
+## License
+
+By contributing to dbzero, you agree that your contributions will be:
+- Licensed under the **GNU Lesser General Public License v2.1 or later** (LGPL-2.1-or-later) for the open-source dbzero Community Edition
+- Subject to the additional rights grant specified in our Contributor License Agreement: [CLA.md](./CLA.md)
+
+---
+
+Thank you for contributing to dbzero! Your efforts help make this project better for everyone. 🎉

dbzero-0.6.2/NOTICE

@@ -0,0 +1,59 @@
+dbzero — Community Edition
+
+Copyright (c) 2025-2026 Wojciech Sebastian Kozlowski
+
+================================================================================
+LICENSE
+================================================================================
+
+dbzero is licensed under the GNU Lesser General Public License v2.1 or later.
+See LICENSE for the full license text.
+
+This library is distributed in the hope that it will be useful, but WITHOUT
+ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more
+details.
+
+You should have received a copy of the GNU Lesser General Public License along
+with this library. If not, see <https://www.gnu.org/licenses/>.
+
+================================================================================
+
+DISTRIBUTION REQUIREMENTS
+================================================================================
+
+When redistributing this library:
+- Preserve this NOTICE file
+- Include the full LICENSE file
+- Retain all copyright and license notices
+
+================================================================================
+THIRD-PARTY COMPONENTS
+================================================================================
+
+This software includes the following third-party components:
+
+Google Test
+-----------
+Repository: https://github.com/google/googletest
+Copyright:  2008, Google Inc.
+License:    BSD-3-Clause
+Purpose:    Unit testing framework
+License File: THIRD_PARTY_LICENSES/GOOGLETEST_LICENSE
+
+Boost Intrusive Containers
+---------------------------
+Repository: https://www.boost.org/
+Copyright:  Ion Gaztanaga and other Boost contributors
+License:    Boost Software License 1.0
+Purpose:    Intrusive containers implementations
+Location:   src/dbzero/core/intrusive/
+License File: THIRD_PARTY_LICENSES/BOOST_LICENSE_1_0
+
+Note: Files in src/dbzero/core/intrusive/ are derived from Boost.Intrusive
+      and retain their original Boost Software License 1.0 with full copyright
+      notices. Some files may contain modifications by Wojciech Sebastian Kozlowski,
+      which are licensed under LGPL-2.1-or-later. See individual file headers
+      for specific copyright and licensing information.
+
+================================================================================