Minutes

Topics discussed in each dev call

Preparation of the call

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

Agenda

• What did we achieve since the last call?
  • "done" cards of Kanban-Board "Bugs": https://github.com/orgs/JabRef/projects/7 --> will be archived
  • "done" cards of Kanban-Board "Features & Enhancements" https://github.com/orgs/JabRef/projects/6 --> will be archived
  • "done" cards of Kanban-Board "JabRef Maintainers' Focus": https://github.com/orgs/JabRef/projects/10 --> will be archived
  • "done" cards of candidates of university projects - https://github.com/orgs/JabRef/projects/3/views/1
  • "done" cards of good first issues - https://github.com/orgs/JabRef/projects/5/views/1
• What are important things to do?
  • Devcall issues at user documentation: https://github.com/JabRef/user-documentation/labels/devcall
  • Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
  • Are there failing tests?
  • Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status of PRs:
  • Code: https://github.com/JabRef/jabref/pulls
  • Documentation: https://github.com/JabRef/user-documentation/pulls
  • JabRef Browser extension: https://github.com/JabRef/JabRef-Browser-Extension/pulls
  • From time to time: Check other repositories at https://github.com/JabRef
• Status and main topic for next release. This time v6.0: https://github.com/JabRef/jabref/milestone/24
• Maintenance tasks
  • Status of old "Waiting for feedback" issues: https://github.com/JabRef/jabref/issues?q=is%3Aissue+is%3Aopen++label%3A%22status%3A+waiting-for-customer-feedback%22+
  • Review and tag new issues at https://github.com/JabRef/jabref/issues
  • Review of Kanban-Board "Bugs": https://github.com/JabRef/jabref/projects/5
  • Review of Kanban-Board "Features & Enhancements" https://github.com/JabRef/jabref/projects/7
  • Review "Candidates for university projects": https://github.com/orgs/JabRef/projects/3
    • Think of putting something of "Features & Enhancements", "JabRef UI Improvements", or "For Future" here
  • Discuss "Discussion" column of "For Future" https://github.com/orgs/JabRef/projects/9

JabCon

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

2022-12

• JabRef got 19 years old on Tuesday, November, 29 2022

2022-10-24

• Influx of students trying to work on issues
• The OSS mentorship is doing "OK". One documentation PR merged: https://github.com/JabRef/user-documentation/pull/406
• What are important things to do?
  • Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
    • Discussed https://github.com/JabRef/jabref/issues/8701, especially the workspace concept
  • Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+ - Discussion on https://github.com/JabRef/jabref/pull/9275 - Discussion on behavior of pressing ESC when in an input field; our expectation: field is left, but dialog is kept opened.

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

• GSoC: Feedback on new proposal. No proposal for Apache Thymeleaf existing yet.
• Status and main topic for next release. This time v5.6: https://github.com/JabRef/jabref/milestone/25

2022-03-28

• GSoC: Discussions of current candidates
• Are there failing tests?
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status and main topic for next release. This time v5.6: https://github.com/JabRef/jabref/milestone/25

2022-02-18

• Christoph: Feedback on https://github.com/JabRef/jabref/pull/7825 --> general color design. Should we hire someone? --> Postponed to JabCon
• Checkup GSoC --> application filed; descriptions can still be updated

2022-01-31

• GSoC ideas (also for non-students)
• Discussion of BlueHat next steps - context https://github.com/blue-hats/bluehats-soc/blob/main/propositions.md#jabref--contribuer-%C3%A0-un-logiciel-de-gestion-bibliographique-de-premier-plan
• Google Season of Docs application

2022-01-17

• Exchange

2022-01-03

• Working on PRs

2021-12-20

• Good feedback by University of Basel
• Make a release today --> https://github.com/JabRef/jabref/releases/tag/v5.4

2021-12-06

• Update from University of Basel appreciated
• Status and main topic for next release. This time v5.4: https://github.com/JabRef/jabref/milestone/23 --> we shrunk down the list of important issues for v5.4 - and created v6.0 (with Lucene and advanced LO support)
• hit the 64k Java limit again: https://bugs.openjdk.java.net/browse/JDK-8240567

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

• Uni Basel Software Engineering course is running fine
• Typical dicussions

2021-10-25

• Uni Basel: Good progress
• Multilanguage support for docs? https://github.com/JabRef/user-documentation/issues/363 --> There are no volunteers for maintaining translations

2021-10-18

• Uni Basel course
• Dev call issues

2021-09-27

Preparation of Uni Basel SE Course

• Background: Repository: https://github.com/unibas-marcelluethi/software-engineering
• Organization throughout the course
  • Aim: Review requirements specification as soon as possible
• Check: https://github.com/JabRef/jabref/projects/9

What did we achieve since the last call?

• "done" cards of Kanban-Board "Bugs": https://github.com/JabRef/jabref/projects/5 --> will be archived (1)
• "done" cards of Kanban-Board "Features & Enhancements" https://github.com/JabRef/jabref/projects/7 --> will be archived (0)
• "done" cards of Kanban-Board "JabRef Maintainers' Focus": https://github.com/JabRef/jabref/projects/11 --> will be archived

What are important things to do?

• Are there failing tests? Yes. Fetchers. We will work on it.
• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue (none)
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+ (none)
• Status and main topic for next release. This time v5.4: https://github.com/JabRef/jabref/milestone/23

2021-09-13

What did we achieve since the last call?

• "done" cards of Kanban-Board "Bugs": https://github.com/JabRef/jabref/projects/5 --> will be archived (4)
• "done" cards of Kanban-Board "Features & Enhancements" https://github.com/JabRef/jabref/projects/7 --> will be archived (6)
• "done" cards of Kanban-Board "JabRef Maintainers' Focus": https://github.com/JabRef/jabref/projects/11 --> will be archived (1)

What are important things to do?

• Are there failing tests?
  • IEEE: Network error. Key problem?
  • SpringerFetcher: Provides two results instead of one expected
• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+

2021-08-16

What did we achieve since the last call?

• "done" cards of Kanban-Board "Bugs": https://github.com/JabRef/jabref/projects/5 --> will be archived
• "done" cards of Kanban-Board "Features & Enhancements" https://github.com/JabRef/jabref/projects/7 --> will be archived
• "done" cards of Kanban-Board "JabRef Maintainers' Focus": https://github.com/JabRef/jabref/projects/11 --> will be archived

What are important things to do?

• Are there failing tests? Yes
  • IEEE API because of key limit --> @koppor checks
  • Mr. DLib --> Jöran wrote that chances are low to get it fixed the next weeks. We keep waiting until a new JabRef release whether to disable it. We created https://github.com/JabRef/jabref/issues/7995
• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
  • https://github.com/JabRef/jabref/issues/7942 -- developers follow up later
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status and main topic for next release. This time v5.4: https://github.com/JabRef/jabref/milestone/23
  • Reassigned developers, working on it

Maintenance tasks

• Status of PRs: https://github.com/JabRef/jabref/pulls

Other Discussions

• JabCon

2021-08-02

What did we achieve since the last call?

• "done" cards of Kanban-Board "Bugs": https://github.com/JabRef/jabref/projects/5 --> will be archived
• "done" cards of Kanban-Board "Features & Enhancements" https://github.com/JabRef/jabref/projects/7 --> will be archived
• "done" cards of Kanban-Board "JabRef Maintainers' Focus": https://github.com/JabRef/jabref/projects/11 --> will be archived
• "done" cards of Kanban board "JabRef UI Improvements": https://github.com/JabRef/jabref/projects/6

What are important things to do?

• Are there failing tests? IEEE because of rate limit; Mr DLib will be back online soon.
• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue --> none present
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+ --> none present
• Status and main topic for next release. This time v5.4: https://github.com/JabRef/jabref/milestone/23 --> two main things left to do.

Other Discussions

• Christoph: Feedback on https://github.com/JabRef/jabref/pull/7825 --> general color desgin. Should we hire someone? --> Chris will ask him in the next two weeks, since he was too busy yet.

2021-07-19

• Are there failing tests? -> Carl and Christoph will check them
• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status and main topic for next release. This time v5.4: https://github.com/JabRef/jabref/milestone/23
• Review Kanban-Board for our tasks: https://github.com/JabRef/jabref/projects/11
  • Archive all done cards
  • Overall status
  • Status of bugs: https://github.com/JabRef/jabref/projects/5
    • Archive all done cards
  • Status of features: https://github.com/JabRef/jabref/projects/7
    • Archive all done cards
• Status of PRs: https://github.com/JabRef/jabref/pulls
• Status of old "Waiting for feedback" issues: https://github.com/JabRef/jabref/issues?q=is%3Aissue+is%3Aopen++label%3A%22status%3A+waiting-for-customer-feedback%22+
• Review and tag new issues at https://github.com/JabRef/jabref/issues

2021-07-05

• JabRef Release v5.3 is out (soon)
  • Aim: Work on opened pull requests (until JabCon)
• Christoph: Feedback on https://github.com/JabRef/jabref/pull/7825 --> general color desgin. Should we hire someone? --> Postponed to next week
• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Discussion on org.jabref.preferences.PreferencesService
  • https://devdocs.jabref.org/getting-into-the-code/high-level-documentation
  • Discussion on granularity. Shuld the PreferenceService the "huge" DTO or should we use the stripped down "small" preference things (such as org.jabref.logic.importer.ImportFormatPreferences)
  • Long run: integrate org.jabref.preferences into org.jabref.logic
  • Discussion on keyword seperator --> maybe introcude FetcherPreferences object -- same setting; stored once, but preference service puts it into FetcherPreferences, ImportFormatPreferences, CLS...Preferences. We accept that alias issues could occur.
  • Preference classes should follow the use case
  • For each logic package: one preference class (collecting the features of the package) - even if not all citizens of the package use all preference, but that helps to reduce the number of preference objects passed --> this avoids the "pseudo-global" "variable"
  • Discussion on using JavaFX observables at the preferences (to avoid JabRef restart on preferences changes)
• Status of PRs: https://github.com/JabRef/jabref/pulls

2021-06-21, 20oo

• JabRef participates in OpenJDK Quality Outreach program
  • We don't run on JDK17 EA yet (https://github.com/JabRef/jabref/pull/7834) because of https://github.com/gradle/gradle/issues/16857
• Are there failing tests?
  • Grobid is down: Host Grobid on Azure --> Christoph + Olly + Benedikt
  • Fetcher tests failing
    • TitleFetcherTest --> Carl
    • CiteSeerTest --> Christoph
    • Mr Dlib --> they migrate to a new server; will be back in September
    • AstroPhysicsDataSystemTest "ADS" --> Christoph
    • IEEETest --> Oliver + Dominik
    • InspireTest --> Carl
• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status and main topic for next release. This time v5.3: https://github.com/JabRef/jabref/milestone/22
• [ x Review Kanban-Board for our tasks: https://github.com/JabRef/jabref/projects/11
  • Archive all done cards
  • Overall status
  • Status of bugs: https://github.com/JabRef/jabref/projects/5
    • Archive all done cards
  • Status of features: https://github.com/JabRef/jabref/projects/7
    • Archive all done cards

2021-06-07, 20oo

• GSoC: Short presentation by Mohit --> https://github.com/JabRef/JabRef-Word-Addin/projects/1
• GSoC: PDF integration
• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status and main topic for next release. This time v5.3: https://github.com/JabRef/jabref/milestone/22
  • How are our priorities ordered? (high to low)
    1. No failing tests --> new minutes point --> volunteer assigned each dev call
    2. Work on release-critical issues --> we have this in our milestone check
    3. Keep number of PRs low --> we through each devcall
    4. Work on other issues --> happens :)
• multi module build (for GraphQL server, small non-GUI CLI, ...)

2021-05-24, 20oo

• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status and main topic for next release. This time v5.3: https://github.com/JabRef/jabref/milestone/22
• Review Kanban-Board for our tasks: https://github.com/JabRef/jabref/projects/11
  • Archive all done cards
  • Overall status
  • Status of bugs: https://github.com/JabRef/jabref/projects/5
    • Archive all done cards
  • Status of features: https://github.com/JabRef/jabref/projects/7
    • Archive all done cards
• Status of PRs: https://github.com/JabRef/jabref/pulls
• Status of old "Waiting for feedback" issues: https://github.com/JabRef/jabref/issues?q=is%3Aissue+is%3Aopen++label%3A%22status%3A+waiting-for-customer-feedback%22+
• Review and tag new issues at https://github.com/JabRef/jabref/issues

2021-05-10, 20oo

• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• JabCon 2021 - 30.8.2021 to 2.9.2021; location TBD (Sindelfingen is open for guests)
• GSoC next steps
  • Two students selected
  • May, 17th: students announced
• http interface to JabRef (main use case: SLR)
  • Should it be REST Level 3 or less | GraphQL | gRPC (== RMI)? --> We should try to use JabRef online for user interface (thus no built-in interface at JabRef)
  • We need to separate org.jabref.logic from org.jabref.gui and craft org.jabref.httpserver
    • maven central - see https://github.com/JabRef/jabref/issues/110
• Discussion on SLR
  • Proposal use Microsoft Academic only (because they are very complete and can do snowballing easily)
  • Re-Implement SLR in JabRef online (TypeScript)
  • Idea: JabRef SLR (server-side; command-line; cron-job) -> .bib -> JabRef online (same server) -> GraphQL API for external access
    • Alternative to "-> .bib ->" --> online sync JabRef <-> JabRef online
• Microsoft non profit
• Review Kanban-Board for our tasks: https://github.com/JabRef/jabref/projects/11
  • Archive all done cards
  • Overall status
  • Status of bugs: https://github.com/JabRef/jabref/projects/5
    • Archive all done cards
  • Status of features: https://github.com/JabRef/jabref/projects/7
    • Archive all done cards
• Status and main topic for next release. This time v5.3: https://github.com/JabRef/jabref/milestone/22
• Status of PRs: https://github.com/JabRef/jabref/pulls

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

• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status of PRs: https://github.com/JabRef/jabref/pulls
• http interface to JabRef
  • Should it be REST Level 3 or less?
  • Should it be GraphQL?
  • We need to separate org.jabref.logic from org.jabref.gui and craft org.jabref.httpserver
• GSoC next teps
• Microsoft non profit
• JabCon 2021
• Review Kanban-Board for our tasks: https://github.com/JabRef/jabref/projects/11
  • Archive all done cards
  • Overall status
  • Status of bugs: https://github.com/JabRef/jabref/projects/5
    • Archive all done cards
  • Status of features: https://github.com/JabRef/jabref/projects/7
    • Archive all done cards
• Status and main topic for next release. This time v5.3: https://github.com/JabRef/jabref/milestone/22
• Status of old "Waiting for feedback" issues: https://github.com/JabRef/jabref/issues?q=is%3Aissue+is%3Aopen++label%3A%22status%3A+waiting-for-customer-feedback%22+
• Review and tag new issues at https://github.com/JabRef/jabref/issues

2021-04-26, 20oo

• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• GSoC next teps
• JabCon 2021
  • August 30, - september 2
• http interface to JabRef --> postponed
  • Should it be REST Level 3 or less?
  • Should it be GraphQL?
  • We need to separate org.jabref.logic from org.jabref.gui and craft org.jabref.httpserver
• Microsoft non profit
• Review Kanban-Board for our tasks: https://github.com/JabRef/jabref/projects/11
  • Archive all done cards
  • Overall status
  • Status of bugs: https://github.com/JabRef/jabref/projects/5
    • Archive all done cards
  • Status of features: https://github.com/JabRef/jabref/projects/7
    • Archive all done cards
• Status and main topic for next release. This time v5.3: https://github.com/JabRef/jabref/milestone/22
• Status of PRs: https://github.com/JabRef/jabref/pulls
• Status of old "Waiting for feedback" issues: https://github.com/JabRef/jabref/issues?q=is%3Aissue+is%3Aopen++label%3A%22status%3A+waiting-for-customer-feedback%22+

2021-04-12, 20oo

• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status and main topic for next (quarterly?) release. This time v5.3: https://github.com/JabRef/jabref/milestone/22
• GSoC 2021 - 30 min
  • Proposal Check until May
• JabCon 2021
  • somewhere between 2021-08-31 and 2021-09-12
  • either Maichingen, Munich, Zwiesel, or #online

2021-03-29, 20oo

• Scite ai integration https://discourse.jabref.org/t/scite-integration/2624
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status of PRs: https://github.com/JabRef/jabref/pulls
• Rename "master" to "main"
• GSoC
• Review Kanban-Board for our tasks: https://github.com/JabRef/jabref/projects/11
  • Archive all done cards
  • Overall status
  • Status of bugs: https://github.com/JabRef/jabref/projects/5
    • Archive all done cards
  • Status of features: https://github.com/JabRef/jabref/projects/7
    • Archive all done cards
• Status and main topic for next release. This time v5.3: https://github.com/JabRef/jabref/milestone/22
• Status of old "Waiting for feedback" issues: https://github.com/JabRef/jabref/issues?q=is%3Aissue+is%3Aopen++label%3A%22status%3A+waiting-for-customer-feedback%22+
• Review and tag new issues at https://github.com/JabRef/jabref/issues

2021-03-15, 20oo

• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status of PRs: https://github.com/JabRef/jabref/pulls
• Rename "master" to "main"
• GSoC
• Review Kanban-Board for our tasks: https://github.com/JabRef/jabref/projects/11
  • Archive all done cards
  • Overall status
  • Status of bugs: https://github.com/JabRef/jabref/projects/5
    • Archive all done cards
  • Status of features: https://github.com/JabRef/jabref/projects/7
    • Archive all done cards
• Status and main topic for next release. This time v5.3: https://github.com/JabRef/jabref/milestone/22
• Status of old "Waiting for feedback" issues: https://github.com/JabRef/jabref/issues?q=is%3Aissue+is%3Aopen++label%3A%22status%3A+waiting-for-customer-feedback%22+
• Review and tag new issues at https://github.com/JabRef/jabref/issues

2021-03-01, 20oo

• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status of PRs: https://github.com/JabRef/jabref/pulls
• Review Kanban-Board for our tasks: https://github.com/JabRef/jabref/projects/11
  • Archive all done cards
  • Overall status
  • Status of bugs: https://github.com/JabRef/jabref/projects/5
    • Archive all done cards
  • Status of features: https://github.com/JabRef/jabref/projects/7
    • Archive all done cards
• Status and main topic for next release. This time v5.3: https://github.com/JabRef/jabref/milestone/22
• Status of old "Waiting for feedback" issues: https://github.com/JabRef/jabref/issues?q=is%3Aissue+is%3Aopen++label%3A%22status%3A+waiting-for-customer-feedback%22+
• Review and tag new issues at https://github.com/JabRef/jabref/issues

2021-02-15, 20oo

• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status of PRs: https://github.com/JabRef/jabref/pulls
• Review Kanban-Board for our tasks: https://github.com/JabRef/jabref/projects/11
  • Archive all done cards
  • Overall status
  • Status of bugs: https://github.com/JabRef/jabref/projects/5
    • Archive all done cards
  • Status of features: https://github.com/JabRef/jabref/projects/7
    • Archive all done cards
• Status and main topic for next release. This time v5.3: https://github.com/JabRef/jabref/milestone/22
• Status of old "Waiting for feedback" issues: https://github.com/JabRef/jabref/issues?q=is%3Aissue+is%3Aopen++label%3A%22status%3A+waiting-for-customer-feedback%22+
• Review and tag new issues at https://github.com/JabRef/jabref/issues

2021-02-01, 20oo

• Status GSOC application
  • deadline: 2021-01-29
  • [email protected]
  • Finish GSOC Application setup
  • Finish ideas list
• Should we pay UX experts to design the next iteration of the entry editor (e.g. via https://www.fiverr.com/categories/graphics-design/web-plus-mobile-design)?
• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status of PRs: https://github.com/JabRef/jabref/pulls
• Status and main topic for next release. This time v5.3: https://github.com/JabRef/jabref/milestone/22

2021-02-08, 20oo

2021-01-18, 20oo

• Status and main topic for next release. This time v5.3: https://github.com/JabRef/jabref/milestone/22
• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status of PRs: https://github.com/JabRef/jabref/pulls
• Should we enable GitHub discussions?
  • https://github.blog/changelog/2020-12-08-github-discussions-now-available-as-a-public-beta/
  • Example discussions:
    • https://github.com/githubevents/universe2020/discussions
    • https://github.com/MiKTeX/miktex/discussions
    • https://github.com/telegraf/telegraf/discussions
  • Decision: We keep https://discourse.jabref.org/, because a) it works and b) one of our maintainers is active there.
• Status GSOC application
  • deadline: 2021-01-29
  • [email protected]
  • Im googe Drive: GSoC 2021 application

2021-01-04, 20oo

• Status and main topic for next release. This time v5.3: https://github.com/JabRef/jabref/milestone/22
• Devcall issues: https://github.com/JabRef/jabref/issues?q=label%3A%22status%3A+devcall%22+is%3Aissue
• Devcall PRs: https://github.com/JabRef/jabref/pulls?q=is%3Apr+label%3A%22status%3A+devcall%22+
• Status of PRs: https://github.com/JabRef/jabref/pulls

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.