08:41 <sewn> Guest19: leaderless and divided

08:42 <sewn> everyone's doing their own thing, and one of the maintainers is making decisions without communication

09:57 <riteo> thinking about it, should we elect a new BDFL?

09:57 <riteo> if that even makes sense at this point

09:58 <riteo> Maybe that's the nice part of kiss, the fact that it so chaotic and freeform

09:59 <sad_plan> thats some of the idea behind kiss. bus factor of 0

10:00 <sad_plan> so theres really no need for some kind of bdfl or leadership of any sort. people can simply keep their own system up to date

10:00 <sad_plan> however, having some kind of centralized hub or w/e, can ofc be benefitial

10:01 <riteo> well there's also the core framework

10:02 <riteo> and it's not like it's perfect either, so, thinking about it, a BDFL would probably be concerned only about the package manager and init/devman wrappers at this point

10:03 <riteo> I really wish there were more "kiss-compatible" forks, but at a certain point they become different things

10:04 <riteo> I'll definitely make my package manager kiss compatible, so there's that. Just gotta wait for this hell of an exam to end

10:08 <sad_plan> the bdfl has usually been concerning himself with all things kiss. packages, package-manager, init and so on. keeping the whole ordeal up to date and running optimally more or less. some people just want there to be someone making the decisions.

10:09 <sad_plan> theres lots of kiss compatible forks, and obviously theyre their own thing, thats the whole point

10:10 <riteo> mh right

10:10 <riteo> yeah at this point a BDFL might not even make much sense as you pointed out

10:12 <riteo> as long as very few people, if not only one, maintains the core stuff then who cares :P

10:12 <sad_plan> I dont really think it matters at this point. theres couple people keeping the centralized repo up to date, aswell as improving upon the package manager. which I suppose is for the most part what people wants

10:12 <riteo> btw, thanks to everyone still maintaining the thing and updating their shitton of packages, while I occasionally push updates for kakoune and fuse and that's it

10:13 <sad_plan> exacly. some people just dont wanna do the work, so having atleast one person doing it, theyre fine with that

10:14 <riteo> That's nice actually, that the project is so simple that does not need a BDFL

10:14 <sad_plan> yep. everyone can keep their own system up to date. thats the whole design idea :p which is amazing if you ask me

10:15 <riteo> indeed :D

10:15 <sad_plan> :D

16:12 <ehawkvu> riteo: if you're interested in "kiss-compatible", you can checkout https://github.com/echawk/kiss-spec ~ it's my WIP writeup of what makes a system operable with kiss

16:13 <ehawkvu> In that same repo, I'm working on a package "kiss-system", which if it is able to be built and installed, then the system can call itself kiss

16:14 <ehawkvu> but my main interest in the next couple of months is going to be getting kiss and friends to play nice on freebsd

18:49 <riteo> ehawkvu: nice, I'll definitely use this stuff as a benchmark for the kiss builder :D