...
Guest Speaker:
Chris Gabriel from Hyperchain Labs will be demoing some of his work with using the Fabric Certificate Authority, with which he has built a carbon network for different organizations (carbon emitter, regulator, renewable energy project manager, verifier, etc.)
...
- Utility bills
- Shipping data
- Travel data
- Vehicle trip data
- Renewable Energy Certificates
- Carbon offsets
By combining these data sources Think of each of these data source as a "programming primitive." On their own, they're just data. But combined together, we could build many different types of carbon emissions calculators fairly easily, includinga variety of interesting applications, such as:
- Virtual Community Renewable Energy Network
- Vehicle Travel OffsetsVirtual Zero Emission Vehicles
- Personal Carbon Offsets
- Data Center Carbon Calculator
Each of these applications could empower a group of people to work together and take positive climate action, without waiting for a central authority to step up and regulate things.
What we need is more ideas, both of where to obtain emissions data and what kind of applications could be built with them, so please write if you have any suggestions.
...
Coding Standards
Even though, or perhaps because we're building open source software, code quality is very important. We're writing code that others would see long after we're finished, so we'd better leave them something they could actually understand and work with. We'd also like to avoid being featured in an "Anti Pattern" book or blog post.
The most important coding standard is to keep things very modular, so separate each function as much as possible. The UI and application logic must be completely separated, to the point of being separate projects, and talk to each other only through clearly defined (REST) API's. This means that we could have several different UI's, like Linux. It also means we don't start putting our business logic in the UI, like some PHP or JSP code did. Similarly, different application domains such as user management, application logic, and standards data management must be kept apart as well. There are probably a lot of other examples, so feel free to add more ideas here!