#10 Continue restructuring when affected components are outside of the hot patching paths.

Open
opened 2 months ago by mattatobin · 0 comments

During GRE I lead the charge to restructure the codebase for a multitude of reasons. Though less respectable ones no longer apply the more legit ones still do.

The following are considered hot paths for patching and will not be moved/broken up any time soon:

  • dom/
  • editor/
  • js/
  • layout/
  • mailnews/
  • xpcom/

The following will stay at topsrcdir regardless:

  • build/
  • config/
  • ipc/
  • other-licenses/
  • python/
  • tools/

The following are hubs where the majority of things live:

  • apps/ - Application Sources
  • components/ - Platform Components
  • libs/ - Libs owned by third parties
  • modules/ - Platform Modules (non-3rd-party libs)
  • system/ - Foundational subsystems and more complex sub-trees that can't be easily split up into their constituent parts and placed elsewhere.
During `GRE` I lead the charge to restructure the codebase for a multitude of reasons. Though less respectable ones no longer apply the more legit ones still do. The following are considered hot paths for patching and will not be moved/broken up any time soon: - `dom/` - `editor/` - `js/` - `layout/` - `mailnews/` - `xpcom/` The following will stay at `topsrcdir` regardless: - `build/` - `config/` - `ipc/` - `other-licenses/` - `python/` - `tools/` The following are hubs where the majority of things live: - `apps/` - Application Sources - `components/` - Platform Components - `libs/` - Libs owned by third parties - `modules/` - Platform Modules (non-3rd-party libs) - `system/` - Foundational subsystems and more complex sub-trees that can't be easily split up into their constituent parts and placed elsewhere.
Sign in to join this conversation.
No Milestone
No assignee
1 Participants
Loading...
Cancel
Save
There is no content yet.