MacDownApp / MacDownApp/macdown
Find a stable way to distribute binary in future
Nobody has claimed this yet.
- Dominant language
- Rich Text Format
- Stars
- 9.8k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
We have temporarily fixed #1106 by manually removing the code signature. There are three potential long-term solutions:
1. Continue removing the signature with `codesign`. Not really sustainable since this is private API.
2. Create a second target, as mentioned in https://github.com/MacDownApp/macdown/issues/1106#issuecomment-562519332.
3. Create a company to hold the Developer Program account. Obstacles are mentioned in https://github.com/MacDownApp/macdown/issues/1106#issuecomment-558859778
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with issue #1106 and its linked discussion, then compare the three proposed distribution paths: removing the signature with codesign, creating a second target, or using a company Developer Program account. The issue does not identify files or tests, and work is complete only when a sustainable distribution approach is selected and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100