05:11 <tito-me-doe> Hi

05:14 <tito-me-doe> This channel feels very unalive… where do active members usually chat?

05:17 <tito-me-doe> Time zone issue? Seasonal?

05:20 <tito-me-doe> Well, if anyone sees this, I understand trepidation and even skepticism against the idea

05:22 <tito-me-doe> I really do see a path forward where the functions of enabling hardware is moved out into a larger community project with many contributors, maintainers, and stakeholders, and the development of unique frontend experiences continues and hopefully flourishes and even more hopefully expands in bespoke fork projects.

05:40 <tito-me-doe> And yeah, I do think that BootELEC should include BSP contributions (only for mainline unsupported devices!) but I also strongly feel that compiling LibreELEC against BSP would be at the users’ own build/peril and that at no point would you be required to release artifacts for every device supported by BootELEC. Further, LibreELEC would *only* take ownership of/responsibility for the build system and any devices your

05:40 <tito-me-doe> organization wishes to support—all other devices are up to other maintainers to either push code for it or not.

05:40 <tito-me-doe> The core goal is to share efforts

05:41 <tito-me-doe> And enable any firmware to be technically built for almost any device (with some kernel support caveats, obviously)

05:45 <tito-me-doe> Stretch goal is booting BootELEC without a userLand built on top would boot to a script that lists attached hardware, drivers used, recent syslogs, etc information that would be useful to day-one developers trying to bring up support for a new device.

05:49 <tito-me-doe> I would say bringing up a console with basic diagnostic software and basic utilities is good, but not all devices natively support a keyboard, so I think a script that prints information is maybe more useful (if alt+fx with a keyboard attached takes you to a console, then this is a good solution)

06:55 <oblikoamorale> there is no shortage of bright ideas, but a shortage of people willing to do the actual work. why don't show the initiative and start working on a prototype?

10:06 <lebot> <chewitt> So far there’s nobody on the team leaping to share their opinion in public so I’ll end up chatting to a few folk in private and then posting something.

10:08 <lebot> <chewitt> I’m busy with Kodi DevCon until early next week though, so don’t hold breath.

23:46 <tito-me-doe> That’s too bad. I really was hoping to at minimum have some form of dialect, answer questions, reframe my thoughts and ideas, etc

23:51 <tito-me-doe> And yeah, sure, I’m a developer, I don’t mind putting in work, but there are two issues. 1. I have my own opinions. It might be very easy for me to make choices that no one like—for instance, maybe I would make every platform in BootELEC its own branch and then no one wants to adopt more contribute to it and the project does 2. I’m a nobody. The only way this idea would be able to have the level of traction and

23:51 <tito-me-doe> contribution necessary for the project viable is if it came from a prominent community like LibreELEC, where so many other projects have derived