diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index 10366d14..be3eb01d 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -14,7 +14,7 @@ jobs: uses: actions/checkout@v2 - name: Build Docker image - run: docker build -t docker.pkg.github.com/pinnacle-labs/tzgo/tzcompose . + run: docker build -t docker.pkg.github.com/TezosTaqueria/tzgo/tzcompose . - name: Login to GitHub Packages uses: docker/login-action@v1 @@ -24,4 +24,4 @@ jobs: password: ${{ secrets.GITHUB_TOKEN }} - name: Push Docker image to GitHub Packages - run: docker push docker.pkg.github.com/pinnacle-labs/tzgo/tzcompose + run: docker push docker.pkg.github.com/TezosTaqueria/tzgo/tzcompose diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index a2538e3e..00000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,65 +0,0 @@ -# Contributing to tzGO - -We welcome all contributions to tzGO, be it extensions, bug fixes, documentation, or examples. This document outlines some of the conventions we put in place to keep the work on tzGO tidy and fun. - -Before you start, please **read** and **sign** our Contributor License Agreement and send it to license@blockwatch.cc: - -- use the [Individual CLA](https://github.com/blockwatch-cc/CLA/blob/master/ICLA.pdf) if you are an independent developer -- use the [Corporate CLA](https://github.com/blockwatch-cc/CLA/blob/master/CCLA.pdf) if you work for a company - -The CLA is meant to protect you and us from legal trouble. - -If you need any help or mentoring getting started or making a PR, please ask on [Discord](https://discord.gg/D5e98Hw). - - -## Contribution flow - -This is a rough outline of what our contributor's workflow looks like: - -- Create a Git branch from where you want to base your work. This is usually master. -- Write code, add test cases (optional right now), and commit your work (see below for message format). -- Run tests and make sure all tests pass (optional right now). -- Push your changes to a branch in your fork of the repository and submit a pull request. -- Your PR will be reviewed by a maintainer, who may request some changes. - * Once you've made changes, your PR must be re-reviewed and approved. - * If the PR becomes out of date, you can use GitHub's 'update branch' button. - * If there are conflicts, you can rebase (or merge) and resolve them locally. Then force push to your PR branch. - You do not need to get re-review just for resolving conflicts, but you should request re-review if there are significant changes. -- A maintainer will test and merge your pull request. - -Thanks for your contributions! - -### Format of the commit message - -We follow a rough convention for commit messages that is designed to answer two -questions: what changed and why. The subject line should feature the what and -the body of the commit should describe the why. - -``` -rpc: add Granada constants - -Blocks were counting all rewards and deposits including endorsements, -which was confusing and unclear what part was going to the block baker. -This update changes the rewards and deposits fields to only count -amounts related to baking. -``` - -The format can be described more formally as follows: - -``` -: - - - -Signed-off-by: -``` - -The first line is the subject and should be no longer than 50 characters, the other lines should be wrapped at 72 characters (see [this blog post](https://preslav.me/2015/02/21/what-s-with-the-50-72-rule/) for why). - -The body of the commit message should describe why the change was made and at a high level, how the code works. - -### Signing off the Commit - -The project uses [DCO check](https://github.com/probot/dco#how-it-works) and the commit message must contain a `Signed-off-by` line for [Developer Certificate of Origin](https://developercertificate.org/). - -Use option `git commit -s -m 'This is my commit message'` to sign off your commits. diff --git a/LICENSE.md b/LICENSE.md index aebb0a81..21933c30 100644 --- a/LICENSE.md +++ b/LICENSE.md @@ -1,4 +1,7 @@ -The MIT License (MIT) Copyright (c) 2021-2023 Blockwatch Data Inc. +The MIT License (MIT) + +Copyright (C) 2024 Michael Weichert & Taqueria Contributors +Copyright (C) 2021-2023 Blockwatch Data Inc. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/README.md b/README.md index 7d7bddf6..f3492e00 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ > Note: From Tezos Paris onwards development of TzGo has moved to https://github.com/trilitech/tzgo. This repository is kept as a public archive for older versions. Please update your import paths. -TzGo is [Blockwatch](https://blockwatch.cc)'s low-level Tezos Go SDK for reliable, high-performance applications. This SDK is free to use in commercial and non-commercial projects with a permissive license. Blockwatch is committed to keeping interfaces stable, providing long-term support, and updating TzGo on a regular basis to stay compliant with the most recent Tezos network protocol. +TzGo is a low-level Tezos Go SDK for reliable, high-performance applications. This SDK is free to use in commercial and non-commercial projects with a permissive license. Trilitech is committed to keeping interfaces stable, providing long-term support, and updating TzGo on a regular basis to stay compliant with the most recent Tezos network protocol. TzGo's main focus is on **correctness**, **stability**, and **compliance** with Tezos mainnet. It supports binary and JSON encodings for all Tezos types including Micheline smart contract data and all transaction formats. It's an ideal fit for high-performance applications that read from and write to the Tezos blockchain.