<sewn>
logical thing kiss-community should do is fork this tbh
<vova_>
yeah
<vova_>
I thought you knew this repo lol
<sewn>
I think testuser doesn't either, why else did he start kiss-ng
<vova_>
damn
<vova_>
I think we should also follow Dylan repo's name
<vova_>
like no more `kiss b` etc but `k b`
<sewn>
kiss
<sewn>
hm
<sewn>
hmmm
<sewn>
maybe check if there's a utility named k first
<sewn>
and also, maybe name it uhh
<sewn>
smooch
<sewn>
nvm too long
<vova_>
dyk
<vova_>
Dylan Araps Kiss
<illiliti>
vova_: dunno, 200-300$ maybe? this is not final of course and we can negotiate that
<vova_>
just tell me honestly
<sewn>
500$
<vova_>
what do you think about github.com/dylanaraps/k ? illiliti
<illiliti>
it's incomplete, what else to say
<vova_>
yeah but I mean it's a good start no ?
<illiliti>
i'd prefer to start from scratch
<vova_>
how long do you think it will take ?
<illiliti>
hmm. hard question
<illiliti>
if i say half of a year, would that be reasonable?
<illiliti>
perhaps in reality it would take less if i stop doing some other things...
<illiliti>
looking at my previous attempt(king) it took +- half of a year to finish core functionality
<illiliti>
but i was mostly bikeshedding some things i don't like such as how internals are designed
<vova_>
I see, I honestly have no idea how complexe is kiss
<vova_>
BTW illiliti I saw you on a issue in wlroots for netbsd wscons support, you are still using kiss or you switched to BSD ?
<illiliti>
i use kiss. i don't have enough capacity to finish that work unfortunately
<illiliti>
kiss is not so complex, really
<sewn>
vova_: yambar just died
<sewn>
its dropped in community
<sewn>
what are you gonna do!!!?!!?!?
<vova_>
fuck
<vova_>
I love yambar
<vova_>
I even did a module for pipewire + dwl for it
<illiliti>
vova_: i gotta go. feel free to pm me if you interested in further discussing this matter
<phoebos>
vova_: add it back, revert the commit
rfaa has joined #kisslinux
<ehawkvu>
phoebos: regarding the wiki/ idea ~ each repo of packages (kiss-xorg, community, gkiss, etc) would have what appears to be another repository (wiki/)
<ehawkvu>
In that directory, the maintainers (plus anyone who would want to contribute) would be able to write (ideally markdown, but we can all figure that out together) wikipages describing how to do miscellaneous things
<ehawkvu>
that way, documentation is both local, and the entire history is saved as well
<ehawkvu>
so then, on kisscommunity.org, we could have a "wiki from the community" where, like w/ kiss-find, we find all of the wikis and aggregate them into one place
<sewn>
I don't really think kisscommunity is that active to do all of that
sad_plan has joined #kisslinux
<sad_plan>
hi
<sad_plan>
phoebos: pushed fixes to the wiki. only thing I was sortof unsure of was how youd want the prefixes
<sad_plan>
i.e. if something is in kernel/patches, would you like whole dir to be there? or just wiki wiki/kernel, oor..? I used wiki/kernel for now anyway
<sad_plan>
have a peak at the commit msgs and lmk
traidare has quit [Ping timeout: 264 seconds]
ehawkvu has quit [Remote host closed the connection]