Can we create consistency between the naming convention of the (sub)projects related to Visual Editor and Wikitext editor to make them more easily findable and have better parity?
Description
Event Timeline
What are the "subprojects related to Wikitext editor"?
Or basically: Which existing projects are we discussing here?
I've added what I know and can find to the task, but others may be present and hard to find, due to the issue in this task (Catch-22)
We have three distinct editors and three corresponding projects.
- The VisualEditor is VisualEditor, this is an umbrella project that includes all tasks from all of the subprojects like VisualEditor-EditingTools. You should never file tasks in subprojects only or they may get lost (until we have project inheritance or whatever in Phabricator).
- The WikiEditor extension, which is WikiEditor (2010). This is what most people know as the wikitext editor and implements all of the fancy buttons around the wikitext editing area.
- The built-in MediaWiki editor, which you never see unless you're the kind of person who still uses MonoBook and hates new things. It doesn't have a dedicated project, but any issues can be filed under MediaWiki-Page-editing (this project also covers things like editing pages suddenly being broken or something).
I'm not sure what this task is about.
thanks for clarifying @matamarex, you kind of hit on what I'm saying. Is there any way we can make the phab project names for these more clearly show those relationships you just outlined?
No, not really. Core's wikitext editing must stay under MediaWiki- and VisualEditor (and WikiEditor) must be separate.
There's also:
- Mobile Web
- the wikitext editor in Mobile Web, which is dealt with inside MobileFrontend-General-or-Unknown (no specific project for editor issues)
- VisualEditor issues specific to the Mobile Web integration, which are dealt with in VisualEditor-MediaWiki-Mobile
- Apps
- the wikitext editor in the iOS mobile app, which is dealt with in Wikipedia-iOS-App-Backlog (but not really, because they haven't migrated to Phabricator yet)
- the wikitext editor in the Android mobile app, which is dealt with in Wikipedia-Android-App-Backlog (but not really, again)
- Flow
- the wikitext editor in Flow, which is dealt with inside StructuredDiscussions
- the VisualEditor issues specific to the Flow integration, which are, well, not currently filed anywhere, but I guess would go in VisualEditor and StructuredDiscussions together.
- the wikitext editor in LiquidThreads, which is dealt with inside MediaWiki-extensions-LiquidThreads
- the code editor, which is dealt with in CodeEditor
… and probably some others I'm forgetting.
the wikitext editor in Flow, which is dealt with inside MediaWiki-extensions-Flow
the VisualEditor issues specific to the Flow integration, which are, well, not currently filed anywhere, but I guess would go in VisualEditor and MediaWiki-extensions-Flow together.
The VE integration is not actively being worked on, though we still want to use it later, of course.
We basically use the standard scheme (MediaWiki-extensions-ExtensionName). We also have a team board ( Collaboration-Team-Triage ), but if you file it in the extension component you don't need to worry about the team board (we may add that project later, though).
Are there any action items for Collaboration-Team-Triage ? If not, we'll remove our projects from this task.
Umbrella projects having a distinct color seems sane. Upstream seems to do this I think.