Global Developer Network
We are re-inventing the workflow for how developers test, implement, and describe their stacks. We are providing a new industry standard for validating the security and behavior of your app!
Become a financial contributor.
Global Developer Network is hosting the following events.
Global Developer Network is all of us
Our contributors 1
Thank you for supporting Global Developer Network.
Let’s get the ball rolling!
News from Global Developer Network
Updates on our activities and progress.
Join us for programming language engineering discussions!
Town Hall Jan 15th 2pm EST
Let’s get the discussion going! This is a space for the community to converse, ask questions, say thank you, and get things done together.
We are beginning to formulate the Federated aspects of GDN.
Published on February 10, 2021 by Christopher Hogan
This includes the member-level agreement, structure, and council reporting that will be tracked through a system such as ClickUp. More details soon to follow!
Published on January 26, 2021 by Christopher Hogan
We are officially recognized by Open Collective as of today. More details here: https://lmg.systems/gdn-notion (...
Welcome to Global Developer Network
Published on January 3, 2021 by Christopher Hogan
We're just starting out for 2021! But expect to see lots of exciting news here real soon!
Backed by: Full Stack Engine
Pushed forward by: Christopher Hogan and a federated council of advisors.
"We are re-inventing the development process for Full Stack applications with an emphasis on business requirements, domain driven operations, security-first specifications with conformance to industry-standard best practices, and test coverage. "
Global Developer Network (GDN)
Will launch on OpenSourceStacks.com
Open source provider of Full Stack Engine specifications utilizing the open Stack Standard API. (stackStandard.com to launch Feb 1st).
Our mandate is to make things simple for developers when it comes to security, accessibility, and expected behaviors based on business requirements.
So in essence, to solve these problems we have to write our own language. The requirements for the language are:
- Must be architected default secure, end-to-end encryption for LSP, and have solid IDE support for auto-completion, peeking, following classes and interfaces, etc.
- All artifacts must be stored on encrypted disks, with encryption at rest and encryption on actions for data stores, and for data transport to archival storage. For certain regulations we must comply with Gov Cloud, CloudHSM, and their equivalents on various clouds.
- All code that transforms or replaces other code with RAC (Result As Code) functionality must be signed and encrypted with GPG or with DCT (Docker Content Trust) for Docker artifacts.
- The language must work with LSP (Language Server Protocol) and be pluggable to support future languages through "thin" layer modules in various package managers that are open source. The thin loaders will spawn docker containers to bootstrap the CLI itself.
- All core binaries must be released with CICD, pass commit checks, and be reviewed by the community as well as expert peers. All CICD systems must use existing Peach technology (or equivalent) that Gitlab has been working on and musts support their DAST & Fuzzing systems for collaborative purposes to avoid overlap.
- The system itself must describe queries, because the instructions will constantly change.
- A decentralized, multi-az, multi-region, global deployment of the API specification must be made available.
- A CLI musts be available which generates code stubs and scaffolds large stack descriptions into helm charts, and with each stack represented with a `.stack` file written in FDSL, and a `.stack.gpg.pub` file providing a public key signature for verification by our CLI.
- The initial stack backends must conform to Helm3 standards
- The repository must provide an Open API 3 specification.
- The repository must provide a Kubernetes CRD for enterprise deploys and on-premise.
- The advisory council must provide expert security oversight for the project.
- Telemetry data must not be collected on any of our products, ever.
It is a project priority to establish an open source job website for freelance and other types of gigs. We will be providing marketing and project management using Agile methodology and real-world best practices. The website will be provided as part of the StackOps, which is launching in early FY21Q3 ~ basically Jan-Mar.
We have many tools and services that will be provided to the open source community at large. Most importantly, we intend to facilitate compliance with prominent security standards. i.e.- NIST, PCI-DSS, HITECH, HIPAA. How we intend to do this is using a developer-first strategy. The details will be open sourced in stages as the concept launches.
For more information follow @hoganrtp or join our group on LinkedIn, @GloblDevNetwork on Twitter (for announcements only), or Join us on Discord.