Small update pt. 2: we are finalising the draft for the new contract.
Thanks for the update.
And, for the record, happy to see this: a project with sufficient funds supporting one we (and others) use that struggles a bit.
Thanks a lot to @ilmari for working on this! The developer situation around BugZilla is much more demanding than I had assumed, in the sense that very few developers seem available, so it took a while to come up with a plan B.
We have indeed someone willing to work on it, and have a contract draft. Should there be no blockers, we will hopefully have some good news soon! Thanks again to Ilmari for making that happen!
Just out of interest, are TDFâs new mandatory contract terms affecting the situation at all?
No. Even without getting to the contractual terms, the amount of potential developers seems very, very low.
Quick update before the weekend: The final contract draft is now in review, so I hope we can announce progress soon.
We need to update some bits and pieces of the contract. As you can imagine, currently everyone is quite busy, but weâll get to this shortly. In particular in light of issues from the past, TDF is eager to have proper contracts in place, which is a bit more challenging when contractual partners can be worldwide. Additionally, as you have seen, Bugzilla has its own set of challenges, and we want to ensure things work smoothly this time.
Weâre not sharing the contract here because weâre still in negotiations with the service provider about the details, but the scope is as outlined above already.
In particular in light of issues from the past, TDF is eager to have proper contracts in place
Issues from the past regarding Bugzilla development support?
Also, are we still negotiating with the same individual from January?
We had a contract in the past with a different service provider. After several prolongations, that contract was eventually ended without the final deliverable, only parts were done (and paid).
It seems extraordinarily complicated to find a developer for Bugzilla who is also available for contracted work, which is quite concerning.
We had an initial contact with the potential new contractor probably in January, but the first time we had a call about details was early March, and the first contract draft was provided to us about two months ago in mid-March.
Well, letâs hope they donât lose interest.
I am even more worried about the sustainability. If there is one person who can realistically work on a tool we rely on, that is worrying. TDF was willing to spend money, but it was not easy to find someone who was willing to deliverâŚ
I suppose itâs easier for us (and other BZ users) to coast without active maintenace using the now-venerable Bugzilla 5.x versions, rather than a new version a lot of changes, which will have some teething issues.
The scope of the contract is the Bugzilla 6.0 release actuallyâŚ
The contract has been approved today. The expected delivery time is tentatively October 31, but weâre waiting for final clarification on that.
Given the contract discussions took some weeks, weâve agreed on the new delivery date to be December 31, 2026. We will keep you posted about the progress here.
Thanks a lot to @ilmari for driving all this!
@ilmari : Your efforts on this are very much appreciated indeed. If this comes through, it would be a boon for a huge number of people and projects, much more than just us.
That is indeed one of the goals, like we also did with Pootle, Weblate, Jitsi, CiviCRM and other projects in the past: improve software we use and rely on, but make available the result to everyone, so many other projects benefit from it.
It is a tough ride this time, and I am a bit concerned that hat the amount of available developers for BugZilla seems so low, but I am looking forward on getting the final deliverable.
It would probably be a good idea to blog about these fundings we do and what their outcome was.
I just wonder, but i do not know the contracts: i do know that tdf is/was in curt (or at least off-curt lawyerâs talk) for having major problems with cib/allotropia/collabora for not shipping the contracted results.
What is different in this case?