Hey, some random thoughts: - bugs are sometimes related to the build system (e.g. patches for cmake files), so that might be a more generalized version of host-tools - shell seems rather broad if it's supposed to include both explorer (+dlls) and cmd - services.exe, svchost, and actual service implementations might work in a generalized "services" component - umpnpmgr feels like it should go in a category with setupapi & newdev - translations or localization in general might be useful as a separate component -- seeing how they're usually handled by different people than code changes are - what about drivers that don't fall under usb or networking? Storage/FS might also be an interesting extra category; and perhaps uniata would even make sense separated (seeing its possible default assignee) - Rtl stuff would go under ntcore? What about CRT?
Sorry for the messy list ;) -Thomas On 2012-09-11 01:19, cae...@myopera.com wrote:
Hiya We had a little discussion tonight, regarding changes in component list. It is obvious that current list is illogical, unplanned and requires urgent changes, with Jira update this is the best oportunity. Initial plan was to base upon Timo's Layout rewrite. We had just a small trimming done - below is the result: audio applications directx (or rather 3d graphics which would allow also mesa/gallium in) host-tools networking ntcore sdk shell usb winedlls win32core + rosdlls( | | advapi32 | | kernel32 | | crtdll | | lsasrv | | msvcrt | | msvcrt20 | | msvcrt40 | | samlib | | samsrv | | secur32 | | security | | fmifs | | vdmdbg | | userenv | | uext2 | | ufat | | ufatx | | untfs) The problem is what to do with some ill-fitting to the current scheme, like: | nls | services | eventlog | rpcss | services.exe | svchost | umpnpmgr | spoolsv and more. Do you see need for more components?
_______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
