MacDownApp/macdown

Find a stable way to distribute binary in future

Open

#1127 opened on Dec 18, 2019

View on GitHub
 (9 comments) (0 reactions) (0 assignees)Objective-C (7,686 stars) (930 forks)batch import
help wantedtodo

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

Tech stack
objective c
Domain
desktopreleasetooling
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
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.
mostly clear
Prerequisites
macOS developmentcode signingXcode build system
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
15
Research direction
Investigate the three proposed solutions: using private codesign API, creating a second target, or forming a company for Apple Developer Program. Analyze feasibility and maintenance. Refer to comments in issue #1106 for context and obstacles.