<div>Hi all</div><br> <br><br><div class="gmail_quote">On Tue, Nov 9, 2010 at 9:15 PM, Aleksey Lim <span dir="ltr"><<a href="mailto:alsroot@member.fsf.org">alsroot@member.fsf.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div><div></div><div class="h5">On Wed, Nov 10, 2010 at 12:18:48PM +1100, James Cameron wrote:<br> > On Wed, Nov 10, 2010 at 12:20:22AM +0000, Aleksey Lim wrote:<br> > > On Wed, Nov 10, 2010 at 10:51:51AM +1100, James Cameron wrote:<br> > > > On Tue, Nov 09, 2010 at 11:23:46PM +0000, Aleksey Lim wrote:<br> > > > > On Wed, Nov 10, 2010 at 09:53:18AM +1100, James Cameron wrote:<br> > > > > > These announcements from <a href="http://activities.sugarlabs.org" target="_blank">activities.sugarlabs.org</a> of new releases are<br> > > > > > sent without any included identity of the person who did the release.<br> > > > > ><br> > > > > > Could <a href="http://activities.sugarlabs.org" target="_blank">activities.sugarlabs.org</a> please be changed to include the releaser<br> > > > > > in these messages?<br> > > > ><br> > > > > The problem is that uploaders don't include release notes. The proper<br> > > > > fix might be do not accept them (from uploading checks), so patches are<br> > > > > welcome :).<br> > > ><br> > > > No, I think you misunderstand. My observation has nothing to do with<br> > > > whether release notes are present in the mail message.<br> > > ><br> > > > Where's the code?<br> > ><br> > > <a href="http://git.sugarlabs.org/projects/slo-activities" target="_blank">http://git.sugarlabs.org/projects/slo-activities</a><br> > > <a href="http://wiki.sugarlabs.org/go/Activity_Library/Devel/Installing" target="_blank">http://wiki.sugarlabs.org/go/Activity_Library/Devel/Installing</a><br> ><br> > The file site/app/views/editors/email/aslo/release_en_plain.thtml<br> > contains what looks like the release messages, but I cannot see where it<br> > is used. What is needed is the authenticated user's e-mail address.<br> ><br> > > But keep in mind that current code is php/cake based and<br> > > new ASLO will be based on new AMO python/django code. So, would be<br> > > useful if patch is not invasive and might be applied w/o starting new<br> > > development/testing/production cycle.<br> ><br> > That says to me, "don't do anything, your effort will be wasted, nobody<br> > else cares about this problem." Thanks for the warning. I see no way<br> > forward.<br> <br> </div></div>The thing is, we are using not supported AMO code base that have<br> long standing bugs. Upstream has switched to django and we need to do<br> the same. So, if you was thinking about easy hacking, then you was wrong ;)<br></blockquote><div><br></div><div><br></div><div>from AMO's Wiki [1] the migration is not yet complete: </div><div><br></div><div><span class="Apple-style-span" style="font-family: verdana, sans-serif; line-height: 16px; ">''This project is currently underway, and will take some cycles to complete. Bugs that take too much work to fix will likely be delayed until Zamboni is completed, in order to prevent duplicate work when porting features.''</span></div> <div><span class="Apple-style-span" style="font-family: verdana, sans-serif; line-height: 16px; "><br></span></div><div><span class="Apple-style-span" style="font-family: verdana, sans-serif; line-height: 16px; ">Zamboni <span class="Apple-style-span" style="line-height: 33px; ">[2]<span class="Apple-style-span" style="line-height: 23px; "> is the code name for the Django project.</span></span></span></div> <div><span class="Apple-style-span" style="font-family: verdana, sans-serif; line-height: 16px; "><br></span></div><div><span class="Apple-style-span" style="font-family: verdana, sans-serif; line-height: 16px; ">[1] <a href="https://wiki.mozilla.org/AMO:Editors/InfoEditors">https://wiki.mozilla.org/AMO:Editors/InfoEditors</a></span></div> <div><font class="Apple-style-span" face="verdana, sans-serif"><span class="Apple-style-span" style="line-height: 23px;">[2]<a href="http://blog.fligtar.com/2010/01/15/amo-zamboni-planning-underway/">http://blog.fligtar.com/2010/01/15/amo-zamboni-planning-underway/</a></span></font></div> <div><span class="Apple-style-span" style="font-family: verdana, sans-serif; line-height: 16px; "><br></span></div><div><font class="Apple-style-span" face="verdana, sans-serif"><span class="Apple-style-span" style="line-height: 23px;"><br> </span></font></div><div><span class="Apple-style-span" style="font-family: verdana, sans-serif; line-height: 16px; "><br></span></div><div><span class="Apple-style-span" style="font-family: verdana, sans-serif; line-height: 16px; "><br> </span></div><div><span class="Apple-style-span" style="font-family: verdana, sans-serif; line-height: 16px; "><br></span></div><div><span class="Apple-style-span" style="font-family: verdana, sans-serif; line-height: 16px; "><br> </span></div><div><span class="Apple-style-span" style="font-family: verdana, sans-serif; line-height: 16px; "><br></span></div><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> --<br> <font color="#888888">Aleksey<br> </font><div><div></div><div class="h5">_______________________________________________<br> Sugar-devel mailing list<br> <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br> </div></div></blockquote></div><br><div><br></div>