cryptonite
foundation
cryptonite | foundation | |
---|---|---|
6 | 11 | |
224 | 526 | |
- | 1.7% | |
0.0 | 9.4 | |
over 1 year ago | 2 days ago | |
C | Rich Text Format | |
BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
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.
cryptonite
-
Crypton is forked from cryptonite with the original authors permission
There was also the Haskell-crypto fork (https://github.com/haskell-crypto/cryptonite) which was done for similar reasons - will this fork include any of its changes? I can’t remember if much was actually done in that project, most of the work has been on the libsodium library. It would be good to have just one place for all of this, perhaps Kazu could consider moving crypton into that organisation and helping contribute.
-
[ANNOUNCE] GHC 9.2.2 is now available!
GHC 9.2 support for cryptonite is added in this PR: https://github.com/haskell-crypto/cryptonite/pull/354 So that should be fixed soon i guess..
- A new future for cryptography in Haskell
- List of upcoming breaking changes
-
NorfairKing/haskell-dangerous-functions ; Call for contributions
fromIntegral is no joke, for example https://github.com/haskell-crypto/cryptonite/issues/330
-
[Haskell-cafe] Future of package cryptonite
The main issue is actually inability to switch to newer GHC 9.0, which seems blocked by other packages
foundation
-
Ask HN: Canonical Dicussions for OSS Projects?
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.
-
OpenTF Announces Fork of Terraform
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...
- ebpf 月报 - 2023 年 1 月
-
Cubernetes
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
-
A call to the open source community for help!
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.
-
Is Cloud Native meaningless jargon?
Anyone can become a member. Non-profit as in https://github.com/cncf/foundation/blob/master/charter.md
-
Cloud Native design
Read more about role of the CNCF, their projects and Values here.
- CNCF: Third Party Dependencies that have been Relicensed to AGPL
-
Minio Changes License to AGPL
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.
-
Can you recommend some resources for learning about security practices I should know about when approaching an app conversion to kubes from VM based deploys please?
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
What are some alternatives?
cprng-aes - Crypto Pseudo Random Number Generator using AES in counter mode
netboot.xyz - Your favorite operating systems in one place. A network-based bootable operating system installer based on iPXE.
elocrypt - Generate easy-to-remember, hard-to-guess passwords
PIVX - Protected Instant Verified Transactions - Core wallet.
merkle-tree
minio - The Object Store for AI Data Infrastructure
HsOpenSSL - OpenSSL binding for Haskell
autocert - [mirror] Go supplementary cryptography libraries
xxhash - Haskell implementation of the XXHash algorithm
dash - Dash - Reinventing Cryptocurrency
ed25519 - Minimal ed25519 Haskell package, binding to the ref10 SUPERCOP implementation.
toc - ⚖️ The CNCF Technical Oversight Committee (TOC) is the technical governing body of the CNCF Foundation.