Skip to content

Commit

Permalink
Update
Browse files Browse the repository at this point in the history
  • Loading branch information
einar-hjortdal committed Sep 15, 2024
1 parent f742333 commit c5e5e50
Show file tree
Hide file tree
Showing 2 changed files with 42 additions and 31 deletions.
31 changes: 24 additions & 7 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,19 +7,36 @@ Please follow these standards
1. Fork the project and clone your fork to your development environment
2. Add the original repository as an additional git remote called "upstream"
3. Create a new branch
- The branch called production is the branch that goes live
- The branch called meester is the branch used for development
- Feature (feat_) branches are branched off and then merged into meester once features are bug-free
- Release (rele_) branches are branched off meester and then merged into production
- Bug fix (bugf_) branches are branched off production and then merged into both production, release
and meester
- The branch called `live` is the branch that goes live.
- The branch called `pending` is the branch used for changes that are pending to go live.
- New features are branched from `live` and merged into `pending` when ready.
- Bug fixes are branched from `live` and then merged into both `live` and `pending`.

4. Write your code, test it and make sure it works
5. Commit your changes
6. Pull the latest code from upstream into your branch

Make sure your changes do not conflict with the original repository.
Make sure your changes do not conflict with the original repository.

7. Push changes to the remote "origin" (your repository)
8. Create a pull request
- If the pull request addresses an issue, tag the related issue

## V

- No enums.
- No logical assignment operators.
- No static methods.
- No `@[required]` attribute in struct definitions, always manually check values to return adequate
error messages.
- For consistency, use `arrays.concat` over `<<` to concatenate items to an array.
- Always use `fn (a int, b int) bool { return a > b }` over `|a, b| a > b`

### FirebirdSQL

- Uppercase for keywords, data types. Lowercase all other identifiers.
- Use `REAL` and `DOUBLE PRECISION` for floating point types.
- Use `CHAR` for strings with expected exact lengths.
- Use `VARCHAR` for strings with expected maximum lengths, for strings with default values, and for
strings that are in an `INDEX` or `UNIQUE` constraint.
- Use `TEXT` for unknown-length strings.
42 changes: 18 additions & 24 deletions LICENSE.md
Original file line number Diff line number Diff line change
@@ -1,32 +1,26 @@
University of Illinois/NCSA Open Source License

Copyright (c) 2023 Coachonko. All rights reserved.
Copyright (c) 2023 Einar Hjortdal. All rights reserved.

Developed by: Coachonko and the sterniana community
Developed by: Einar Hjortdal and the Chiadenis community

Permission is hereby granted, free of charge, to any person
obtaining a copy of this software and associated documentation files
(the "Software"), to deal with the Software without restriction,
including without limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal with the Software without restriction, including without
limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following
conditions:

* Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimers.
* Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimers.

* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimers in the
documentation and/or other materials provided with the distribution.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions
and the following disclaimers in the documentation and/or other materials provided with the distribution.

* Neither the names of Coachonko, sterniana nor the names of its
contributors may be used to endorse or promote products derived from
this Software without specific prior written permission.
* Neither the names of Einar Hjortdal, Chiadenis nor the names of its contributors may be used to endorse
or promote products derived from this Software without specific prior written permission.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS WITH
THE SOFTWARE.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS WITH THE SOFTWARE.

0 comments on commit c5e5e50

Please sign in to comment.