Skip to content

Minutes 2015 to 2020

Jump to bottom
Oliver Kopp edited this page Jan 3, 2022 · 1 revision

DevCall Minutes - 2015 to 2020

2020-12-28, 16oo

  • Status of release announcement of v5.2
  • Minor fixes

2020-12-21, 20oo

2020-12-07, 20oo

2020-11-23, 20oo

2020-11-10, 8oo

2020-10-13, 8oo

2020-09-29, 8oo

2020-09-15, 8oo

JabCon 2020: 2020-09-01 to 2020-09-02

  • two days for JabRef

2020-08-18, 8oo

2020-08-04, 8oo

  • Status and main topic for next release. This time v5.1: https://github.com/JabRef/jabref/milestone/20. We had to move some issues to v5.2 to have a change to release v5.1 before JabCon
  • JabCon 2020
  • Do we really want to have JabRef as a registered trademark? -> Yes, the upcoming JabRef e.V. will protect the name

2020-07-21, 8oo

2020-07-07, 8oo

2020-06-23, 8oo

2020-06-09, 8oo

2020-05-26, 8oo

2020-05-12, 8:00 to 9:00

2020-04-28, 8oo

2020-04-14, 8oo

2020-03-31, 8oo

2020-03-17, 8oo

  • Funding to create Apple Developer account (99 Euro / year) and Microsoft account (17 Euro once?)
    • Required for the JabRef Browser Extension
    • "Nag" in the extension for donations
    • Checkpoint 2021 for usage - build-in at Apple
    • Current numbers at Firefox: 2000 users/day
  • Can we fund GitHub pro for each dev who asks for? --> https://github.com/pricing
    • Should be focused on JabRef
  • SnapCraft dev build: Is once a day enough? Or even once a week? I think, we should not spam snap.
    • Main reason: Increase build time
    • Other distributions: nightly builds
    • Decision: nightly builds (once a day); beta releases coupbled to JabRef beta releases.
    • Similar for chocolatey --> refs https://github.com/JabRef/jabref/pull/5378
      • offers "beta" channel only
      • we offer "jabref-nightly"
  • loss of freeze label -> how do we deal with lost issues and how to deal with future issues? Our text sent up to now:

    We are currently trying to focus on other things. 🔥 We will come back later to this topic, therefore closing adding freeze label and closing the issue for now.

    • "lost" frozen issues: Use the text above to search for
  • Preparation for student projects: Preparation by @koppor, discussion in the dev calls.
  • We create a page guiding lectures.
    • Link from CONTRIBUTING.md.
  • Reminder: Project board: https://github.com/JabRef/jabref/projects/5

2020-03-03, 8oo

  • Release 5.0 -- we try to do it today. Blog post etc will be finished next week.
  • JabCon 2020
  • Use "Added" from KeepAChangelog (https://keepachangelog.com/en/1.0.0/ )
  • Swags?
  • Vision 2020
    • Stabilize JabRef 5.0
    • Increase visibility of JabRef 5.0

2020-02-26

2020-01-31

2020-01-05

2019-11-22

2019-07-13

  • GSoC
  • Mentor Summit: Christoph and Tobi will go
  • Polish language (Request from Crowdin)
  • Olly has to write certificate authority an email to cancel the process
  • Collaborate with https://ra21.org/?
  • JabRef Code and Sleep Sindelfingen

2019-04-30

  • GSoC
  • Developer Meeting in Stuttgart (this time for real), ask Oliver for dates
  • LaTeX2Unicode Create a PR to get the JabRef behavior, else create a fork to get our tests green and move on.
  • JPMS Closed this PR, needs to be re-done.
  • Status of Swing Removal Define an Exception for the UndoManager, merge as fast as possible

2019-03-29

  • Introduction of the people in the devcall
  • GSoC
    • Application closes in 11 days, we should support the candidates with good PRs so far in guiding them to useful projects
  • #4707 Group and reorder the Main Menu (tabs & icons)
    • How to group the items in the menus?
    • Martin will create additional documentation in the Wiki
    • Will subsequently create an issue to check if everything is correct according to the specification in the Wiki
  • #2115, #4798 Entry Editor Issues
    • Entry Preview should be an additional tab? So where should we put it?
    • How should the Entry Editor look in future?
    • Multiline-vs-single fields (year, bibtexkey) Tobi will implement this
  • #4689, #4690 Identifiers in the Entry Editor
    • Implement as proposed, in case of URL in a MISC entry: duplicate it to required fields and Web Resources
  • #4688 Entry Editor: change Optional Fields tab
    • Robin will have a look
  • #4694 Remove global search feature
    • Remove it for now and think about search in general
  • #4717 Remove "plain text import" feature
    • Remove for now an create followup issue
  • Discussions for Leisure Time: Firefighting Drones

2019-02-19

  • Olly has to write certificate authority an email to cancel the process
  • GSoC: Let's see if we get accepted and how many students apply.
  • JabCon Sindelfingen: Olly's house warming party (to be announced)
  • Martin has presented his Masters's thesis at ZEUS
  • Remove Swing in about two months, then release!

2019-01-25

  • Certificate
    • Try to abort the process, get money back.
    • Talk to Oliver
  • Features that should be implemented as part of the student project of Igor Steinmacher
    • Talk to Oliver at ZEUS
  • Architecture Analysis with KAU/Joerg Lenhard
    • Seems to be upcoming.
    • Christoph takes care about it with Joerg
  • JabRef Usability Study Results
    • Martin reports about his project
    • Martin will create issues in Github.
    • ZEUS Paper is under review
    • Blog entries about the usability
  • Mr.DLib UI experimentation
    • They can do that if the UI versions are still reasonable.
    • Focus should be on great recommendations.
  • Google Summer of Code
    • Which project? PDF integration: Search PDF, Import Metadata, PDF viewer.
    • Alternative: Social Features, sharing of references, Chrome integration
    • More interplay between references and papers.
    • MS Word integration
  • 5.0 Alpha Release
  • JabCon?
    • Since most people are not there, there will be no JabCon
  • Merch
    • Buy some swag for the ZEUS participants
    • Pro magnets

2018-11-16

  • Chaos Communication Congress Assembly?
    • No formal assembly, maybe join another assembly
    • We'll meet in Leipzig (Christoph, Tobi, Linus)
  • Certificate
    • no new progress
  • Google Summer of Code https://developers.google.com/open-source/gsoc/timeline
    • Deadline Feb 6, 2019
    • Define topic at 35c3, probably around PDF integration
  • Hacktoberfest
    • Many contributors, overall good quality
  • Christmas release of first beta v5.0?

2018-10-26

  • JabCon 2019/Zeus 2019
    • Dates are problematic for Tobi and Linus. Christoph unclear, due to job in 2019.
  • Chaos Communication Congress
    • Potentially nice opportunity to meet people and prospective contributors
    • Linus is going, Christoph is interested, Tobi maybe 2 days
    • Organizing an assembly? Maybe if we have 4 JabRef people?
  • Hackathon in Paderborn in March
    • Maybe not the best opportunity to meet
  • Recommendations/Mr.Dlib
  • Certificate
    • Comodo ignores the ticket for validation. Try to escalate?
  • JabRef Usability Study
  • 5.0 Release
    • Bugfixing
    • Stable in MS Windows
    • Unstable in MacOs
    • 5.0 should run in Java9

2018-06-29

  • Logo-Lizenz (ETH-Mail) (via @koppor)
  • Android App for JabRef (via @koppor)
  • Paper with Jöran (via @koppor)
  • Igor Steinmacher - OSS course (via @koppor)
    • ideally sometime between July 4 and July 10, in a time slot that's not too awkward from China (realistically morning or early afternoon Germany time).
  • Usability Master Student at TUM
  • Everything tagged with devcall - includes closed issues and closed PRs
  • PR status?
  • Status and main topic for next release. This time v4.4 and v5.0.

2018-06-01

2018-04-20

  • Merchandise:

    • Linus collects cups and flyers in Bamberg on April 30.
    • Flyers are distributed in Bamberg by the university library
    • Each SOSE conference participant received a flyer
    • Stefan can send everybody JabRef flyers
    • Tobias checks if the MPI has resources to print the flyers locally
    • Check possibilities for creating a own store with merchandise products

  • Code Signing Certificate

    • Needs some more time :/

  • Status of maintable-beta (imho we cannot maintain two versions for too long side-by-side)

    • Implementation is hardening, still some minor bugs. Performance problems?

  • Rename maintable-beta branch to v5

    • To be done together with the first alpha/beta release

  • Status of next release

  • Release 4.2 soon, even without Code Signing Certificate. Remaining issues: https://github.com/JabRef/jabref/milestone/17

Topics discussed in each telephone conference

2018-02-23

  • rueckblick jabcon
    • Merchandise - Was genau? (T-Shirts?) Bug Bounty
    • Bugs fixen! Stability coding instead of features?!
    • Issues gemeinsam durchgehen
    • Status codesigning: March, 6th
  • Flyer: Looks good. Can be printed when comments are incorporated. Linus wants 100 pcs.
  • Featureset next releases. What should V5.0 be?

    • 4.2 when certificate is ready

    • discussion: javafx

      • Drivers:
        • test user for javafx thing
        • Being release ready
        • conflicts at branches
        • testing to public should offer a thing without obvious issues
        • maintable takes approx. 4 month to be finished after start of test phase
      • Ideas:
        • stable branch + master branch (javafx)
        • maintable branch (javafx) + master branch
      • Decision:
        • after 4.2 release:

          • master gets maintable-beta merged

          • stable branch branch for bug fixes to keep it release ready

          • stable always (!) merged into master

            • Idea: 5.0-alpha release, can be continiously made alpha-1, alpha-2, ...

    • Discussion

      • new PRs should target maintable-beta branch
      • new PRs should target master branch
  • Everything tagged with devcall - includes closed issues and closed PRs
  • Social media buttons: will be tracked and we check whether they are really used
  • PR status?
  • Status and main topic for next release. This time v4.2.

2017-01-12

2017-12-22

2017-12-08

Next telco - 2017-12-08

  • Code Signing Certificate
  • JabCon - optinally Monday

Topics discussed in each telephone conference

2017-11-22

  • Code Signing Certificate - waiting for feedback
  • JabCon
  • Alternatives to versioneye. Think, we need to develop a stripped-down version
  • Merged some PRs to prepare version 4.1.
  • Release 4.1 after code signing is clear.

2017-11-07

2017-09-18

2017-08-31

2017-08-25

2017-08-10

2017-07-18

Topics discussed in each telephone conference

2017-07-11

2017-05-30

2017-04-24

2017-04-06

2017-03-27

Telko - 2017-03-09

Topics discussed in each telephone conference

Telko 2017-01-20

2016-12-22

2016-12-16

2016-12-09

JabCon tasks

  • We need Skype telco and maybe beamer for all that can't be in Lugano but maybe are able to code with us on that day!
  • Talk about all open issues is what we do at JabCon

JabRef

2016-12-02

2016-11-07

2016-10-20

2016-10-06

2016-09-28

2016-09-21

2016-09-13

2016-09-06

2016-08-25

2016-08-18

2016-08-09

2016-07-26

  • Icon contest
    • nothing happened yet
  • PR Reviews: perform real tests of changes - not code review only (Matthias)
    • Checking whether implemented/changed feature is (still) working in the normal user workflow
    • Simon: Add another bullet point to PR template: "Manual test in GUI successful"
  • Remove option "enforce illegal characters in bibtex keys"
  • Everything tagged with devcall
  • https://github.com/JabRef/jabref/milestone/9 fixed to 2016-09-01
  • JavaFX should be added as pull request to enable reviewing
  • Reduce issues: Concrete Milestones in JabRef 2.x did not work out - "fixup" and "next version" were pseudo milestones, not working out either

2016-07-13

  • label "fixed-in-master" should be used rarely
  • Icon contest
    • Stefan, Olly, Tobias, Matthias: Logo-Contest
    • Jörg, Simon: Peter-Logo-Aufhübschen
    • -> Matthias und Stefan
  • Licensing
    • Simon, Jörg, Olly, Matthias, Stefan: für MIT
    • Tobias: Code sollte wieder veröffentlicht werden müssen, also EPL, MPL, GPL, .. OK
    • Our licenses listed in external-libraries.txt allow the switch
    • Olly kümmert sich
      • CONTRIBUTING.md -> ab sofort MIT
      • Kritische Stellen im Code suchen und Leute anschreiben
      • Alle Leute anschreiben und informieren
        • Hold the current momentum, preserve energy we currently invest
        • Simple license, widely used, not restricting development and distribution
      • Final switch
  • Future of JabRef
    • Button in Toolbar (+: Jörg, Simon, Olly; -: Matthias; 0: Stefan, Tobias)
  • JabRef Architecture - https://github.com/JabRef/jabref/wiki/High-Level-Documentation
    • Checkstyle can enforse our rules
    • Alle Paramter sollen Logik explizit übergeben werden, so dass unabhängig von Globals.Prefs, wo so "magischerweise" Verhalten geändert wird
    • Idee: Logik als JSON-API ins Web stellen
  • Release v3.5 on 2016-07-14
    • Stefan and Olly

2016-07-06

  • Milestones v3.5
  • Group renaming works
  • Hierarchical Groups
  • Next release as soon as #1495 is fixed.
  • Aim for 3.6: Number of opened bugs below 10
  • Icon contest?
  • Financial Status
  • Licensing
    • MIT: As many persons should be able to use the software

2016-06-28

2016-06-14

  • a bug fix release should be published ASAP; to be included:
    • #1481: Broken Mac OS X installer
    • #1434: static vs. dynamic
    • #1482: correct number of hits
  • Levenshtein lib: to replaced by apache commons? Olly tries replacement
  • JabRef 4.0. Target date: October 2016 and fix issues such as #1179
    • Milestone already exists - date not yet fixed
  • Clear workflow when to merge PRs. Personally, I'm looking for a more focused discussion and workflow.
    • Stefan: Define clear main topic for each release to concentrate on a common goal - which also improves review ability/quality
  • PR #1471: comments in bib file are preserved
    • will be part of 3.5 and not integrated in 3.4.1
  • GUI tests randomly fail, its annoying for PRs etc...
    • fixed by Olly

2016-05-10

  • Bundle Jabref for app stores? See #1371.
  • evaluate auto update by students. maybe we should use something like texcenter that just displays a dialog and a link rather than auto downloading it (donations). we need to evaluate what install4j can do!
  • We need to keep the number of issues down. The more issues we have the more immature and buggy our product looks. Other projects have pointed this out as well.
  • focus of releases and work packages
  • Close old waiting-for-feedback issues? Close after 4 weeks.
  • Do not mark as bug if it wasn't reproduced yet
  • Wiki Migration von Sourceforge - anything interesting still in the old wiki? Otherwise remove the link
  • Developer++?

2016-04-12

  • Do we want to order JabRef gadgets, e.g., T-Shirts, mugs, stickers, etc.?
    • Do we need a new logo? - See #1177
  • Package renaming net.sf.jabref to org.jabref. Relates to #152. Filed at #1179
  • Issues targeted for next release
  • Everything tagged with devcall
  • #496: Should the possibility to define more than one file-directory be added?
    • Decision: If someone else comes up with the same issue, we will have a look again
  • We need help from our users in documenting JabRef. A shout out to the mailing list should be made - no programming skills required, only motivation to help JabRef.
    • Mail after release
  • Developers should favor pull requests over issues for minor things, e.g., #963, for less bureaucracy
  • FXML vs. Java Code for building the JavaFX UIs, see pull request
    • We move forward using FXML
  • discussed some pull request, including blog posts.

2016-04-01

2016-03-30

  • Worked on PRs and Issues

2016-03-08

2016-02-24

  • Plan for 3.3: focus on bug fixing; no new features should be added until release of 3.3
    • planned release date for: 1st week of March
  • Issue status targeted for next release
    • partially discussed
  • All issues tagged with devcall
    • #825: Postponed to 3.4, awaiting feedback from users
    • #629: will be implemented; goal 3.4
      • UI should remain the same
      • technical side: only dynamical groups
      • migration is important
  • https://github.com/blog/2111-issue-and-pull-request-templates
    • updated during dev call: see #836
  • Hosting of binaries:
    • Hosting on all platforms: sf.net; github and fosshub.com
    • Default download platform used @jabref.org: fosshub.com
  • Pull Requests without tests - OK or NOT OK?
    • new/changed model/database code should be tested
    • UI tests not mandatory
    • minimal requirement: at least one test
    • adjust PR template
  • Cleanup branches on builds.jabref.org
    • Olly will try to automate deletion (trash everything older than one month)
  • UI tests... still not working; should be checked how to execute stabily on travis-ci
  • stupro PRs: should be made ready for merge - will be closed otherwise in the next days

2016-01-08

  • 3.2 with current state
  • JabCon
    • Currently registered: 2 + Orgas + 1?
    • Travelling through Nuremberg
    • Informal presentation at beginning of conference, infos presented in Wiki @olly email
  • Branches - at JabRef/jabref or each developer on his own
    • Currently, there are many branches which are all copied to all forks. Users have difficulties to get rid of them
    • Proposal: keep only "master" and "dev_2.11"
    • EVERYTHING IS LEFT AS IS
  • BibType - see https://github.com/JabRef/jabref/pull/605
    • skype call required, make advantages more explicit through bullet list

2015-12-15

  • Last telco items done?
  • Badge Wahnsinn inside README file
  • travis-ci reactivating because CircleCI cannot automatically inform the committer of a failing commit. This is annoying, especially for the stupro as well as PRs. We should add travis-ci only for executing the tests (which is fast, compared to building the binaries and other checks)
  • Look-and-Feel: Use Metal for Linux as default because other LaF fail when used with openjdk?
  • 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...
  • Should we add Objects.requireNonNull to the code howtos?
  • Log output of exceptions: LOGGER.debug("msg", e); vs LOGGER.debug("msg" + e.getMessage()); vs LOGGER.error("runCommand error: " + ex.getMessage(), ex)
  • https://github.com/JabRef/jabref/issues/447 -> Handling of BibTeXEntryTypes
  • Each bibtex entry should store a latex-free version of its fields for searching and passing to search engines. Add wrapper to be able to change default returns of getField to latex-free version of the field value.: getField and getFieldRaw. See https://github.com/JabRef/jabref/issues/518
  • https://github.com/JabRef/jabref/pull/391 - How are we dealing with linebreaks? CRLF vs. LF? When the bib file uses CRLF, the user has set "LF" as separator, and the user changes something, the updated entry is written using LF, whereas the other parts of the file are written using CRLF. This leads to a mix of CRLF and LF, which is not professional.
    • Discussion: always LF vs. configurable CR/LF.
    • Keep as is. Mixed cases seem to appear very rarely.
  • bibtex/biblatex handling + fetcher - what is the strategy behind this?
    • Each fetcher has to take care
  • biblatex: journal as alias for journalTitle. How to treat?
  • https://github.com/JabRef/jabref/pull/472 - non-empty fields in the main table also for @Book.
  • must be implemented "vernünftig (matthias)" "Entry table -> fit table horizontally ...."
  • 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.
  • koppor/jabref/issues vs. JabRef/issues. Should JabRef/issues the primary repo? (see https://github.com/JabRef/jabref/issues/455#issuecomment-161713097 - which says "no" to that)? Should we point users to koppor/jabref? (That was NOT the real intention). Should we close down koppor/issues (and have 100+ open issues at JabRef/issues)? Leave everything as is, but have JabRef/issues as main issue repo?
  • Issues at koppor/jabref create another issue repo. I think one tracker is enough and issues are important or not.
  • sponsoring: what defines a sponsor?
  • Licensing
  • https://github.com/JabRef/jabref/issues/483: Should we fix erroneous bibtex files?
    • We will create a page showing the quality of the exported bibtex entries
  • PR status?
  • v3.1 issue status
  • When should 3.1 be released?
  • Sorting and Output Format: Fix rules vs. only format what has changed
    • Use standard format for new things, keep existing format
    • Sorting Strategy of Entries: change as little as possible on load/save-cycle; no sort; insert on new entries on bottom
    • New entries: write with fixed format, but for existing files use
    • Only format entry if it is changed
    • Casing for keys: only lower case
    • Casing for entry types: camel case
    • Content: do not change anything
    • Indent: = aligned on one space after longest key
    • Formatter: cleanup on load moved to separate formatter with defaults
    • Tests are required for to implement these! According to BibtexEntryWriterTest.roundTripTest. For each entry type and formatting option.

2015-11-23

  • jabref.org
    • works now
  • Ensure consistency of "file linking" actions - see also https://github.com/JabRef/jabref/issues/190
    • Solution: Remove icon on the left; Remove "Download"; Auto: if not found, say "not found. please input URL . [OK] [CANCEL]";
    • For a single entry: Look up full text document in local folder, Look up full text document in web, Download document from URL (also check what Tools -> lookup full text document)
    • For a bunch of entries: Synchronize (combination of find unlinked and automatically set file links)
  • Fetchers/Web Search:
    • Distinguish between simple "fetch by key" and free keyword search? Different menu items?
    • UI Improvement: Default: Web search should be opened and "DOI to BibTeX" (or "ISBN to BibTeX") should be selected as default. (refs: handling of minor issues)
    • UI Improvement: "Add entry": Should we add "from DOI", "from ISBN" ... there? Maybe move all the non-search fetchers to there?!
    • @koppor creates issue
  • How do we treat http://www.nature.com/news/eight-ways-to-clean-a-digital-library-1.18695 ?
    • done, no reaction
  • Use online instead of offline help files? (add by Matthias)
    • Pros: Easier to update, easier to add translations
    • Cons: Internet access required (but can be assumed nowadays?)
    • For 3.0: Update documentation rudimentary
    • For 3.1+: Online + markdown + own repository
  • Search
    • Concurrency Bug
    • Documentation
  • Add section about current dev-strategy to wiki?
    • done
  • Unique selling point: customization in JabRef?
    • we know it
  • Do we want http://feathub.com/JabRef/jabref (svg might not be displayed?!)
    • Too early, maybe later when JabRef is more mature.
  • STUPRO: test strategy for the importers:
  • Formatting: Tags everywhere (why??), strange behavior in some PRs with indentation
    • should be reduced, maybe through better language script
  • https://github.com/koppor/jabref/issues/36
    • done
  • https://github.com/koppor/jabref/issues/34
    • done

2015-11-10

  • Next version: 3.0
    • Yes
  • Remove Gitter
  • install4j: jre bundle download over jabref.org; oracle license of bundling jre
    • It is allowed to bundle and distribute. Use with jabref.org. Maybe use for 3.0?
  • We release 3.0 on the 12th anniversary on 29 November
    • Yes. Create branch on 20.11. for jabref-3.0
  • CircleCI: Automatically run generate-authors.sh?
    • No, must be done manually for consistency reasons.
  • Format whole code according to the new formatting rules?
    • No, because of git blame
  • Sorting and Output Format: Fix rules vs. only format what has changed
    • Use standard format for new things, keep existing format
    • Sorting Strategy of Entries: change as little as possible on load/save-cycle; no sort; insert on new entries on bottom
    • New entries: write with fixed format, but for existing files use
    • Only format entry if it is changed
    • Casing for keys: only lower case
    • Casing for entry types: camel case
    • Content: do not change anything
    • Indent: = aligned on one space after longest key
    • Formatter: cleanup on load moved to separate formatter with defaults
    • Tests are required for to implement these! According to BibtexEntryWriterTest.roundTripTest. For each entry type and formatting option.
  • spin.jar: remove now or with transition to JavaFX?
    • On transition to JavaFX
  • Highlight vs Pinning for marked entries (see preferences -> entry table -> float marked entries ...)
    • Add toggle button for float on/off and move out of preferences menu
  • New default setting for Use native file dialog: Yes? Should we remove that option completely?
    • native: java icon, but right-click as usual (on Mac OS X really better than our dialog)
    • our dialog: jabref icon, but right-click only our options
    • (Windows) sieht sonst ziemlich gleich aus
    • native always on without option
  • Translations: switch to pull requests
    • olly asks @mlep
  • SourceForge Tracker: Close/Make ready-only
    • is already read only
  • Pull requests: Codecov auf geforktem Repo? --> Wie können die Studis sehen, ob sie alles "erwischt" haben?
    • EclEmma in Eclipse or simply in IntelliJ IDEA
  • Search #164 and #104
Clone this wiki locally