jep
governance
| jep | governance | |
|---|---|---|
| 1 | 7 | |
| 142 | 36 | |
| 0.0% | - | |
| 5.3 | 8.3 | |
| about 2 months ago | over 2 years ago | |
| Shell | Shell | |
| - | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jep
-
How do you turn off all Jenkins security hardening?
What sounds like a workaround is described in the README linked from the page you linked to in your question (i.e. https://github.com/jenkinsci/jep/blob/master/jep/200/README.adoc):
governance
- Why I'll vote no on proposal 120 (and why I think every OSMO holder should do the same)
- What is the difference between voting for "Veto" and voting "No"?
-
💬🔥 AMA with Jack Zampolin, co-founder of Sommelier, on Governance Proposal #56💬🔥 - This Thursday, September 16, 9am PDT / 12pm EDT
Proposal#56: Github • Proposal • Twitter
-
💬🔥 AMA with Billy Rennekamp, the Cosmos Hub Lead 💬🔥 - September 7th, @ at 8 AM UTC / 10 AM CET
There's also a recent proposal to include an IBC packet routing feature from u/jackzampolin that should go onto the hub soon: https://github.com/cosmos/governance/pull/46. This would make it easier to use the Hub as a router, on of the strongest and earliest uses for the Cosmos Hub. As the author of the go relayer and a relayer himself, Jack knows that it's easier for relayers to operate between one network and the hub at a time, compared to running relayers between every single network. Today there are only a handful of live networks using IBC so the latter scenario is still possible. However it may be important to set the precedent that all IBC packet routing should go through the hub to ensure it continues to be the case as the number of IBC connected networks grows. This new feature allows a single IBC transaction to result in multiple hops through the Hub to a destination chain.
- Found some good talking points regarding the Ethereum bridge dilemma for anyone interested.
- Signaling Proposal - Deployment of Ethereum Gravity Bridge on the Cosmos Hub
-
⚛️🌉 Gravity Bridge is Coming to Cosmos Hub 🌉⚛️
This is an explicit point of the Gravity bridge design. Described here in the proposal.
What are some alternatives?
mkdkr - mkdkr = Makefile + Docker
gaia - Cosmos Hub
kubernetes-extension-fortosi - 'Fortosi' Kubernetes extension is meant to address a fundamental requirement of any project team running their applications on Kubernetes - which is to quickly provision CI/CD pipelines (on demand) for their various private/public GitHub projects/organisation using simple kubectl commands. Basically, implementing the concept of No Ops. It is agnostic of cloud platform, be it AWS (EKS) or Azure (AKS), and agnostic of application technology framework.
osmosis - The AMM Laboratory
Fast-Kubernetes - This repo covers Kubernetes with LABs: Kubectl, Pod, Deployment, Service, PV, PVC, Rollout, Multicontainer, Daemonset, Taint-Toleration, Job, Ingress, Kubeadm, Helm, etc.
cross-chain-validation
MonarcAppFO - MONARC - Method for an Optimised aNAlysis of Risks by @NC3-LU
governance - Resources for Cosmos governance