Comments on: The Evolution of SUMO http://coffeeonthekeyboard.com/the-evolution-of-sumo-339/ by James Socol Thu, 22 Sep 2011 20:50:05 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Testing with Legacy Data in Django | Coffee on the Keyboard http://coffeeonthekeyboard.com/the-evolution-of-sumo-339/comment-page-1/#comment-7851 Testing with Legacy Data in Django | Coffee on the Keyboard Wed, 07 Apr 2010 23:25:49 +0000 http://coffeeonthekeyboard.com/?p=339#comment-7851 [...] we incrementally move SUMO over to Django, we often run into problems with legacy data—I’d say all of our problems so [...] [...] we incrementally move SUMO over to Django, we often run into problems with legacy data—I’d say all of our problems so [...]

]]> By: Code-sharing Update | Coffee on the Keyboard http://coffeeonthekeyboard.com/the-evolution-of-sumo-339/comment-page-1/#comment-6928 Code-sharing Update | Coffee on the Keyboard Mon, 08 Mar 2010 17:02:21 +0000 http://coffeeonthekeyboard.com/?p=339#comment-6928 [...] we decided to move SUMO to a new platform, one of the reasons we chose Django was code sharing and reuse—specifically that SUMO and AMO [...] [...] we decided to move SUMO to a new platform, one of the reasons we chose Django was code sharing and reuse—specifically that SUMO and AMO [...]

]]> By: Axel Hecht http://coffeeonthekeyboard.com/the-evolution-of-sumo-339/comment-page-1/#comment-6719 Axel Hecht Sat, 27 Feb 2010 16:14:38 +0000 http://coffeeonthekeyboard.com/?p=339#comment-6719 Well, the add-on descriptions are far from being as lively documents as a support document, I guess. Well, the add-on descriptions are far from being as lively documents as a support document, I guess.

]]> By: James http://coffeeonthekeyboard.com/the-evolution-of-sumo-339/comment-page-1/#comment-6658 James Wed, 24 Feb 2010 18:26:59 +0000 http://coffeeonthekeyboard.com/?p=339#comment-6658 @Axel: We probably won't be sharing Django apps, but we are sharing libraries, middleware, and anything else we can. For l10n, there are really two problems: interface l10n--which we'll handle with gettext--and content l10n. The latter is the tricky part, but there are good examples. Even AMO has localized add-on descriptions. It's not a trivial problem, of course, and I'm glad you're willing to help us make sure the l10n process is great! @Axel: We probably won’t be sharing Django apps, but we are sharing libraries, middleware, and anything else we can.

For l10n, there are really two problems: interface l10n–which we’ll handle with gettext–and content l10n. The latter is the tricky part, but there are good examples. Even AMO has localized add-on descriptions. It’s not a trivial problem, of course, and I’m glad you’re willing to help us make sure the l10n process is great!

]]> By: Axel Hecht http://coffeeonthekeyboard.com/the-evolution-of-sumo-339/comment-page-1/#comment-6652 Axel Hecht Wed, 24 Feb 2010 09:39:47 +0000 http://coffeeonthekeyboard.com/?p=339#comment-6652 I seriously hope this will go well. My webapps are all over django, which makes me both a fan boy and a grain of salt. You know all the good stuff, so here's the salt ;-) Fixtures are nice for small apps, but my apps tend to grow to a size that makes it hard to actually come up with good test data to run interesting tests on. Not sure on which side of the story sumo apps would be. Are there any concrete ideas on which apps to share between sumo and amo? Regarding wiki l10n, I'm happy to see that l10n is all over the notes. I'd like to add that tikiwiki is the only system I have found so far that doesn't totally suck on translating live documents, though. Make sure to design that one with as much input from the l10n community as possible? I'll totally comment and help out here myself. Historically, this is risky business. MDC l10n died on "good enough for now" and hasn't recovered ever since. Makes the bad news that you might have to start off in that area by being better than tikiwiki from the get go. I'm aware that this is pretty much an "asshole requirement", but we shouldn't be surprised if SUMO needs to make up for MDC here. Again, or still, maybe? I seriously hope this will go well. My webapps are all over django, which makes me both a fan boy and a grain of salt. You know all the good stuff, so here’s the salt ;-)

Fixtures are nice for small apps, but my apps tend to grow to a size that makes it hard to actually come up with good test data to run interesting tests on. Not sure on which side of the story sumo apps would be.

Are there any concrete ideas on which apps to share between sumo and amo?

Regarding wiki l10n, I’m happy to see that l10n is all over the notes. I’d like to add that tikiwiki is the only system I have found so far that doesn’t totally suck on translating live documents, though. Make sure to design that one with as much input from the l10n community as possible? I’ll totally comment and help out here myself. Historically, this is risky business. MDC l10n died on “good enough for now” and hasn’t recovered ever since. Makes the bad news that you might have to start off in that area by being better than tikiwiki from the get go. I’m aware that this is pretty much an “asshole requirement”, but we shouldn’t be surprised if SUMO needs to make up for MDC here. Again, or still, maybe?

]]> By: SUMO Blog » Blog Archive » The Evolution of SUMO http://coffeeonthekeyboard.com/the-evolution-of-sumo-339/comment-page-1/#comment-6645 SUMO Blog » Blog Archive » The Evolution of SUMO Wed, 24 Feb 2010 00:28:38 +0000 http://coffeeonthekeyboard.com/?p=339#comment-6645 [...] post by James Socol of the webdev team. Comments or questions? Head on over to James’ original blog post and comment [...] [...] post by James Socol of the webdev team. Comments or questions? Head on over to James’ original blog post and comment [...]

]]>