[Sugar-devel] New ASLO Project Definition

[James Cameron]

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 using the Wiki it may be exclusionary to demand it, just as
  it is exclusionary to demand use of Google Docs,

- the feature process has been used and tuned more for Sugar than for
  server infrastructure, and;

- the process is tied to a regular Sugar platform release schedule,
  which we have since lost.

It may be more effective to document the design in parts, posting each
part to the sugar-devel@ mailing list as it becomes available.

Holding back until a design is complete, and therefore lengthy, will
trigger a TL;DR response.

On Sat, May 20, 2017 at 09:55:59AM +0800, Tony Anderson wrote:
> 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" <[1]quozl at laptop.org> 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 here.
> 
>         [2]https://github.com/samdroid-apps/aslo
> 
>         This work started around 16th April 2014, and the last commit was on
>         18th July 2015.
> 
>         It is written in Python, uses Flask, Docker, git, and has a workflow
>         that is very close to what Samuel has defined.
> 
>         Instead of a separate GitHub organisation, Sam designed a registry
>         repository;
> 
>         [3]https://github.com/samdroid-apps/sugar-activities
> 
>         This uses JSON metadata derived in part from the .info files.
> 
>         An aslo-bot was responsible for detecting releases in activity
>         repositories and adjusting the registry.
> 
>         The New ASLO is already integrated with the Social Help discourse
>         forum.
> 
>         Chris has reminded us, the New ASLO already has translations;
>         [4]https://translate.sugarlabs.org/projects/NewAslo/
> 
>         So please explain why Sam's work cannot be used?
> 
>         --
>         James Cameron
>         [5]http://quozl.netrek.org/
>         _______________________________________________
>         Sugar-devel mailing list
>         [6]Sugar-devel at lists.sugarlabs.org
>         [7]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
>    
>     _______________________________________________
>     Sugar-devel mailing list
>     [8]Sugar-devel at lists.sugarlabs.org
>     [9]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:quozl at laptop.org
> [2] https://github.com/samdroid-apps/aslo
> [3] https://github.com/samdroid-apps/sugar-activities
> [4] https://translate.sugarlabs.org/projects/NewAslo/
> [5] http://quozl.netrek.org/
> [6] mailto:Sugar-devel at lists.sugarlabs.org
> [7] http://lists.sugarlabs.org/listinfo/sugar-devel
> [8] mailto:Sugar-devel at lists.sugarlabs.org
> [9] http://lists.sugarlabs.org/listinfo/sugar-devel

> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel


-- 
James Cameron
http://quozl.netrek.org/