tracker.org

notes/factorio_maps.org

@@ -0,0 +1,27 @@
+:PROPERTIES:
+:ID:       e5c17702-09d5-4d7d-97ff-95a8de353ea0
+:END:
+#+TITLE: Factorio Maps
+#+Author: Yann Esposito
+#+Date: [2022-01-10]
+- tags :: 
+- source ::
+
+
+.
+* Easy 200% + no cliff + low enemies
+
+#+begin_src
+>>>eNpjZGBkMAJiIGiwB2EOluT8xBwg1wGCDzhwJecXFKQW6eYXp
+SILcyYXlaak6uZnoipOzUvNrdRNSixOhZkINjWzKD8P3QTW4pL8P
+FSRkqLU1GJkjdylRYl5maW56HoZGG+W/HRvaJFjAOH/9QwK//+DM
+JD1AKgGhBkYGyAqgWIwwJqck5mWxsCg4AjETmBFjIzVIuvcH1ZNs
+WeEqNFzgDI+QEUOJMFEPGEMPwecUiowhgmSOcZg8BmJAbG0BGgFV
+BWHA4IBkWwBSzL2vt264PuxC3aMf1Z+vOSblGDPaOgq8u6D0To7o
+CQ7yAtMcGLWTBDYCfMKA8zMB/ZQqZv2jGfPgMAbe0ZWkA4REOFgA
+SQOeDMzMArwAVkLeoCEggwDzGl2MGNEHBjTwOAbzCePYYzL9uj+A
+AaEDchwORBxAkSALYS7jBHCdOh3YHSQh8lKIpQA9RsxILshBeHDk
+zBrDyPZj+YQzIhA9geaiIoDlmjgAlmYAideMMNdAwzPC+wwnsN8B
+0ZmEAOk6gtQDMKDJlewURBawAEc3MwMCABMG7wPMkwBU92clw==<
+<<
+#+end_src

tracker.org

@@ -1986,7 +1986,7 @@ To me this totally doable, and I think should be the preferred route.
 *** 2022-01-06 Thursday
 **** MEETING Weekly                                               :work:meeting:
 :LOGBOOK:
-CLOCK: [2022-01-06 Thu 16:59]
+CLOCK: [2022-01-06 Thu 16:59]--[2022-01-06 Thu 18:42] =>  1:43
 :END:
 [2022-01-06 Thu 16:59]
 
@@ -2054,3 +2054,59 @@ client-id: "client-67436e65-d6a8-4f8c-9bea-3de6feed3b44"
   "created-at": "2021-09-28T09:50:35.814Z"
 }
 #+end_src
+
+** 2022-W02
+
+*** 2022-01-10 Monday
+**** CHAT Deploy UI for IROH-Auth                                 :work:chat:
+:LOGBOOK:
+CLOCK: [2022-01-10 Mon 17:59]--[2022-01-10 Mon 18:34] =>  0:35
+:END:
+[2022-01-10 Mon 17:59]
+- ref :: [[file:~/Library/Mobile Documents/iCloud~com~appsonthemove~beorg/Documents/org/tracker.org::*Notes][Notes]]
+
+We have a change that will imply a change in how we deploy our app.
+We would like to use the code from Dar's team.
+So mainly they just need to provide assets (js, html, css, imgs, etc…)
+
+We would like to use:
+
+- On INT, use the `master` branch of their repo,
+- On TEST/PROD, use the matching release branch of their repo.
+
+One option is to ask them to deploy a new `SNAPSHOT` versionned jar for
+every commit in master and depend on it, and ask them to deploy a release
+version of the jar for the release branch.
+
+I think it would be a lot easier if could depend directly on a git
+specific commit in the declaration of the dependences in our `project.clj`.
+Ambrose I think you did touch something like that.
+Do you have any opinion about how to do this?
+
+
+**** MEETING Registration Simplification Weekly                  :work:meeting:
+:LOGBOOK:
+CLOCK: [2022-01-10 Mon 16:28]--[2022-01-10 Mon 17:59] =>  1:31
+:END:
+[2022-01-10 Mon 16:28]
+- ref ::
+
+Date for Q3: 6 releases  in next April 27th
+
+***** Agenda (to discuss about)
+***** Notes
+
+- Region cannot be seen.
+
+***** Actions
+
+*** 2022-01-11 Tuesday
+**** MEETING Secure Endpoint                                      :work:meeting:
+:LOGBOOK:
+CLOCK: [2022-01-11 Tue 15:31]
+:END:
+[2022-01-11 Tue 15:31]
+- ref ::
+***** Agenda (to discuss about)
+***** Notes
+***** Actions