here's my current view on the situation on the Tinifier issues. I want to solve it, but want to get my facts straight first.
Tinifier (https://www.nuget.org/packages/Tinifier/) is deprecated.
TinifierNext (https://www.nuget.org/packages/TinifierNext/) replaces it but doesn't play well with Umbraco 8.6 and higher.
An issue was created (https://github.com/dimonser147/UmbracoTinifier2/issues/1) in august, but it seems there is no active development/maintenance.
The contact address '[email protected]' bounces. The website seems unrelated to Umbraco stuff and no longer contains the Tinifier pages.
Is there another package floating around I am unaware of?
Yesterday, I fixed some issues on a fork of the project and got it back in a working state. I would like to make these fixes available and have them tested on more projects then just mine, but then the PR needs to be processed by someone.
Is anyone in contact with the devs?
I noticed some bugs in the dashboard as well, which are minor, but I'd still like to address these as well. If Backend Devs cannot be contacted, I guess the only alternative is to make my fork more permanent and start a new Nuget-package with a new name?
I haven't used the Tinifier package itself (yet), but I'm a big fan of the TinyPNG service. I'm not aware of another package that does the same.
I just wanted to reply to say that I think you're taking the right path with an approach to forking the package/project.
You've reached out to the developer(s) and awaiting a response... as for what timeframe to wait, I'm not sure - people have their own lives to deal with too.
But given that http://backend-devs.com/ appears to be a spam-blog now... and like you say their company website https://www.ssa.group/ doesn't mention Umbraco anymore. I wonder if BackendDevs were acquired?
The only other line of comms I would suggest is the Gmail address listed on their GitHub profile: https://github.com/dimonser147?
I think until you hear back from them, then an interim temporary fork is totally acceptable. With a view of if they do come back, that you'd offer to merge your fork back in to their repo/package, (if they want to accept the amends, of course).
In a nutshell, as a old time package dev, I'd give this approach the thumbs up.
I guess the question comes down to whether you want to maintain the code/package moving forwards?
I also did find the gmail address. I'll give it a couple of days.
In the mean time, I'm communicating with the poster of the Github-issue to see if I can reproduce his issue, which seems to be separate from mine at the moment.
I'd be willing to maintain the package as I find it very valuable. I've read a post saying it clashes with umbraco Forms (DI-wise), which might be a different barrel of fish to tackle. We'll see.
Tinifier 2.0.2 and v8 - let's solve this!
Hi to all Tinifier fans,
here's my current view on the situation on the Tinifier issues. I want to solve it, but want to get my facts straight first.
Yesterday, I fixed some issues on a fork of the project and got it back in a working state. I would like to make these fixes available and have them tested on more projects then just mine, but then the PR needs to be processed by someone.
Is anyone in contact with the devs?
I noticed some bugs in the dashboard as well, which are minor, but I'd still like to address these as well. If Backend Devs cannot be contacted, I guess the only alternative is to make my fork more permanent and start a new Nuget-package with a new name?
Your thoughts?
Hi Jeroen,
I haven't used the Tinifier package itself (yet), but I'm a big fan of the TinyPNG service. I'm not aware of another package that does the same.
I just wanted to reply to say that I think you're taking the right path with an approach to forking the package/project.
You've reached out to the developer(s) and awaiting a response... as for what timeframe to wait, I'm not sure - people have their own lives to deal with too.
But given that http://backend-devs.com/ appears to be a spam-blog now... and like you say their company website https://www.ssa.group/ doesn't mention Umbraco anymore. I wonder if BackendDevs were acquired?
The only other line of comms I would suggest is the Gmail address listed on their GitHub profile: https://github.com/dimonser147?
I think until you hear back from them, then an interim temporary fork is totally acceptable. With a view of if they do come back, that you'd offer to merge your fork back in to their repo/package, (if they want to accept the amends, of course).
In a nutshell, as a old time package dev, I'd give this approach the thumbs up.
I guess the question comes down to whether you want to maintain the code/package moving forwards?
Cheers,
- Lee
Thanks for the feedback, Lee.
I also did find the gmail address. I'll give it a couple of days. In the mean time, I'm communicating with the poster of the Github-issue to see if I can reproduce his issue, which seems to be separate from mine at the moment.
I'd be willing to maintain the package as I find it very valuable. I've read a post saying it clashes with umbraco Forms (DI-wise), which might be a different barrel of fish to tackle. We'll see.
I've released my fork as a separate Nuget package.
The biggest issue was the problem where you can no longer create and publish new content items.
Some minor issues were solved as they came up. I can now successfully use this package in my active projects.
https://www.nuget.org/packages/Our.Umbraco.Tinifier
Any feedback welcome.
is working on a reply...