|
1 | 1 | # TODO |
2 | 2 |
|
3 | | -- [x] Add KNEEAD to navigation bar (external link needs redirect setup) |
4 | | - |
5 | | -- [x] proto.pretty move the lib out of Protokit and into KiCad-Master-Lib? Then use in Protokit and in the Slice_PRTO_XYZ projects? |
6 | | - |
7 | | -- [x] KiCad-Hierarchical-Designs change to KiCad-Design-Blocks ? Using KiCad's [Schematic Design Blocks](https://docs.kicad.org/9.0/ca/eeschema/eeschema.html#schematic-design-blocks) or would it be better as a separate project? Need to investigate further. |
8 | | - |
9 | | -- [x] Update all Slice_PRTO_XYZ projects to use proto.pretty from KiCad-Master-Lib |
10 | | - |
11 | | -- [x] Update all templates to use revised KMLib |
12 | | - |
13 | | -- [x] Clean up concepts: |
14 | | - - VEGIS and CRUST |
15 | | - - The 2 stacks |
16 | | - - SLICE, LOAF, BATCH, OVEN |
17 | | - - SLICE, FROOTS, PROTINS, SIGARS |
18 | | - - Retain as a future vision / prior ideas / brainstorming section in the documentation? |
19 | | - |
20 | 3 | - [ ] Update all protokit to use proto.pretty from KiCad-Master-Lib and build schematics for those that don't have them yet where it makes sense (i.e. project boards) |
21 | 4 |
|
22 | | -- Add the MVP documentation for the following projects and how they fit into the FEAST ecosystem and relate to each other: |
23 | | - - [ ] BreakoutPack |
24 | | - - [ ] protokit |
25 | | - - [ ] DevBoardDepot |
26 | | - - [ ] Maybe merge all these for now under a mono-repo? |
27 | | - - [ ] Now does it related to nanos-kicad and can-nano-shield? |
28 | | - - Maybe |
29 | | - - Devboarddepot and nanos kicad could be merged? |
30 | | - - Breakoutpack and protokit could be merged? |
31 | | - - Then for hardware we have proto?, nanos?, breads (slice+loaf) |
32 | | - |
33 | 5 | - [ ] Freeboard transfer from personal |
34 | 6 |
|
35 | 7 | - [ ] Update all protokit examples to use proto.pretty from KiCad-Master-Lib |
|
46 | 18 |
|
47 | 19 | - [ ] [KiCad-Databases](https://github.com/FEASTorg/KiCad-Databases) |
48 | 20 |
|
49 | | -- [ ] rename from FEASTorg to feast-labs? Note that [github.com/feast-dev](https://github.com/feast-dev) is a taken and well established name for the feast-dev ML feature store project. |
| 21 | +- [ ] rename from FEASTorg to feast-labs? Note that [github.com/feast-dev](https://github.com/feast-dev) is a taken and well established name for the feast-dev ML feature store project. Maybe feast-group? Or another idea would be to rename to feast-org or feast-hq? |
0 commit comments