Comments (1)
Sorry I missed this, let me clarify.
The motivation behind exploring changing the repo structure was that the teams developing BTP 1.1 integrations were doing so in isolation. It was raised that one driving reason for this isolation was the repo structure.
We have addressed this issue of isolation in the ICON Bridge repo. It did not require any changes to the folder structure. In fact, nothing we did was specific to this project. What we did change was the following:
- Issue tracker is public on GitHub. This way, everyone knows what's going on. We also use Zenhub for project management. The tools themselves are not important. The important thing here is that the issues are publicly shared and that the ongoing development is clear to everyone. Security issues are still private.
- Issues are triaged and expect a certain level of detail. There are some templates to assist with this.
- Clear guidelines for development, architecture records, and contributing.
- A number of static CI checks that come free with open source. These include CodeQL, OpenSSF Scorecards, Codecov, and Dependency Review.
- Scheduled releases. We found that it is easier to do a release train when multiple teams are collaborating on the same project. Effectively this just means that on the last Monday of every month, we tag a new release. Hotfixes are still adhoc.
- Trunk based development with branch protection rules.
main
is the only long-lived branch, and requires submitting a pull request that has 1 reviewer and 1 approver to merge tomain
. Designated codeowners, PR templates, and PR linting assists with this. - Architecture design records and clear documentation for the API, how to build, and how to run tests. This is still being drafted and is going to make its way to the
docs
folder as .md files pretty soon. Note that the API documentation should just be in the code itself, as described in the development guidelines.
The only changes I anticipate we would make to the folder structure are for the purpose of making provisioning
easier, cleaning up unused code, and moving common
to its own package. I want to be clear - my entire intent was to get the integration teams on the same page, stop independently working on the same issues, and improve developer effectiveness overall. It ended up having nothing to do with folder structure.
Again, sorry this never got to you. If you are ever left wondering what's going on or have frustrations, please just ping me directly.
from btp-product.
Related Issues (20)
- Message Broker in Java HOT 1
- Message Broker in Rust HOT 2
- BMC in Solidity HOT 2
- Call Service in Java
- Call Service in Solidity HOT 4
- Call Service in Rust
- BMR Core Module
- Example Call to Call Service Contract HOT 1
- BTP Whitepaper HOT 2
- BTP Fee Auction System
- Making draft of rules for managing BTP repositories HOT 1
- Integration for BTP Block (BTP2.0)
- Implement BTP Blocks on GOLOOP HOT 2
- Sample Node for RELAY
- BMR Relay Components for BTP Block HOT 1
- Java BMV for BTP Block
- Solidity BMV for BTP Block HOT 1
- xCall Fee Structure HOT 1
- Survey for adding IBC Module to GOLOOP
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from btp-product.