Skip to content

Minutes

Jump to bottom
Oliver Kopp edited this page Aug 1, 2022 · 478 revisions

Topics discussed in each dev call

Preparation of the call

  • git checkout main && git pull
  • gradlew run
  • Start IntelliJ
  • Change screen resolution to 1920x1200 (because this is the maximum resoultion all participants have)

Agenda

JabCon

  • JabRef will be 20 years old on November, 29 2023 - any thoughts for a three-year celebration phase?

2022-08-15

  • Check CiteSeer fetcher
  • Release before JabCon

2022-08-01

  • Worked on DevCall issues

2022-07-18

  • Worked on DevCall issues
  • CiteSeer is down

2022-06-06

  • Worked on DevCall issues

2022-05-23

  • GSoC: We got one mentee - welcome Houssem!
  • Discussions as usual

2022-05-09

  • Reviewed PRs, finalized on PR

2022-04-25

  • We merged some pull requests
  • We headed to a release

2022-04-11

2022-03-28

2022-02-18

2022-01-31

2022-01-17

  • Exchange

2022-01-03

  • Working on PRs

2021-12-20

2021-12-06

2021-11-22

  • Christoph: Feedback on https://github.com/JabRef/jabref/pull/7825 --> general color design. --> we are looking forward to input
  • Linus: Privacy Policy of JabRef? (So people can use JabRef on company computers) --> List of services, why we are using it, link to their privacy policy
  • GSOC 2022: Now open to non students as well

2021-11-08

2021-10-25

2021-10-18

  • Uni Basel course
  • Dev call issues

2021-09-27

Preparation of Uni Basel SE Course

What did we achieve since the last call?

What are important things to do?

2021-09-13

What did we achieve since the last call?

What are important things to do?

2021-08-16

What did we achieve since the last call?

What are important things to do?

Maintenance tasks

Other Discussions

  • JabCon

2021-08-02

What did we achieve since the last call?

What are important things to do?

Other Discussions

2021-07-19

2021-07-05

2021-06-21, 20oo

2021-06-07, 20oo

2021-05-24, 20oo

2021-05-10, 20oo

Thinking of Alternatives to File Writing

Decision drivers

  • check whether file is written correctly
  • after power outage: recognize that something was wrong during writing

Alternative 1:

ren a.bib a.tmp # renaming keeps the hard links copy a.tmp a.bib # placeholder if something goes wrong --> a.bib is always there write to a.tmp # ren a.tmp a.bib # renaming keeps the hard links

  • Good, because hard links are kept
  • Bad, because issues with dropbox could arise
  • Bad, because issues with OneDrive surely arise

Alternative 2:

copy a.bib to a.bak write to a.bib # assumption: throws error if something goes wrong del a.bak (after successful write)

if something goes wrong at writing: copy a.bak to a.bib

  • Good, because easy to implement
  • Good, because in the case of writing errors, users can restore the bib from a.bak (JabRef warns at startup)
  • Bad, because data will be lost in case of power outages

Alternative 3:

(Current solution)

write to a.tmp copy a.bib to a.bak move a.tmp to a.bib del a.bak

2021-05-10, 20oo

2021-04-26, 20oo

2021-04-12, 20oo

2021-03-29, 20oo

2021-03-15, 20oo

2021-03-01, 20oo

2021-02-15, 20oo

2021-02-01, 20oo

2021-02-08, 20oo

2021-01-18, 20oo

2021-01-04, 20oo

Discussions for Leisure Time

  • Use nullity annotations from IntelliJ IDEA to have less annoying NPE bug reports. IDEA can automatically set @NotNull and @Nullable annotations throughout the code and then analyse the code to see any violations of the contracts. Downside: adding dependency to IntelliJ annotations... --> https://github.com/soc/annotation and https://github.com/google/guava/issues/2960
  • XMPUtil.main -> CLI strategy (see #266). Currently, we JabRefMain exposes a CLI interface and also is able to start the GUI. Options: 1) ignore XMPUtil, 2) add XMPUtil as a jabref xmputil PARAMS cli option as part of existing cli interface, 3) create a separate jabref-xmputil.jar which is also shipped that has this class as a main class.
Clone this wiki locally