Date
1 - 8 of 8
[Feedback] Categorizing Videos and presentations of ELC, ELCE, and Japan Technical Jamboree
|
Amit Agarwal <amit.a@...>
Hello All, We are planning to reorganize the wiki pages on eLinux.org by presenting the content of ELC conferences of the last 15 years (ELC, ELCE and Japan Technical Jamboree) based on Categories to which they belong. The working list of categories and sub-categories for the same have been identified and can be accessed at: https://elinux.org/Categorized_Videos_Proposal#Category_Candidates A sample wiki page format has been created for "Build Systems" at: https://elinux.org/Buildsystems Creation of pages for Verticals like Automotive and IoT are also part of the plan. Relevant content will be cross-referenced between Category and Vertical pages. Let us know your comments on the formatting of the wiki page. Any other Regards, Amit Agarwal This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. |
|
|
|
Tim Bird
toggle quoted message
Show quoted text
-----Original Message-----I've been working with Amit and others at PathPartnerTech on this project, and I'm very excited about it. I'll put the current proposed list of categories inline below, if people would rather comment on them inline. What we're looking for is any missing categories or sub-categories that you think would be good to add - but any feedback is appreciated. Please keep future discussions of this project on the celinux-dev mailing list. ?? looks like this sentence was not finished. Amit - the notice below is a bit problematical. If there's any way to remove it, it would be nice. I know it might be out of your hands, but maybe you could add a disclaimer somewhere in the e-mail, to let people know that this message is not confidential? This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, youHere is the proposed category list: * Linux General ** Status Check ** Upstreaming ** Community ** Development process ** LTSI * [[Buildsystems]] ** Yocto ** Buildroot ** Bitbake * Scheduler ** Real Time ** Interrupt latency ** Optimizations * Boot Loaders ** U-Boot * Boot Time ** Initialization ** Boot Time optimization * Device Drivers ** How to write a device driver? ** User Space Device Drivers, Optimizations ** UIO * Size ** Kernel Size – Reduction ** Source code * File Systems * Flash Storage ** NAND Flash ** eMMC * Networking ** Ethernet ** Wi-Fi ** BlueTooth ** X-Ref – IoT relevant topics here (see below) * Security ** SELinux * Upgrades ** OTA updates ** Firmware upgrades * Legal * Multimedia ** Audio ** Video ** Codecs ** GStreamer ** V4L2 (X-Ref with V4L2 kernel sub-system) * Architecture ** ARM ** RISC-V ** PowerPC * Compilers ** GCC, GLIBC ** Linkers, Loaders ** Compiler Optimizations * Device Tree * Kernel sub-systems ** I2C ** SPI ** USB ** Video4linux (V4L2) ** MIPI-DSI ** GPIO ** MTD * Scheduling * Memory Management ** Virtual Memory ** Process Memory ** TLB * Power Management * SMP ** Multi-core ** Concurrency, Locks * Testing ** Automation ** Fuego * Embedded ** MPPWG ** Digital STB ** Linux enabled Light bulbs, * Porting * Tools and Debugging ** GDB ** KGDB ** JTAG ** Tracing -- LTTng * Distributions ** Tomoyo ** Android ** OpenWRT ** OpenHardware ** uCLinux * Virtualization ** QEMU ** Xen * Robotics ** Drones * Miscellaneous ** FOSS * Applications ** SDK ** Qt Development Framework ** Web development, API development ** HTTP ** Maemo Platform – from Nokia ** Eclipse IDE – Open Development Platform * Graphics ** OpenGL ** DigitalFB * Application Protocols ** UPnP ** Protocols like UDP/TCP/IP/HTTP/SOAP/SSDP/XML/GENA/SCPD, SIP, IM, XMPP * Open Source Projects ** Zephyr ** BeagleBone Board ** Dragon Board ** Nine-Dollar Computer CHIP, Good to have different page for following topics with links provided from the Main Page VERTICALS * Automotive ** V2X ** AGL ** Xen * IoT ** IIoT - Embedded Linux in Industrial IoT ** Embedded Protocols – MQTT, 6lowpan ** Stream Processing for IoT ** Home Automation Tools ** X-Ref selected topics/presentations with Networking Category (See above) * Defense Systems I'm going to respond to these in a follow-up e-mail. -- Tim |
|
|
|
Tim Bird
Please find below my feedback on the proposed category list
toggle quoted message
Show quoted text
-----Original Message-----Overall - Is each item below intended to be a standalone page, or is the intent that sub-topics will be sections within a top-level page? Some of the sub-topics (e.g. RealTime) really are big enough to have their own top-level page (or even several pages). Maybe this will depend on the number of talks that end up on a page? Here is the proposed category list:I'm not sure what "Status Check" is - can you give an example talk in this category, or describe it more? ** UpstreamingMaybe add "Legal" here? ** LTSILTSI might go better under "distributions"?, but I'm not sure. * [[Buildsystems]]There are lots more: OpenWRT, Embedded Debian, Debos, etc. How would you categorize ELBE, which builds binary distributions from Debian? Would it go on this page? * SchedulerI'm not sure I see scheduler as a top-level page. I'm not sure how many scheduler talks we've had. Power-management scheduling was a big topic for a while (e.g. big.LITTLE), but maybe going back farther there were lots of talks when the O(1) scheduler was introduced. ** Real TimeRealTime is big enough to deserve it's own top-level page. Likely, Scheduler is not big enough to deserve it's own top-level page. In fact, RealTime might deserve two pages: one for PREEMPT_RT and the other for dual-kernel approaches (e.g. Xenomai) ** Interrupt latencyAlso BareBox * Boot TimeI'm not sure what the "Source code" category is here. * File SystemsDoes "IO scheduling" go here? * Flash StorageSecurity divides into multiple categories. There are mandatory access control systems, like SELinux, AppArmor, Smack, Tomoyo. And then there are different aspects of security like: ** Secure Boot ** Cryptography ** Trusted stores (TPM) ** Hardening * UpgradesOK - maybe this should be a standalone page, but it's kind of in the non-technical category of pages. * MultimediaWe need Intel or x86 as well (and maybe mips) * Compilers** LLVM/Clang ** Linkers, LoadersDon't we already have Scheduling above? * Memory ManagementI would put Fuego underneath a sub-category of ** Test Frameworks *** Fuego, KernelCI, Kselftest, I would add: ** Board farms and infrastructure * EmbeddedNot sure what "MPPWG" is. ** Digital STBAdd ftrace here. * DistributionsI thought Tomoyo was a security system, not a distro, but I could be wrong. ** AndroidI'm not sure * MiscellaneousLegal could also go here? * ApplicationsThis category seems to be "Development Tools", not applications. ** SDKI think I'd stick these under "networking", but some are higher-level protocols. ** UPnPI don't think that "Open Source Projects" is a good category for these sub-topics: ** ZephyrWe should probably have a "non-Linux RTOS" page. I think there have been several different talks over the years for non-Linux OSes (NuttX, Zephyr, Free RTOS, etc.) ** BeagleBone BoardWe should have a "Hardware" category for these board-specific talks. These should be under networking ** Stream Processing for IoTI think I'd put "Home Automation" as it's own topic (not under IoT) maybe also add "Embedded Industrial Systems" as a topic? ** X-Ref selected topics/presentations with Networking Category (See above)I'd put Robotics and Drones under verticals. -- Tim |
|
|
|
Rob Landley
On 8/18/20 3:18 PM, Tim Bird wrote:
FYI we recently re-uploaded the j-core talk that got caught up in The Great-----Original Message----- Purge: https://www.youtube.com/watch?v=GHORpXNRJiE I don't know if anybody downloaded my 2015 toybox talk, I can't find that one locally... Rob |
|
|
|
Tim Bird
toggle quoted message
Show quoted text
-----Original Message-----Thanks for the link. I added your link to the page: https://elinux.org/ELC_2016_Presentations We were able to get most of the 2016 videos restored, but alas not the 2015 ones. BTW - do you have a copy of your presentation from that year? The link on the presentations page is missing a file. -- Tim |
|
|
|
Rob Landley
On 8/19/20 5:36 PM, Bird, Tim wrote:
...I don't know if anybody downloaded my 2015 toybox talk, I can't find that one BTW - do you have a copy of your presentation from that year? The link on theI usually youtube-dl an archive copy, but haven't got it on any current machine and haven't hunted through the old disk pile. Rob |
|
|
|
scott preece
MPPWG was the Mobile Phone Profile Working Group, which I led in an ill-fated effort to define an open API for phones built on Linux, back before Android swept the field. We did have talks at a couple ELCs.
toggle quoted message
Show quoted text
-- Scott On Tuesday, August 18, 2020, 4:47 PM, Tim Bird <tim.bird@...> wrote:
|
|
|
|
Tim Bird
toggle quoted message
Show quoted text
-----Original Message----- Hey Scott! It's good to hear from you. I hope you are doing well! It's been a few years since we used the MPPWG acronym, but I should have remembered it. -- Tim On Tuesday, August 18, 2020, 4:47 PM, Tim Bird <tim.bird@...> wrote: |
|
|