Core Platform Team/Initiative/Reduce Extension Interface Surface Area/Open Questions

< Reduce Extension Interface Surface Area

  • How should an extension expose a web API?
  • How do we annotate source code so that code is public or private to extensions?
  • Should Wikimedia and third party extensions have the same interface into core?
  • How close can we come to killing all global state, replacing it by using service locators?
  • Should there be a restricted service locator that extensions are forced to use?
  • Can the internal tag be used to mark certain classes as internal without making it difficult to work within core