#hprep — Public Fediverse posts

The solution is to record an #HPREp on the topic of sonar.properties (and -D parameters, same thing) and its mapping to the UI project settings and to docs.sonarqube.org/latest/proj… and then send anyone who asks to that episode and its shownotes.

@mastodon I learned git by using it for 15 years and reading man pages, so I don't have personal recommendations. I am however conducting git workshops in the office and once I've found a form that doesn't scare people I may create a series of #HPREp from that. If and when I do I promise to come back here and post links.

Oops misspelled ‌‌#HPREp

Matrix, libera.chat, nickserv

How to join #hpr:matrix.org when you're on XMPP

‌‌#HPREp

Stage, Lock and Milestone for declarative Jenkins pipelines ‌‌#HPREp

Python 3.10 came out last week.

The most interesting feature included is PEP 622 -- Structural Pattern Matching , similar to Scheme's (match), but a bit less powerful and spelled in Python. That's worth an #HPREp.

The most interesting feature *not* included was PEP 563 -- Postponed Evaluation of Annotations, which was slated for inclusion but was pushed to 3.11 to sort out some details regarding libraries like Pydantic that rely on reflection on declared types.

#python #python310 #python3100

Python 3.10 came out last week.

The most interesting feature included is PEP 622 -- Structural Pattern Matching , similar to Scheme's (match), but a bit less powerful and spelled in Python. That's worth an #HPREp.

The most interesting feature *not* included was PEP 563 -- Postponed Evaluation of Annotations, which was slated for inclusion but was pushed to 3.11 to sort out some details regarding libraries like Pydantic that rely on reflection on declared types.

#python #python310 #python3100

The handmade.network/manifesto would make sense for the #HPREp series of software-related manifestos.

Re: libranet.de/display/0b6b25a8-1…

libranet.de/display/0b6b25a8-2…

The material for the multiple #HPREp (this time spelled correctly) on the CC-by-SA licenses 3.0 and 4.0.

@ken_fallon @hpr @perloid It might be!

Higher version and better adapted to non-US jurisdictions sounds better without really knowing what the difference is.

We need an #HPREp that could answer this question.

@Moon Thanks, that means I should make an #HPREp to explain the other words.

#HPREp #FreenodeTakeover

#HPREp Audacity telemetry (rejected) and CLA (not yet rejected)

Why yes, I am indeed using #pyenv and #anaconda together to manage my #nodejs interpreter for different projects!

#HPREp

So #matrix isn't set up with #libera yet, but a kind soul on IRC reminded me that #biboumi exists, and tipped me off that disroot has one running.

I'll set that up instead of waiting for a matrix.org bridge, and I'll do an #HPREp on the steps required with Conversations and a SASL login to libera. It's going to involve using a second XMPP client that supports XEP-0050.

#HPRep fighting system settings in macOS 10.14

Reading and comparing and contrasting this with the cooptech manifesto is an #HPREp given.

@efraim It's also how I described Guix in a talk I've given to small circles and in an HPR episode I never finished back in 2015. I guess I just admitted I owe HPR that show! #HPREp

@mansr Compared to the Blue Oak Model License and copyleft-next it looks a bit long, but at least it's half the length of the GPLv3. 😁

It does have some innovative and bits in there, of urgent importance. I should study it properly, drag out some lawyers' comments from the internet and make an #HPREp on it.

@bhaugen That's a lot of words, sorry. Am I making sense?

I should think this through and create an #HPREp on writing composable code.

These two comments were adapted into part of my #HPREp reading the manifesto. Once processed it will be available at hackerpublicradio.org/eps.php?… .

Until then, show notes with my commentary are available at codeberg.org/clacke/hpr/src/br… (old file name, I mention the new label in the text and use it in the episode title) -- the episode is me 99% just plain reading those notes and the manifesto.

@alcinnz @josias @be

#CooperativeTechnology #CommunalSoftware

These two comments were adapted into part of my #HPREp reading the manifesto. Once processed it will be available at hackerpublicradio.org/eps.php?… .

Until then, show notes with my commentary are available at codeberg.org/clacke/hpr/src/br… (old file name, I mention the new label in the text and use it in the episode title) -- the episode is me 99% just plain reading those notes and the manifesto.

@alcinnz @josias @be

#CooperativeTechnology #CommunalSoftware

Reading this Communal Software manifesto out loud will be an easy yet valuable #HPREp

#AdaLovelace #BarbaraLiskov #FrancesAllen #GraceHopper #MargaretHamilton

And the Nitter / birdsite thread also mentions:

#LynnConway (also a pioneer transwoman)

#RadhiaCousot #ShafiGoldwasser #NancyLynch #WangXiaoyun #PamelaZave #NancyLeveson #RuzenaBajcsy

Other than in terms of name recognition and symbolic inspiration, all of them influenced computer science more than Ada Lovelace.

Each of them deserves her own #HPREp !

#AdaLovelace #BarbaraLiskov #FrancesAllen #GraceHopper #MargaretHamilton

And the Nitter / birdsite thread also mentions:

#LynnConway (also a pioneer transwoman)

#RadhiaCousot #ShafiGoldwasser #NancyLynch #WangXiaoyun #PamelaZave #NancyLeveson #RuzenaBajcsy

Other than in terms of name recognition and symbolic inspiration, all of them influenced computer science more than Ada Lovelace.

Each of them deserves her own #HPREp !

#AdaLovelace #BarbaraLiskov #FrancesAllen #GraceHopper #MargaretHamilton

And the Nitter / birdsite thread also mentions:

#LynnConway (also a pioneer transwoman)

#RadhiaCousot #ShafiGoldwasser #NancyLynch #WangXiaoyun #PamelaZave #NancyLeveson #RuzenaBajcsy

Other than in terms of name recognition and symbolic inspiration, all of them influenced computer science more than Ada Lovelace.

Each of them deserves her own #HPREp !

#AdaLovelace #BarbaraLiskov #FrancesAllen #GraceHopper #MargaretHamilton

And the Nitter / birdsite thread also mentions:

#LynnConway (also a pioneer transwoman)

#RadhiaCousot #ShafiGoldwasser #NancyLynch #WangXiaoyun #PamelaZave #NancyLeveson #RuzenaBajcsy

Other than in terms of name recognition and symbolic inspiration, all of them influenced computer science more than Ada Lovelace.

Each of them deserves her own #HPREp !

The bootstrappability problem #HPREp

At least gnat builds with an old ADA: libranet.de/display/0b6b25a8-4…

This is now an #HPREp and will be available at hackerpublicradio.org/eps.php?… when it has been processed!

The very first commit in github.com/highlightjs/highlig… is considered invalid by GitHub Enterprise, so now I've been forced to discover the new --rebase-merges to be able to reproduce the whole commit tree minus that root commit.

git-scm.com/docs/git-rebase#Do… is AMAZING.

The rebase-todo language now has labels, resets and merges, and git rebase --rebase-merges generates a todo that uses these to faithfully reproduce the git commit tree!

Caveats apply:

* It doesn't deal with merge conflicts, so you'll have to resolve those again. Luckily it puts the original merge in REBASE_HEAD, so if you didn't actually change any code you can just git rm -rf . && git checkout REBASE_HEAD -- . && git rebase --continue every time it stops to make you resolve a conflict.
* Use git 2.25.0 or higher. 2.23.0, which is the latest in anaconda, has a bug where the todo generator generates labels that aren't valid refs, so you'll have to edit the todo until it works.

#HPRep

@[email protected]

If you don't have time for that nonsense, you will add environment markers (conditionals like dataclasses; python_version < "3.7" or colorama>=0.4.1 ;platform_system=="Windows" to your requirements.in, and then you will make sure to run pip-compile on the lowest common denominator that includes all of your conditional packages.

If you have no lowest common denominator, because some transdep is only for Windows and some other transdep is only for Linux, tough luck. You'll have to either do the "one requirements.txt for each combo", or do something even more exotic like running pip-compile on several combos and merging the results into your Ultimate requirements.txt.

No guarantee that the Ultimate requirements.txt exists. In reality it probably does by pure luck[0], but I could easily invent a toy example corner case where different combos have conflicting requirements.

[0]‌ Pure luck and reasonable effort takes you surprisingly far. It's what has allowed the pre-2020 pip resolver to survive as long as it has. Packages generally behave nice enough.

#HPREp

#HPREp talk to @jgaskins about the intersection of ActivityPub, Linked Data and graph databases

#HPREp the saga of adding this one generated file as a data file in a python package as part of the build process

#HPRep #PEP441 zipapp pyzzer pex shiv

#HPREp the python packaging tool saga

I've started looking at doing an #HPREp series on the various bash releases and which features arrived when, and my idea is to start with bash 5 and work my way backwards. Once we're back at the first release we still have a tarball for, back in the early 90s, that can be a summary episode about the differences between 1.x and 5.x.

I looked at bash 4.4 for the coproc episode, and now I happened to still have a page open with the release notes, and I saw that 4.4 was the released that fixed #shellshock. Nobody actually did an episode on Shellshock from what I can tell, so maybe that's what I'm doing first.

Shellshock was mentioned by name 1:10:50 in on New Year's show 2015 part 2: hackerpublicradio.org/eps.php?…, but that's it.