[Sugar-devel] anonymous ASLO messages
alsroot at member.fsf.org
Tue Nov 9 21:15:11 EST 2010
On Wed, Nov 10, 2010 at 12:18:48PM +1100, James Cameron wrote:
> On Wed, Nov 10, 2010 at 12:20:22AM +0000, Aleksey Lim wrote:
> > On Wed, Nov 10, 2010 at 10:51:51AM +1100, James Cameron wrote:
> > > On Tue, Nov 09, 2010 at 11:23:46PM +0000, Aleksey Lim wrote:
> > > > On Wed, Nov 10, 2010 at 09:53:18AM +1100, James Cameron wrote:
> > > > > These announcements from activities.sugarlabs.org of new releases are
> > > > > sent without any included identity of the person who did the release.
> > > > >
> > > > > Could activities.sugarlabs.org please be changed to include the releaser
> > > > > in these messages?
> > > >
> > > > The problem is that uploaders don't include release notes. The proper
> > > > fix might be do not accept them (from uploading checks), so patches are
> > > > welcome :).
> > >
> > > No, I think you misunderstand. My observation has nothing to do with
> > > whether release notes are present in the mail message.
> > >
> > > Where's the code?
> > http://git.sugarlabs.org/projects/slo-activities
> > http://wiki.sugarlabs.org/go/Activity_Library/Devel/Installing
> The file site/app/views/editors/email/aslo/release_en_plain.thtml
> contains what looks like the release messages, but I cannot see where it
> is used. What is needed is the authenticated user's e-mail address.
> > But keep in mind that current code is php/cake based and
> > new ASLO will be based on new AMO python/django code. So, would be
> > useful if patch is not invasive and might be applied w/o starting new
> > development/testing/production cycle.
> That says to me, "don't do anything, your effort will be wasted, nobody
> else cares about this problem." Thanks for the warning. I see no way
The thing is, we are using not supported AMO code base that have
long standing bugs. Upstream has switched to django and we need to do
the same. So, if you was thinking about easy hacking, then you was wrong ;)
More information about the Sugar-devel