Future of Exiv2 #1466
Comments
|
@boardhead: I hope you will be able to join us. |
|
Slides for the meeting. |
|
Meeting notes of 2021-02-27 Participants:
Join OIN (open invention network)?
Exiv2 after v0.27.4?
There is no active plant for development of Exiv2 beyond 2021. |
|
It was nice to see you again after such a long time! Just a small nitpick: I'm still in favor of naming the new main branch 'master' rather than 'main', because to any outsider, 'master' is the most obvious name for "the git branch to use" (for final testing, pull requests, etc.). |
|
That's the new default in git, github and many other installations... |
|
Thanks, Volker @vog. Maybe I'll do that. Yesterday I changed the name of 'master' to 'old-master' to discourage anybody from submitting further PRs. I also set '0.27-maintenance' as the default branch. I should close all the open PRs on 'master' and explain what's going to happen. By the time we ship 0.27.4 on 2021-05-22, it'll probably be safe and reasonable to branch an new 'master' from 0.27-maintenance. I want to retain the 0.27-maintenance branch in case we need a 0.27.5 security update in future. We haven't had a security issue raised on the code for almost 18 months. Your comments are appreciated. Thank you for contributing. @phako. Are you saying 'main' is the new default? I thought somebody said that during the meeting on Saturday. |
|
yes, at least for github, see https://github.com/github/renaming. I thought git itself had switched as well but I cannot find any reference for it in quick search, only heated discussions why this is "PC gone mad" |
|
It's not (yet?) a default in git, but the default branch has recently(ish) been made configurable: https://github.blog/2020-07-27-highlights-from-git-2-28/#introducing-init-defaultbranch |
|
@phako @imsodin Thanks for clarifying the issue with I fully agree that, given those circumstances, By the way, I never liked the wording |
|
Thanks you everybody for your comments. I've had a message from @alexvanderberkel saying 'main' is the new 'master'! Let's stick to the plan. On 2021-05-22, I'll branch 0.27-maintenance -> main and make 'main' the default branch. I've already renamed 'master' -> 'old-master' to discourage its use. |
Sorry, I missed this. I haven't been keeping up with all of the Exiv2 posts recently. |
|
Exiv2 v1.00 We are now within sight of Exiv2 v1.00 and could achieve that by the end of 2021. In many ways this is a more desirable goal than KDE. Exiv2 declaring v1.00 says Exiv2 is complete. If KDE wish to take over the project in 2022, that will be fine. I think it's better to use our limited resources to reach Exiv2 v1.00 on GitHub and not put effort into working with KDE.
We hope to have a Zoom meeting on the weekend of 24 April or 1 May to discuss the plan and assignments.
The schedule looks like:
The detailed task/priority list is still below. I hope each group will complete their Priority tasks by 2021-06-30. If we have to drop lower priority tasks to make the schedule, we will. If we hit Priority Complete in late June, success is certain. The commitment of time per contributor should be of the order of 100 hours. I suspect the metadata group tasks will require more than 100 hours per contributor. I will work on/with any group as requested in addition to dealing with users, release engineering and project management. Please be aware that the task list is based on open issues on 2021-04-13. New issues will be reported during the life of the project.
|
|
I can and will finish localisation to Slovak & Czech, my primary and secondary languages. |
|
Also, please correct JXP/codestream to JXL as an abbreviation of JPEG XL. Thanks. |
|
Thanks for your input, Peter (@1div0). This is forming a nice project. Nobody has to do a lot of work and nobody is stuck with this forever and ever. Apparently KDE have localisation folks to whom we can send the files. I've never discovered how to access that channel. I'm thinking about bullding RC2 next week to include the JXL/bmff code. The code will then be frozen and I will open branch 'main'. I'm meeting with Luis this afternoon to discuss auto_ptr/C++20. |
|
I do have a very good experience with https://crowdin.com for ML based localisation. Probably worth to explore. |
|
If there's interest, I could volunteer to localize to Brazilian Portuguese (my native language). I also have previous experience with Crowdin. |
|
@lbschenkel Thanks. I've updated the task table. You've got that task. Localisation is documented in README.md. It's driven by gettext technology. I believe this is a commonly used approach. Some companies provide free services and products to open-source projects. Perhaps you could explore that with Crowdin. As Exiv2 has no revenue, so we are unable to pay for a license. |
|
I'm also familiar with gettext, so that is not a problem to me. However, Crowdin can be easier for non-developers to contribute translations since they can do it directly via the website compared to editing PO files, which is a bit awkward. Crowdin is free-of-charge for open source projects, and I could apply on behalf of the project, but only the project lead can do so: https://crowdin.com/page/open-source-project-setup-request |
|
I've filled in the application form. I think they expect you to have already created something on their platform. I don't want to start learning about Crowdin. Is it a big job to tool up to use this platform? Can you set up the necessary resources? |
|
It's not hard. I can volunteer to set the project up as an experiment if you want, and then you can judge if it's something that you think that could be useful to the project. But I think if I do that, it'll be tied to my account at first. I should be able to transfer it to somebody else's account. |
|
I have opened a new issue "Investigate Localisation using Crowdin" for further discussion. #1510 Please be aware this topic "The Future of Exiv2" is circulated to about 200 people who have contributed to Exiv2 since 2004. |
clanmills
added
TeamExiv2
and removed
request
|
Hi guys, I warmly welcome you to the kick-off meeting for our work on Exiv2. Please find attached the prepared meeting slides and meeting details. The meeting is scheduled for: Zoom details The full backlog for the project can be found on GitHub: |
|
I just realized that we cannot use the zoom details of Robin and he is not attending. Please use this link Video call link: https://meet.google.com/ceo-uckx-uof |
|
For Exiv2 1.0, the 'code complete' is scheduled for 2021-09-30. Is this still going ahead? |
|
When I put that in the schedule, I was intending to drive the project and "make it happen". Code-complete is an important milestone to achieve the goal of releasing v1.00 by the end of 2021. I've now retired and leaving Alex to manage the project. He's likely to call a zoom meeting to ask everybody about goals to which they can commit and deliver. My impression is that maintenance, security fixes and user support for Exiv2 is going well. Development of v1.00 is sluggish. However Luis has done the C++11 modernisation and that's important enough to release "main" even although other priority one features (such as Unified Metadata Container and removing xmpsdk from the code base) have not been developed. |
|
Do all major API changes need to be finished before 1.0 is released? I would quite like to try switching the standard size type from |
|
It is very desirable to make big API changes before declaring v1.00. I know Alex has been intending to call a team meeting and this kind of thing should be discussed. Developing every priority one features probably cannot be achieved for several years. Perhaps a good way forward is to aim to release main as v0.9 with C++11 support next year (say June 2022?). The intention with the v0.9 family is to avoid API changes on a series of half-yearly releases (v0.9.1, v0.9.2 and so on). Eventually reaching v1.00 in a few years time. |
|
I think we discuss when we think we are able to release 1.0 and who's committed to work on certain topics. Putting new things into the backlog I would say doesn't put us in a bad situation as long as we have people to work on it. |
|
I have set up a call in the past for 1.0 but there was only one participant. That is why I have not scheduled another call so far. |
|
I think it's kind of difficult to commit to a schedule without full time engineers. I was able to deliver releases to a schedule because I was working full-time on Exiv2. Everybody has full-time and demanding jobs. With the Paris Climate Treaty, Ms. Figueres asked the countries "what can you do?" and drew the canvas from the bids. And I think that's how you'll have to approach Exiv2. Ask "What can you do by March 2021?" and that's the spec for v0.9. Always allow 3 months from Code-complete to GM to allow for several RCs. If code is to ship in June, it has to be written, documented and tested by the end of March. |
|
Release notes for v0.27.5: #1018 (comment) |
The development of v0.27.4 is on track. @clanmills has volunteered to help one last time by shipping v0.27.4 before he retires. I've set up a Zoom meeting to discuss the following two questions:
Zoom meeting details:
Topic: Future of Exiv2
Time: Feb 27, 2021 06:00 PM Amsterdam, Berlin, Rome, Stockholm, Vienna
Join Zoom Meeting
https://us05web.zoom.us/j/87388802811?pwd=RStyUUdRak1aNmRENnRKZ3k1Z3U3Zz09
Meeting ID: 873 8880 2811
Passcode: S0qPG1
This is the list of contributors / people who forked and/or worked on Exiv2 over the years on GitHub.
@1480c1 @1div0 @354380o726502 @5l1v3r1 @a17r @adammartak @ahuggel @alexvanderberkel @AmaniBHH
@AndreasMartin72 @andreilabato @Anmol92verma @anmolvermamm @arkiruthis @asp @astippich @Aurora-Community
@awilfox @badola @bellaperez @bentglasstube @BioDataAnalysis @bkuhls @blockspacer @boardman @BohuaCao
@Cadcorp @caomw @carlosbasecodeit @Cethric @cgilles @chan0415 @clanmills @clayne @clthomas
@codingdave @connectthefuture @criadoperez @cryptomilk @csparker247 @CTF-s @cygwin-lem
@czgnp @D4N @danielkaneider @danileo @dbeichl @Deneb99 @derselbst @devil1437
The text was updated successfully, but these errors were encountered: