It might be useful to create a “Text” component that people could use for reporting typos, suggesting text changes, etc. This would also automatically be a good starter component for people who need something super easy to learn how to submit a patch.
Recent comments
newtonsongbird on Suggestions Kim Parsell on Core Contributor Handbook Lance Willett on We’re getting very close… Muhammad Abdi on Core Contributor Handbook Maor Chasen on We’re getting very close…
Marko Heijnen 2:21 pm on November 16, 2012 Permalink
I would even go further. something as “needs-text” and “has-text”. I talked about this with multiple people that every new string should be checked.
Jane Wells 2:26 pm on November 16, 2012 Permalink
needs-text and has-text are tags to describe the ticket (also would be useful), but Text as a component would mean that it ONLY involves a text change, not anything functional (that might also need text to be complete).
Kailey Lampert (trepmal) 5:50 pm on November 16, 2012 Permalink
+1 My first patch was a typo fix. It’s a great way for potential-committers to drop the ‘potential’ part.
Kailey Lampert (trepmal) 6:18 pm on November 16, 2012 Permalink
err… contributors
scribu 6:29 pm on November 16, 2012 Permalink
+1. Currently, they all get lumped under the i18n component.
Andrew Nacin 7:15 pm on November 16, 2012 Permalink
Just to brainstorm, what about something like “Text Changes”, or “Typos”, or something? For some reason, “Text” seems too abstract to immediately realize what it is referring to.
Jane Wells 7:18 pm on November 16, 2012 Permalink
Text Changes sounds good. Or Text/Strings. Typos too limiting.