Meeting Notes - ISC Docs (2023-11-21)

Attendees

• Jeroen van den Hout
• Jorge Silva
• Kevin Mayrhofer
• Lucas Tortora

Summary

Jeroen van den Hout led the discussion on structuring documentation for Smart Contracts, emphasizing the importance of distinguishing between different technology components to prevent confusion. The meeting revolved around improving the content structure for the SDK and other tools within the wiki, taking an iterative approach to refining the documentation. There was a focus on clarifying concepts for newcomers, deciding where to place certain explanatory content, and ensuring that even those who bypass the 'Learn' section can understand what's on each page they land on.

Key points discussed include:

• It's crucial to separate the theoretical background required to build Smart Contracts from the practical documentation to aid different user journeys.
• The need to iterate documentation and accept non-linear paths users might take to find information.
• Discussing the placement of content specific to Ethereum (EVM) and WebAssembly (WASM) Virtual Machines and ensuring proper highlighting of experimental features.
• Highlighting the differences between IOTA’s approach to Smart Contracts and other networks, specifically the decimals aspect.
• Addressing the need for a clear categorization of languages and tools associated with different VMs and how best to demonstrate examples for various programming languages.
• Ensuring users understand the implications of using experimental features, specifically in the context of WASM modules that may not be production-ready.

Actionable Items

• Explain the difference between layer one accounts and Ethereum accounts more clearly.
• Add a section on how accounts and addresses map between different chains.
• Update documentation to reflect the iterative nature and provide a clearer structure for users.
• Include a warning about using experimental features, especially regarding WebAssembly.
• Highlight the compatibility of existing EVM tooling with ISC and explain the specifics, like decimals differences.
• Discuss the tools and languages supported and how to pick the right VM based on required functionality.
• Emphasize that WebAssembly is not suitable for production as it stands.
• Lucas Tortora to take notes regarding proposed changes and additional points raised.
• Redefine the scope of the 'Learn' and 'Build' sections, ensuring each one meets its intended purpose and provides clarity for developers.

Open Questions

• Will there be a focus on making WebAssembly (WASM) production-ready in the future, or will the emphasis remain on Solidity and EVM compatibility?

Notes for Review

• Clarity is needed on the current state and future of WASM within ISC documentation.
• Ensure that the experimental status of certain features is communicated effectively throughout the documentation.

(End of Meeting Notes)

It seems there was an issue with accessing the file you've provided as I did not find it in the uploaded documents. Could you please upload the document directly to this conversation so that I can proceed with creating the meeting notes for you?

Meeting Notes

Details

• Date/Time: 2023-11-20 15:13 GMT-3
• Attendee: Lucas Tortora
• Duration: 1 minute 2 seconds

Transcript Summary

Lucas Tortora talked about business operations, emphasizing on operating teams, shared sets and connections, centralized login and more specifically, he referred to a "Fire Company plan." Additionally, he mentioned the concept of a "coordinator," which involves civic sign blocks, something termed as "miles growth," and trust issues related to the confirmation of language consensus. He also referred to some aspects being indirectly referenced by a certain amount of blood and deemed automatic. The need for measures seemed conditional depending on some context related to "black current coordinator," based on the transmittent recorder BFG list, which is associated with enabling automated validators for some description-related operation.

The meeting was computer-generated and the transcript warns that it might contain errors and can be edited post-creation.

Action Items

• The transcript did not specify any tangible action items.

Note

• Given the summary, the context of the discussion appears to be technical or industry-specific, possibly involving systems, protocols, or project plans. However, the lack of detail in the transcript and the brevity of the meeting make it difficult to extract more actionable insights or concrete information. Further clarification from Lucas Tortora or additional context would be required for a more accurate understanding and any follow-up actions.