Closed
Bug 695104
Opened 14 years ago
Closed 13 years ago
move Army of Awesome snippets to Verbatim
Categories
(support.mozilla.org :: Army of Awesome, task, P4)
support.mozilla.org
Army of Awesome
Tracking
(Not tracked)
VERIFIED
FIXED
2012-02-07
People
(Reporter: atopal, Assigned: tgavankar)
Details
(Whiteboard: u=contributor c=AoA s=2012.2 p=2)
Our idea during the design of AoA was that the snippets would change frequently and that Kitsune deployments were rare, making it rather cumbersome to have code pushes for snippet changes. But the times, they are a-changing. So now, we have weekly code pushes, and the snippets don't really change that often.
On the other hand localization is a major pain in the ass with the current system, where people have to localize things in the admin interface, without getting notified about any changes etc.
So, please move the strings to code, and make them localizable in Verbatim.
Comment 1•14 years ago
|
||
(In reply to Kadir Topal [:atopal] from comment #0)
> So, please move the strings to code, and make them localizable in Verbatim.
If possible, let's drop the models so we're not hitting the DB for these at all.
Reporter | ||
Comment 2•14 years ago
|
||
Hey guys, can you give me an estimate on how much time this change would take? Apparently a lot of locales want to get started on AoA and I don't want them to use the old method, which is hard to explain, requires them to use the admin and be marked as staff, so I'm reevaluating the priority of this.
Comment 3•14 years ago
|
||
Right now we have 22 responses in 4 categories. I am assuming that they will all have to be translated again in Verbatim (we will lose the current translations). I don't think there is a way around that. Also, Verbatim won't limit the response length so that the tweets fit in 140 characters. We will have to do with L10n comments saying so.
We have to:
* Create a python module/object/dict/array/something to put the gettext() wrapped responses in.
* Export all the current en-US categories and responses from the db and put them in there.
* Change the view/templates to use this new thing.
* Add unit tests.
* Drop the existing tables, models, and invalidated tests.
I'd say 2-4 days.
Reporter | ||
Comment 4•14 years ago
|
||
Okay, thanks for that estimate, Ricky.
Reporter | ||
Updated•13 years ago
|
Whiteboard: u=contributor c=AoA s=2012.2 p=
Updated•13 years ago
|
Whiteboard: u=contributor c=AoA s=2012.2 p= → u=contributor c=AoA s=2012.2 p=2
Updated•13 years ago
|
Target Milestone: 2011Q4 → 2012Q1
Reporter | ||
Updated•13 years ago
|
Priority: -- → P4
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → tgavankar
Assignee | ||
Comment 5•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: 2012Q1 → 2012-02-07
You need to log in
before you can comment on or make changes to this bug.
Description
•