BTW, we went "the hard way" and picked the sourcehut todo service as a bug tracker and project management tool for RDE, Ares, Arei and neighboring projects.
It's very bare-bone, but we could implement cross-project milestones via labels, it's already have basic filtering and searching and integrates nicely with email and git.
Will be developing the rest of the functionality as we go. Probably via API or by upstreaming patches to sourcehut.
#sxmo#linuxmobile news:
i fixed the wifi-sec hotspot creation bug, added a 'GSM Disable' entry and a 'Wifi Credentials' to show pw in text and qr-code of the connected wifi or hotspot.
and:
i decided to stop messing with sourcehut, #git send-email and upstream, for fuck sake, its so demotivating! to which email address? why did it not only send the last commit? where is it gone?
i prefer to use my time for features/fixes and to document them, not to messup pipelines of others....
Kennt ihr #Git? Auch wenn ihr kein(e) Programmierer:in seid, dann seid ihr bestimmt schonmal auf #GitHub, #GitLab o.Ä. gestoßen. Auch als Designer:in, Maker:in, Texter:in oder einfach nur zum Projektmanagement spielen Git und die dazugehörigen Plattformen heute eine große Rolle. Wir erklären Git/GitHub/GitLab für Nicht-Programmierer in einem dreistündigen Workshop am Sonntag, den 19. Mai. https://www.welcome-werkstatt.de/veranstaltungen/git-fuer-nicht-programmierer
PSA: Do not submit "omnibus" pull requests to #git repos, especially without talking to the maintainer first. Keeping PRs generally focused to one particular problem or feature makes things far more manageable for reviewing, testing, and reverting/bug-fixing later on. I would always much rather have 10 smaller PRs focused one specific thing each than one massive unsolicited one with a bunch of scope creep.
It's a big mix of small and medium-sized changes:
– A spiffy new welcome window, with recent repos
– You can now open a special example repository for testing things, that resets when you close its window. Go nuts!
– Check the global Git config using the sensibly-formatted table in Settings.
– Never forget about a rebase again: Retcon shows a big obvious badge in the Dock whenever you're paused for editing.
@jrf_nl I have the same technique! I make the messy commits on a branch called sandbox-something and then git merge --squash to either main or a feature branch if it's just one step of many. #git
BitMover's closed-source product, BitKeeper, was used for source control for the #Linux kernel. Larry McVoy, CEO of BitMover, was upset because someone tried to figure out how the BitKeeper worked and he pulled the BitKeeper licenses from Linux developers.
Needing distributed source control, Linus Torvalds created #git in a couple of months.
BitMover is gone and BitKeeper is now open-source, gathering dust, in a git repository.
Opinion: people who staunchly prefer working with Gerrit, and consider anything else inferior, really love working with git-review. And if git-review were not Gerrit specific they would be just as happy with, say, GitLab.
The process that the git-review/Gerrit combo automates/enforces (one commit per change, automatically generated topic branches, change IDs with cross-project uniqueness) could also work just fine by hooking up git-review with the GitLab API.