Post by @drew@social.freebitcoin.gay

@drew

@davidrevoy :D

@davidrevoy

Thank you for your reply!
Hope that things sort itself out for you so you can find time for things you enjoy!

@elly @drew @selea Good to see, and yes, that's to be expected for Wayland, as many things for drawing-tablets were delegated to libinput and the compositor and the D.E itself; while all was more centralized on X11.

I'll check how X11 NetBSD works, very curious to get a machine with that. I'm working on it (on week-end, so slowly).

@drew there you go boss. I look forward to using this on CI btw, NetBSD or AlpineBSD

@drj it's nice :) a bit too derivative, though... but if you vectorize it I'll ship it for now!

@drew vectors (Inkscape) at https://git.sr.ht/~drj/logo-absd/tree

@drj that's great!

@drj license? CC-0 okay?

@drj oh haha CC-BY is also fine, I didn't check the readme

@drew Oh, it's CC0 now. :) If you use it, you can comp me for a month's on sr.ht ;)

@drj sure thing :)

@drew

@martijnbraam what's the symbolism here lmao

@drew wait what parts of the alpine userspace?

@megatog615 apk-tools and abuild and busybox are the base

@drew

Alright, here we go, some loose connections:

* Butterfly - Parnassius for Alpine reference
* Dark-ish-Steal-Blue - For the Alpine Linux colour reference
* Orange - For the NetBSD reference
* Colourising the words to represent the parts

@ahto oh very nice! Can you provide vectors and a license?

@drew hey it's me, we worked together before!

@prahou hi Tomáš :)

@drew what's your favorite animal, because it'll be panda otherwise

@prahou ferrets for sure

@drew brb

@prahou o7

@drew i put over it a japanese jesus watermark, that way nobody can steal this amazing idea for their project with the same name!

Think of the marketing possibilities. The ferret can wear different hats depending on the season of the year.

@angel @drew good luck removing the watermark, it can't be done.

@Mae @drew @angel you also get automatically blessed by JJ every time you look at a picture!

@angel @Mae @drew Stay prayed up, fam!

@prahou @angel @drew
I only want the watermark. I guess with jj it's a walk-on-watermark.

@FritzAdalis @angel @drew we need to make a JapaneseJesusBSD

@prahou it's beautiful 🤩

@drew here you go, cc0, etc

@prahou @drew This is great, and i can pretend it's a Marmot (which is an actual Alpine mammal).

@drj @prahou @drew I mean, as long as it’s some sort of mustelid I can get behind it.

@prahou @drew it's not gonna help you if their project is Japanese Jesus themed

@prahou@merveilles.town @drew@social.freebitcoin.gay

LOVE
IT

DOOK DOOK DOOK DOOK DOOK DOOK DOOK DOOK

@paul @drew omg u guys

@angel @paul @drew

now you draw one!

@prahou@merveilles.town @angel@triptico.com @drew@social.freebitcoin.gay I can't do a logo, but please accept a drawing of two ferrets in an alpine lodge/shack snuggled all cosy and stuff.

@paul @prahou@merveilles.town @angel@triptico.com @drew@social.freebitcoin.gay original picture for reference - and ferrets.
(above: Duffle, below: Alfie)

@paul
very much a "me and who" situation
@prahou @angel @drew

@prahou

Chonky cat with hangover

@drew

@drew@social.freebitcoin.gay I may just be a lowly system admin, but I would happily cast my vote for a ferret logo

(the butterfly one I've seen is also good by the way)

@thedaemon goat

@drew Relatedly, I'm also looking for an artist to draw a logo for #s6 !

s6 is a process supervision suite that has grown into a complete init system (incidentally the one #AlpineBSD is using).

Ideally the logo would represent a young striped wild boar, as cute as you can make it.
(The main author of a well-known init system once called s6 a "dependency hog".)

@ell1e @drew They have not done so since the policy was clarified in 2024.

Anyway, it needs clarifying again, since there's some third-party code we're not necessarily ready to remove, upstream has accepted AI contributions, it needs updates, and the decision between shipping slop and shipping vulnerable code to users is a huge catch-22.

@netbsd @drew well, you could always write a manual fix for an AI reported vulnerability. so I don't think shipping slop is required for that either.

@ell1e @drew we unfortunately don't have the resources to fork and take over maintenance of large software projects like Postfix and BIND, but thankfully they are entirely optional.

their choices also advance the argument for having a smaller base system by default.

@netbsd @drew ah, I see, yes for third-party projects I understand.

But in that case, it would be nice to have some sort of table to understand what is slop free. I think more transparency would make people way more at ease if the guideline needs to be occasionally broken.

(My apologies if this already exist, perhaps it should be linked then on this page: https://www.netbsd.org/developers/commit-guidelines.html after the paragraph talking about LLMs.)

@ell1e @drew yeah, exactly, that's what i meant by "anyway, it needs clarifying again, since there's some third-party code"

@netbsd @drew after researching NetBSD some more, I think another pain point here might be moving over drivers from FreeBSD, like e.g. here: https://blog.netbsd.org/tnf/entry/wifi_renewal_restarted Since FreeBSD has sadly gone down the slop route, it seems like...

(Basically would be interesting to know how this will be handled in the future!)

@ell1e @drew All of the BSDs contain a high amount of code in common, especially in the driver area. Notice this post is from 2020. While work continues on the Wi-Fi branch, all code committed there in the last few years is from us.

@netbsd @ell1e i was just wondering if my NetBSD on my tiny Netbook need postfix. Or a mailserver. or mail. Just pipe through « mail » if you must. Like good old days.

@netbsd

If Postfix and BIND are doing the thing, there may soon not be much of a Net for NetBSD to connect to… 😬

@ell1e @drew

@argv_minus_one @netbsd @drew replacing a DNS server is much less work than a kernel.

regarding email servers, it seems exim bans AI? but haven't really looked into that one yet and how portable it is

@ell1e @argv_minus_one @drew We can't have new GPL in base.

dma is promising and simple enough that we likely wouldn't have problems maintaining it. https://leaf.dragonflybsd.org/cgi/web-man?command=dma&section=ANY

@netbsd

Hmm? Wouldn't an email server fall under the GPL's “mere aggregation” clause?

@ell1e @drew

@drew throwing my hat in the ring, maybe this is a bit too close to both alpine and netbsd logos?

@drew & with a bit of orange

@drew Would it be possible for me to use absd-ports alongside pkgsrc? Cause I have a NetBSD install already and would like to use it more

@Zayac no, they're mutually exclusive

@drew this may be kind of dump or nitpicking: can the logo always use lowercase for the alpine part? As in #alpineBSD

Why would be ever considered?
Seeing the current proposals *my* head kind of reads it as AI-pine, as in Artificial-Intelligence-pine, and being a non-AI project sometimes it seems like the other way around.

Other option would be change the name to a derivative of Alpine but I do understand is besides the point and reduce credit for #alpinelinux.

@esparta alpineBSD is fine with me

@drew I put this together quickly in inkscape, feel free to use it if you want

@drew

Depending on how iterative you like your logotypes and isotypes here are some quick scribbles, which is just rearranging the existing visual identity of the other projects into one.

This is the type of thing that would less require someone to doodle designs and more having some broad goal of what the identity/message could be like.

@drew

Cannot have a logo without a joke answer either. Being obsessed with bunnies this would be our choice (closeness to the Hare language and all, too).