dash VS foundation

In case you are facing issues with nodes you forgot to update, please update now https://github.com/dashpay/dash/releases/tag/v19.2.0 and if your node is stuck on a prior block, please be sure to reindex that node.

I want to create a bot that sends messages once new releases of certain GitHub/Gitlab repo’s ( -https://github.com/bitcoin/bitcoin/releases -https://github.com/ethereum/go-ethereum/releases -https://github.com/prysmaticlabs/prysm/releases -https://github.com/dashpay/dash/releases -https://github.com/Team-Kujira/core/tags -https://gitlab.com/thorchain/thornode/-/releases ) have been released.

Visit the official Dash GitHub repository at https://github.com/dashpay/dash/releases/tag/v19.1.0 to access the latest version, v19.1.0.

"Dash mainnet blockchain has frozen currently. Dash payouts will be resumed when the issue is fixed Github Issue"

Please upgrade to https://github.com/dashpay/dash/releases/tag/v19.1.0 This release should resolve the chain stall once a sufficient number of masternodes and miners have upgraded. Please be aware of the known issues listed in the release announcement. A reindex may be needed.

Talking about spitting code out faster and better, do you know whats going on with the v19 release to Mainnet ? Product brief was from 3 days ago and their v19 release process (https://github.com/dashpay/dash/issues/5294) has not been progressing lately (stuck at 10 of 48 tasks).

A mature open source project may be governed under an open source foundation which usually gives it a charter https://github.com/cncf/foundation/blob/main/charter.md#3-va...

... and/or set of values: https://kubernetes.io/community/values/

There's also a lot of open source guides here https://todogroup.org/resources/guides/ that may help you if you're looking at building mature open source projects.

The CNCF has made exceptions on their license policy before, specifically for MPL based software. It'll probably be easier for OpenTF to go through that process than to relicense (which is likely not even possible for anyone other than Hashicorp).

- https://github.com/cncf/foundation/tree/main/license-excepti...

- https://github.com/cncf/foundation/blob/main/license-excepti...

Your comment or post were removed for violating the CNCF Code of Conduct. Please take a moment to review that here: https://github.com/cncf/foundation/blob/master/code-of-conduct.md

His behavior offends me as a professional software engineer and/ in my opinion, violates CNCF Code of Conduct https://github.com/cncf/foundation/blob/master/code-of-conduct.md.

Anyone can become a member. Non-profit as in https://github.com/cncf/foundation/blob/master/charter.md

Read more about role of the CNCF, their projects and Values here.

https://github.com/cncf/foundation/blob/master/allowed-third...

I haven't read the details, or ever seen this policy before (I'm new to both projects) but it was summarized by one of our counterparts at the Linux Foundation here:

https://twitter.com/cra/status/1384859663615864833

Tl;dr: licenses must be approved for use, and the CNCF has this list of allowed licenses, AGPL is not on it. The CNCF is in the business of distributing permissively-licensed software is the short version I guess. I don't understand, I don't work on the legal side, I am a dev and I support end users.

It seems if your Apache 2.0 licensed project needs to modify and distribute as modified Grafana, which it seems likely we will need to do at some point, then you cannot distribute them together. Chris says they are going to work something out, but when a component has made a decision to re-license with a restrictive-copyleft license such as AGPL, I don't know what there is that can be done.

Maybe the CNCF adopts AGPL too, (which would mean that then all those "viral-GPL" FUD-spreaders will have been right...) that seems counter-productive if that is the outcome.