https://wiki.sugarlabs.org/go/Features/Feature_Template
On the one hand it is a useful template to guide a consensus approach,
most of us are familar with it, and it ties into the release process.
On the other hand,
- the feature process is tied to the Wiki, and as most people here
aren't
Is a wiki features page the right way to get the design documented for
this project?
Tony
On 05/20/2017 05:54 AM, Walter Bender wrote:
One of the pre-summer tasks is to answer that question.
On May 19, 2017 5:51 PM, "James Cameron" > wrote:
On Fri, May 19, 2017 at 05:57:18PM -0400, Samuel Cantero wrote:
> I thought the community had the answer about why ASLOv2 failed!
What was the answer?
--
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
On Fri, May 19, 2017 at 06:13:44PM +0800, Tony Anderson wrote:
> Thanks for the list of Fructose activities, I have been trying to
> find a definitive list since the issue was raised.
I'm surprised. Just ask next time? You asked on a Debian mailing
list, but it was off-topic for that list, and
I thought the community had the answer about why ASLOv2 failed! Personally,
I would love to review Sam's ASLO.
Best,
Sam C.
On Fri, May 19, 2017 at 5:54 PM, Walter Bender
wrote:
> One of the pre-summer tasks is to answer that question.
>
>
> On May 19, 2017 5:51 PM,
One of the pre-summer tasks is to answer that question.
On May 19, 2017 5:51 PM, "James Cameron" wrote:
> Samuel & Jatin,
>
> Rather than make a new Django app to replace a PHP app, please
> consider the previous New ASLO written by Sam Parkinson with help from
> many of us
Samuel & Jatin,
Rather than make a new Django app to replace a PHP app, please
consider the previous New ASLO written by Sam Parkinson with help from
many of us here.
https://github.com/samdroid-apps/aslo
This work started around 16th April 2014, and the last commit was on
18th July 2015.
It
Thanks very much for this. I am optimistic that our path is converging.
* The "python setup.py genpot" step implemented in BundleBuilder does
extract the summary and description for localisation.
The best problem is one that is already solved.
* The root problem is the loss of activity
Composite reply to several posts, see text in quoted context below.
In summary;
- the translation of summary and description is already handled by
sugar3.activity.bundlebuilder module,
- a root problem is loss of activity maintainers, and this effort
won't fix that, so it will be wasted
Hi Chris
Currently there are two text fields per activity in ASLO: Summary and
Description.
This gets a bit more complicated since these text fields edited by the
developer in github.
Perhaps this might work. Have a po directory in the activities/
directory of the bundle. When the activity
On Thu, May 18, 2017 at 10:36 PM, Tony Anderson wrote:
> Hi, Jatin
>
> I think you are familiar with Pootle. The trick with Django is that the
> display of strings is indirect.
>
> First, the locale is set client-side so ASLO needs to determine the
> applicable locale -
Hi Sam,
Thanks for the proposal. Naturally this raises the question of the
relationship between your ASLOv3 and the GSOC project. Do you see two
parallel implementations or a merger of the two projects?
I agree with your proposal to install the activity repositories in
I just realized that proposal wasn't send to sugar-devel list. It was
removed from the thread at some point. So I just forward the link again.
Sorry for people subscribed to multiple lists.
https://goo.gl/VEIzCr
Best,
Sam C.
On Wed, May 17, 2017 at 4:06 PM, James Cameron
Yes, please attach any files that developers should see.
The sugar-devel@ mailing list has a message size limit of 1024K.
Messages above the limit are held for approval by Sebastian and I.
My previous offer still stands; if people truly have no time to edit a
Wiki, set up public web hosting, or
14 matches
Mail list logo