I do want to get involved in the ResourceStore API discussion.
Unfortunately, I’ll be on vacation next week, so if you don’t mind I propose we leave it off from this release.
Meanwhile, I’d like to ask Niels to update the PR description with a (rather succinct) description of the issue and breakdown of the approach. That helps a lot in reviewing, and going through the very long discussion on the email list is draining.
TIA,
Gabe
···
camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS
I wish I had done it earlier actually, because it would have helped me remember the details which are already fading
Regards
Niels
···
On 16/02/2024 15:36, Gabriel Roldan wrote:
Hi,
I do want to get involved in the ResourceStore API discussion.
Unfortunately, I’ll be on vacation next week, so if you don’t mind I propose we leave it off from this release.
Meanwhile, I’d like to ask Niels to update the PR description with a (rather succinct) description of the issue and breakdown of the approach. That helps a lot in reviewing, and going through the very long discussion on the email list is draining.
TIA,
Gabe
camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS
Thanks Gabe for being clear - we are operating with reduced resources these days and I need to ask for help where it can be effective.
Niels I have set aside time next week to fix the bug getting in your way (for sure); and go over the javadocs API changes to see if we can work out a compromise.
···
–
Jody Garnett
camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS
Just to be clear, in my pull request I did take account of our discussion and your concerns, we had arrived at a vague outline for a compromise that I tried to respect as much as possible, filling in the gaps.
I will provide more information soon.
Kind Regards
Niels
···
On 16/02/2024 20:49, Jody Garnett wrote:
Thanks Gabe for being clear - we are operating with reduced resources these days and I need to ask for help where it can be effective.
Niels I have set aside time next week to fix the bug getting in your way (for sure); and go over the javadocs API changes to see if we can work out a compromise.
I do want to get involved in the ResourceStore API discussion.
Unfortunately, I’ll be on vacation next week, so if you don’t mind I propose we leave it off from this release.
Meanwhile, I’d like to ask Niels to update the PR description with a (rather succinct) description of the issue and breakdown of the approach. That helps a lot in reviewing, and going through the very long discussion on the email list is draining.
TIA,
Gabe
camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS
I do want to get involved in the ResourceStore API discussion.
Unfortunately, I’ll be on vacation next week, so if you don’t mind I propose we leave it off from this release.
Meanwhile, I’d like to ask Niels to update the PR description with a (rather succinct) description of the issue and breakdown of the approach. That helps a lot in reviewing, and going through the very long discussion on the email list is draining.
TIA,
Gabe
camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS