LumoSQL Meeting 2022/02/04 Minutes

Meeting started by danshearer at 2022-02-04 11:56:28+0000 (full logs).

These notes have been very slightly edited by hand since it was the first time we used the HCoop Meetbot.

Meeting Summary

  1. Prologue (danshearer, 11:56:28)
    1. MEETING_NAME: LumoSQL Meeting 2022/02/04 (danshearer, 11:56:50)
    2. ATTENDEE: Claudio (Labhraich, 11:57:06)
    3. ATTENDEE: Dan (danshearer, 11:57:30)
    4. ATTENDEE: Ruben (rubdos[m], 12:01:16)
    5. ATTENDEE: Björn (BKJ621, 12:01:27)
    6. ATTENDEE: Gabby (gabby_bch, 12:02:02)
  2. introduction (danshearer, 11:59:42)
    1. ACTION: Dan to locate notes from last meeting especially the actions (danshearer, 12:03:30)
    2. INFO: no notes from last meeting. That's ok, from now on we have the Bot! (danshearer, 12:04:56)
    3. INFO: I still have the IRC logs from 2022-01-21 if nobody else has collected anything 2 weeks ago (Labhraich, 12:05:24)
    4. LINK: Notes from first meeting at https://lumosql.org/src/lumosql/file?name=doc/meetings/lumo-meeting-notes-2022-01-14.md (danshearer, 12:05:25)
    5. ACTION: dan to look at irclogs from 2022-01-21 (danshearer, 12:06:02)
  3. Documentation (danshearer, 12:07:05)
    1. LINK: https://ams.uilebheist.fr/lumosql-2022-01-21.txt (Uilebheist, 12:07:11)
    2. INFO: I have been working on two aspects of documentation: RFC and citations. RFC will be very important. We already have a lot of citations. (danshearer, 12:08:05)
    3. ACTION: Ruben to do the initial BibLaTeX dump into a Lumo repository. (rubdos[m], 12:09:10)
    4. LINK: the RFC page, including current RFC and info on the RFC toolchain, is at https://lumosql.org/src/lumosql/file?name=doc/rfc/README.md (danshearer, 12:09:16)
    5. INFO: Dan has discussed with Ruben and decided how we can handle citations. We will use BibLaTeX format files and generate what we need from that. (danshearer, 12:09:58)
    6. INFO: : formality: I believe we had meetings Jan7 and Jan21. The notes say something else (BKJ621, 12:10:05)
    7. INFO: I've been editing some of the docs, want to separate it into Phase one and Phase two topics, have not updated the repository yet because my editing is still so messy (gabby_bch, 12:10:23)
    8. INFO: Discussion between Dan and Ruben was mainly to see whether we would commit RDF files (which contain a lot more data) or Bib(La)TeX. The latter was chosen because it's got plenty of information and is very compatible with tools. (rubdos[m], 12:11:08)
    9. ACCEPTED: We will use BibLaTex for citations relating to Lumoions/RFC and also LumoSQL/SQLite/general topics (danshearer, 12:12:15)
    10. INFO: pandoc has a --biblatex filter, which can produce HTML, Markdown or most other things. So that's how we add citations to the RFC markdown, and also Gabby's documentation (danshearer, 12:13:11)
    11. LINK: Everyone can turn email notifications on/off for Fossil here: https://lumosql.org/src/lumosql/subscribe (danshearer, 12:18:03)
    12. ACTION: Gabby to commit updated docs for review (gabby_bch, 12:24:10)
  4. LumoSQL Development and Testing (danshearer, 12:24:36)
    1. IDEA: modify the benchmark to be able to specify a version as "latest" so I don't need to commit changes when there's a new release of something (Labhraich, 12:29:50)
    2. INFO: SQLite 3.37.0 (the current latest) compiles on Dan's laptop using the LumoSQL build system by Claudio (danshearer, 12:32:30)
    3. INFO: 3.37.2 fails to compile with the LMDB backend (Labhraich, 12:33:06)
    4. ACCEPTED: Claudio's draft metadata document can be committed (on the topic of adding metadata to SQLite for LumoSQL to have hidden columns etc) (danshearer, 12:34:13)
  5. Lumions and Related Things (danshearer, 12:36:40)
    1. INFO: Claudio and Ruben have exchanged citations (danshearer, 12:36:59)
    2. INFO: Claudio's work with prof. Varadayan has been sent to Ruben, Ruben has compiled it into bibtex and rdf (rubdos[m], 12:37:34)
    3. INFO: Dan has figured out the toolchain and got the author of mmark (which generates an RFC from Markdown) to update the docs regarding dependencies (danshearer, 12:37:46)
    4. INFO: My schedule is now "clear"™ since the Rust meetup has finished yesterday, and since I did all the debriefing stuff. I should be able to focus 95% on literature as of this afternoon. (rubdos[m], 12:38:25)
    5. INFO: Dan *thinks* he has an example of everything we are likely to need in the RFC in the way of formatting. Including ASCII art (danshearer, 12:38:55)
  6. Brief Notes on Project Admin (danshearer, 12:43:13)
    1. ACTION: Dan to point everyone at the meetbot notes, which are both pretty HTML, and also the raw irc logs. We can decide if this is good, or needs editing. (danshearer, 12:44:21)
    2. INFO: Dan has chatted with people from LibreOffice and NextCloud and a few other well-known projects about the concept of Lumions. It seems like maybe this is an idea the world is ready for. No detail of course since we don't even have a design yet. (danshearer, 12:46:15)
    3. ACTION: Björn to remind everyone a few days before Feb 18 that there will be a meeting (danshearer, 12:47:59)
    4. INFO: I have populated a draft Leantime project management board, with URL in the wiki you all have access to. Probably not the perfect tool but I am confident extracting the data with SQL anyway. (danshearer, 12:49:01)
  7. Miscellaneous (danshearer, 12:57:08)
    1. INFO: Dan tells everyone that if they can't work with the format, I will figure something out with Björn. This can be fixed quite easily if there is any problem. (danshearer, 12:58:33)
    2. IDEA: Labhraich suggests creating a -dev channel (danshearer, 13:00:43)
    3. ACTION: Dan to send gabby_bch a database of benchmark results (danshearer, 13:01:05)
    4. ACTION: Dan to followup with Labhraich regarding benchmark amalgamation code (danshearer, 13:02:50)
    5. ACCEPTED: no -dev irc channel for at least the next two weeks (danshearer, 13:04:20)
    6. MOTION: So far, the Meetbot seems easy to use, and if the output is good we should keep it (danshearer, 13:07:27)
    7. VOTE: +1 (Labhraich, 13:07:38)
    8. VOTE: +1 (danshearer, 13:07:45)
    9. VOTE: +1 (gabby_bch, 13:07:53)
    10. VOTE: +1 (rubdos[m], 13:07:54)
    11. VOTE: +1 (BKJ621, 13:08:01)
    12. ACCEPTED: Motion accepted: 5 in favor to 0 opposed (danshearer, 13:08:04)
Meeting ended at 2022-02-04 13:08:58+0000 (full logs).

Attendees

  1. BKJ621 (aka Björn) - 20 lines
  2. Labhraich (aka Claudio) - 31 lines
  3. Uilebheist - 1 lines
  4. danshearer (aka Dan) - 104 lines
  5. gabby_bch (aka Gabby) - 10 lines
  6. lumosql-meetbot - 13 lines
  7. rubdos[m] (aka Ruben) - 27 lines

Action Items

  1. Dan to locate notes from last meeting especially the actions
  2. dan to look at irclogs from 2022-01-21
  3. Ruben to do the initial BibLaTeX dump into a Lumo repository.
  4. Gabby to commit updated docs for review
  5. Dan to point everyone at the meetbot notes, which are both pretty HTML, and also the raw irc logs. We can decide if this is good, or needs editing.
  6. Björn to remind everyone a few days before Feb 18 that there will be a meeting
  7. Dan to send gabby_bch a database of benchmark results
  8. Dan to followup with Labhraich regarding benchmark amalgamation code

Action Items by Attendee

Generated by HCoop Meetbot v0.4.1 (15 Nov 2021)