-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
🌶️🏈 ↝ Beginning to add [currently] open Jira tickets
- Loading branch information
1 parent
32ccc2d
commit 495fb80
Showing
8 changed files
with
203 additions
and
13 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,62 @@ | ||
| 1. Come up with todo list & structure by the hour -> including for the hours we're having our coffee | ||
| 2. Dynamic plan for keepup, including logo | ||
| 3. Check "promised" timeline for nk12 and prepare daily milestones | ||
| 4. Contact Manu and produce a list of 10 components, provide a bit of discussion | ||
| 5. Create plan for microservices, integration into `sytizen`, workflow for Unity (including action), discuss plan for integrating new UI & actions with microservices, automated tests. | ||
| 1. d3.js v0.dev based on lightcurves? | ||
| 6. Continue with migration to Quartz | ||
|
|
||
| ### Microservices | ||
| 1. Method for generating lightcurve, integrating into d3 | ||
| 2. Method/route for populating anomaly/entity data -> sample, point to old routes in `signal-k/sytizen` repo | ||
|
|
||
| ### Nordkurve | ||
| Phase 1 -> | ||
| 1. Registration, migration and schema setup | ||
| 2. "Backend" portal (really a frontend, though, technically) for admins/board to view all data | ||
|
|
||
| ### Keepup | ||
| What we have now -> | ||
| 1. Bottom bar | ||
| 2. Main area/content grid | ||
|
|
||
| Minimum viable product -> | ||
| 1. Push notifications | ||
| 2. Method to create a feed | ||
| 3. Posts will be pushed from a local dictionary for now -> no server-side action for this component | ||
| 4. Ability to "favourite" posts/messages, these will be saved in runtime state | ||
| 5. Post category | ||
|
|
||
| Post features: | ||
| 1. Content | ||
| 2. Avatar, title/user sender metadata | ||
| 3. Favourite, user-determined metadata | ||
|
|
||
| ### Copernic | ||
| Possible components: | ||
| 1. Discussion board, based around bucket/node | ||
| 1. Discussion board would be divided into Lens & other protocols (for now, off-chain) | ||
| 2. News feed for nodes | ||
| 3. Metadata/custom tags (e.g. linking to a "proper" dsl node) | ||
| 4. Documentation area -> just do it here on quartz for now | ||
| 1. Should include videos/tutorials on how to use our platform | ||
| 5. Physical data tracker -> could be especially useful for copernic passports? | ||
| 6. Ask gpt for another 5. | ||
|
|
||
| Focus on minimal/incomplete UI, the priority is reasoning, brainstorming, documentation and minimum functionality for presentation | ||
|
|
||
| ### Travel | ||
| Key dates: | ||
| 1. May 18 -> Bayer Leverkusen vs FC Augsburg (11.30pm melbourne) | ||
| 2. May 22 -> Europa League Final (Dublin) ** | ||
| 3. May 25 -> DFB Pokal Final (Berlin) ** | ||
|
|
||
| So some options -> | ||
| * Go for the week | ||
| * Go for first two | ||
| * Go for second two | ||
|
|
||
| No other key conferences as far as I'm aware | ||
|
|
||
| Key questions -> | ||
| 1. Is it worth focusing on achieving Velocity Platinum or trying to maximise United Airlines/Star Alliance? keeping in mind I'm going to the US at least one more time this year |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,20 @@ | ||
| --- | ||
| title: GP-10 | ||
| tags: | ||
| - Star-Sailors | ||
| - Content | ||
| - Sector | ||
| - Structure | ||
| - Building | ||
| - Anomaly | ||
| --- | ||
| https://signalk.atlassian.net/browse/GP-10?focusedCommentId=10122 | ||
|
|
||
| Minimum requirement -> | ||
| 1. Allow users to build structures on a planet's sector | ||
| 2. Require classification to do so (this will, for now, be contingent on the user having set a `basePlanet` as their `profiles.location` field, which right now is done via fiddling with the backend -> but it could be considered to be an equivalent barrier) | ||
| 3. Link the structure that has just been placed to the next step of classification. Provide a pathway to generate additional context/information once the user has placed that structure. | ||
|
|
||
| A child issue, GP-11, has been created and will be targeted towards the microservice for validating correct items & crafting recipes. | ||
|
|
||
| Some additional context has been added to the Jira issue, which has been handballed to Rhys for completion/filing |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
50 changes: 50 additions & 0 deletions
50
content/Star Sailors/Components/Content/Create Planet Sector.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,50 @@ | ||
| --- | ||
| title: CreatePlanetSector.tsx | ||
| tags: | ||
| - Star-Sailors | ||
| - Sector | ||
| - Empty | ||
| --- | ||
|
|
||
| Path: `components/Content/Planets/CreatePlanetSector.tsx` | ||
|
|
||
| ```tsx | ||
| import React, { useEffect, useState } from "react"; | ||
|
|
||
| import { useSupabaseClient, useSession } from "@supabase/auth-helpers-react"; | ||
|
|
||
|
|
||
|
|
||
| function CreatePlanetSectorComponent ({ planetId }) { | ||
|
|
||
| const supabase = useSupabaseClient(); | ||
|
|
||
| const session = useSession(); | ||
|
|
||
| const [isLoading, setIsLoading] = useState(false); | ||
|
|
||
|
|
||
|
|
||
| const createSector = () => { | ||
|
|
||
| if (!session) { return; }; | ||
|
|
||
|
|
||
|
|
||
| if (!planetId) { return; }; | ||
|
|
||
|
|
||
|
|
||
| // Generate random mineral deposits - will later be set in db | ||
|
|
||
| const depsitCount = Math.floor(Math.random() * 5); | ||
|
|
||
| }; | ||
|
|
||
| }; | ||
| ``` | ||
|
|
||
| I think this might be a component/script that was unfinished? Must look into this | ||
|
|
||
| Update -> appears `components/Content/Planets/IndividualPlanet.tsx` is also another component. Might be from the v1 (`CPW-8` branch) template | ||
| Update 2 -> actually another way of showing the planet content in dynamic routing/pages. So should keep that here for now |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| --- | ||
| title: Star Sailors - Crafting & Inventory Operations | ||
| tags: | ||
| - Star-Sailors | ||
| - Content | ||
| - Narrative | ||
| - Planning | ||
| - Sector | ||
| --- | ||
| > Raw material [combination] → base building block → tool/structure/vehicle or other entity | ||
| Current setup: | ||
| 1. /Gather page -> list of all sectors, ability to create new sectors | ||
| 2. Create sector -> Take a random raw material, add that as the mineral deposit for the sector | ||
|
|
||
| It would probably be a good idea to get a list of all the files relevant to the gather and sector components to begin identifying possible duplication/code redundancy. | ||
|
|
||
| `<ImagesGrid` component needs to be removed, and replaced with a function that takes all the [public] sectors and displays them. Currently it just shows a random set of images as a demo. | ||
|
|
||
| ## Creating a sector | ||
| 1. Check to see what planet a user currently "owns" (aka has set as their home planet. This is currently a manual process, in `profiles.location`, this is a part of our workflow we have to setup soon as well) | ||
| 2. Currently the client chooses between silicates & coal when choosing the resource to be a part of the sector | ||
| 3. A new rover image/cover image (so not required to be from a rover) SHOULD be generated, however we have it set to select the same one each time (for now): `coverUrl: "https://mars.nasa.gov/mars2020-raw-images/pub/ods/surface/sol/00090/ids/edr/browse/edl/EBE_0090_0674952393_193ECM_N0040048EDLC00090_0030LUJ01_1200.jpg",`. This should be fixed as well |