aonez/Keka

Create an "open standard" to preserve HFS+ compression in archives

Open

#153 opened on Mar 19, 2018

View on GitHub
 (13 comments) (0 reactions) (0 assignees)PHP (4,097 stars) (229 forks)batch import
blessedhelp wanted

Description

I started a discussion with ImageOptim's developer about HFS+ compression... he would prefer if he didn't have to use .dmg for his app to preserve HFS+ compression...

So... I think that maybe we could try to see if we could get developers of popular archiving/unarchiving utilities for Mac to agree on something like an "open standard" to preserve HFS+ compression, at least among popular archiving/unarchiving utilities for Mac with a GUI.

https://github.com/ImageOptim/ImageOptim/issues/253

Contributor guide

Tech stack
None
Domain
documentationtooling
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
HFS+ compressionmacOS archive formatscross project collaboration
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
Review the linked discussion in ImageOptim issue #253 to understand the context of HFS+ compression preservation. Investigate existing standards for archive formats on macOS, such as UDIF and DMG. Reach out to maintainers of popular macOS archivers like Keka, ImageOptim, and The Unarchiver to gauge interest and gather requirements.