Closed epowell101 closed 1 year ago
I expect to be able to access the lego both from the website and from Github. Each lego should have a title and short description on the website. On Github, we could also include the name of the project referent and other status such as the ones you proposed.
I feel this could be a project that the community can own inside the Sandbox , the Lego project could be alive , with clear guidelines for who ever wants to build one of the ' to be build legos" just build it , submit a PR and add it to maybe " the ODC Legos Python Package" ( dreaming out loud) . Will talk about this with people on today's Sandbox meeting. @epowell101
I have made some progress here this weekend.
Went into our version of the Lego docus and updated them for accuracy and readability.
for example: https://github.com/OpenDataforWeb3/Resources/blob/main/docs/Legos.md
Started trial of MarkPrompt
If we execute on these two pieces continuously -
I think we will have addressed some of this use case. That said, we may want to have a table of Legos added to the Lego.md file.
The requirement is well stated here: "a Lego registry / Index" that lists the legos by status (hypothesis, latest experiment results, which are in ideation, etc) would help me grok it"
How can we track all of the Legos?
Should we put them into a single repository or different ones?
Would it be in the Sandbox?
Also should we fork and include the Lego Documentation?
Perhaps we could have a readme or similar that indexes all of them.
From one interested consumer of this information:
"cool.. yeah a "Lego registry / Index" that lists the legos by status (hypothesis, latest experiment results, which are in ideation, etc) would help me grok it"