From: 0x5c <0x5c@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: fritzing
Date: Mon, 08 Apr 2024 10:43:40 +0200 [thread overview]
Message-ID: <20240408084340.BD7D22659A@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49544@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
New comment by 0x5c on void-packages repository
https://github.com/void-linux/void-packages/issues/49544#issuecomment-2042192540
Comment:
From other threads online, upstream indicates not wanting to offer Fritzing "for free" anymore[^1][^2][^3], with many justifications like "development sustainability"[^1][^2][^3], and also resisted for quite some time the idea of even syncing the code on Github for each releases[^1][^2][^3]. They also express wanting not to publicly develop on Github anymore for reason of "excessive charges" for "CI"[^2][^3] and "transactions"[^3], and instead have a private repository somewhere else. The "charges" thing is very strange considering public Github repos are the only ones getting free CI, and more than enough of it to power even massive high-frequency repos like [this one](https://github.com/void-linux/void-packages).
As to the "git sync", the code published on git is untagged, and seemingly would not compile a binary of the current version (latest version information it contains is a beta `*.*.*b` number).
[^1]: https://github.com/fritzing/fritzing-app/issues/4070
[^2]: https://forum.fritzing.org/t/can-t-find-source-code/19723
[^3]: https://forum.fritzing.org/t/just-thinking-fritzing-is-actually-not-opensource-anymore/22861
next prev parent reply other threads:[~2024-04-08 8:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 7:46 [ISSUE] " U2C9727A4
2024-03-30 9:29 ` MIvanchev
2024-03-30 9:34 ` classabbyamp
2024-03-30 9:41 ` MIvanchev
2024-04-08 8:43 ` 0x5c [this message]
2024-06-14 7:15 ` [ISSUE] [CLOSED] " classabbyamp
2024-06-14 7:15 ` classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240408084340.BD7D22659A@inbox.vuxu.org \
--to=0x5c@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).