[somos-azucar] Resumen de somosazucar, Vol 24, Envío 24

[Boniek]

MIS COLEGAAS ESTAN DESARROLLANDO UNA PLATAFORMA BASADA EN BSD KERNEL,
ESPERO PRONTO ACABAR PARA DAR RESULTADOS CONCRETOS Y SINCEROS ANTE LA
PROBLEMATICA Y FALTA DE LIDERES SIN FINES DE LUCRO EN NUESTRO PAIS. SERA
MULTILENGUAJE PAR NUESTRO PAIS.
GRACIAS



                         .011001100110.


El 13 de abril de 2012 15:07, <somosazucar-request en lists.sugarlabs.org>escribió:

> Envíe los mensajes para la lista somosazucar a
>        somosazucar en lists.sugarlabs.org
>
> Para subscribirse o anular su subscripción a través de la WEB
>        http://lists.sugarlabs.org/listinfo/somosazucar
>
> O por correo electrónico, enviando un mensaje con el texto "help" en
> el asunto (subject) o en el cuerpo a:
>        somosazucar-request en lists.sugarlabs.org
>
> Puede contactar con el responsable de la lista escribiendo a:
>        somosazucar-owner en lists.sugarlabs.org
>
> Si responde a algún contenido de este mensaje, por favor, edite la
> linea del asunto (subject) para que el texto sea mas especifico que:
> "Re: Contents of somosazucar digest...". Además, por favor, incluya en
> la respuesta sólo aquellas partes del mensaje a las que está
> respondiendo.
>
>
> Asuntos del día:
>
>   1. Re: Cordinacion Hexoquinasa (Sebastian Silva)
>   2. Re: [Sugar-devel] [DESIGN] Home views (was: Request for
>      Sweets Distribution logo) (Eduardo H. Silva)
>   3. Re: Aleksey's Benefits Request (Laura Vargas)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 13 Apr 2012 13:33:06 -0500
> From: Sebastian Silva <sebastian en somosazucar.org>
> To: David Cruz Herrada <dacruz132 en gmail.com>,   Neyder Achahuanco Apaza
>        <redyen2099 en gmail.com>,         Rubsoft <rubsoft en gmail.com>,
> Eleazar Pacho
>        <eleazarpacho en gmail.com>
> Cc: todos <todos en somosazucar.org>
> Subject: Re: [somos-azucar] Cordinacion Hexoquinasa
> Message-ID:
>        <CABNfu5VESzrRB8dHXj6cjBJizT+vwKTBt5dsTB0yWzfDgxRndQ en mail.gmail.com
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> Estimados miembros del equipo Escuelab Puno,
>
> Nunca recibí respuesta a este correo de hace dos semanas.
>
> Por el cariño que les tengo, seguimos pendientes de ustedes.
>
> La red de soporte y distribución de contenidos Sugar Network [1] requiere
> de la ejecución de un piloto [2].
>
> Si el proyecto de ustedes, como han indicado, es diferente, también
> agradecería una respuesta definitiva para concentrar nuestras energías en
> otros miembros de nuestra comunidad en Puno y en el piloto en Comas.
>
> Saludos,
> Sebastian
>
> [1] http://pe.sugarlabs.org/go/Proyecto_Piloto_Hexoquinasa
>
> [2]
> http://wiki.sugarlabs.org/go/Platform_Team/Sugar_Network/Mejorar_Sistema
>
>
> El 23 de marzo de 2012 12:09, Sebastian Silva
> <sebastian en somosazucar.org>escribió:
>
> > Hola David y equipo,
> > Vemos con muy buenos ojos que se esté asumiendo una posición crítica.
> > Justamente buscamos abrir espacios de disención y pluralidad.
> >
> > El proyecto Hexoquinasa ha sido pensado para escalar a nivel nacional.
> > Por lo tanto cada nodo regional goza un espacio para adaptar la
> metodología
> > a su realidad.
> >
> > Desde el punto de vista técnico el grueso del trabajo de diseño y
> > desarrollo
> > ya se ha hecho. Es por ello que es tiempo de programar el piloto, el cual
> > ha sido diseñado en colaboración con los miembros de Escuelab Puno.
> >
> > Escuelab Puno tiene la experiencia como para delinear la metodología de
> > despliegue necesaria para hacer del piloto un éxito. Entiéndase éxito
> como
> > la consecución de los objetivos del proyecto: "mejorar la experiencia de
> > uso y apropiación" [1] y específicamente "desarrollar hexoquinasa",
> > "conformar red de usuarios", "medir el uso de la red".
> >
> > La lógica de este diseño obedece a la hipótesis de definir la
> > participación en la comunidad, el acceso a contenidos y el soporte como
> > factores críticos de éxito para el mejoramiento de la experiencia de
> > usuario y su apropiación.
> >
> > Esto es lo que se ha documentado en la Wiki desde Noviembre [2]
> >
> > Esperamos del equipo de Puno proactividad en la definición de sus
> > respectivos roles y definir los recursos necesarios para garantizar
> > la activación de la red de soporte nacional desde Puno.
> >
> > Un abrazo,
> > Sebastian
> >
> > [1] http://pe.sugarlabs.org/go/Proyecto_Piloto_Hexoquinasa
> > [2] http://wiki.sugarlabs.org/go/Deployment_Team/Peru/Puno
> >
> > On Fri, 23 Mar 2012 11:08:35 -0500
> > David Cruz Herrada <dacruz132 en gmail.com> wrote:
> >
> > > Saludos  a todos,
> > >
> > >
> > >
> > >
> > > Les escribo referente al proyecto Hexoquinasa, y hablo el equipo de
> Puno
> > >
> > > Antecedentes
> > > Sabes  que sugar  es una plataforma  abierta, que  ha sido  desplegada
> en
> > > varios paises pero  hasta la fecha  no  ha  tenido  mucho exito que
> > digamos
> > > salvo Uruguay que se trabajo no en plataformas sino en  capacidades
> > > Docente (fortalecimiento de capacidades) y padres como parte de
>  proceso
> > de
> > > aprendizaje. En el caso de Perú no tiene  mucho exito  debido a la
> falta
> > de
> > > capacidades  en como aplicar las TICs en aula. Aqui sebastian y laura
> uds
> > > ya hicieron  un trabajo de campo  y sabes como es la realidad, que no
> es
> > > solo poner  una herramienta sino es como usarla.
> > >
> > > En el Proyecto  Hexoquinasa  (tanto en objetivos y presupuesto) se esta
> > > priorizando mas el tema de de plataforma realmente que  al final  si en
> > > correcto uso de ella no serviria de mucho. Ahi podemos  pensar que  las
> > > escuelas en Perú  ya tiene  XO malo que  bueno pero quienes de ellos
>  las
> > > utilizan realmente es decir no le sacan probecho salvo excepciones.
> > >
> > > Proponemos equilibrar participaciones  no tanto en el tema de dinero
> sino
> > > en el objetivo del proyecto, para nosotros si lo aplicamos  asi no  va
> > > tener mucho resultado  que mostrar excepto de una plataforma que  puede
> > > funcionar o no. Y uno de los puntos fuertes es la lenguas originarias
> en
> > el
> > > Perú
> > >
> > >
> > > Y finamente de  lo ya  expuesto por nosotros estamos  considerando
> >  nuestra
> > > participacion  en  el proyecto Hexoquinasa, Escuelab Puno  aqui en Puno
> >  ya
> > > tiene  un espacio  ganado en este poco tiempo pequeño pero lo tiene y
> hay
> > > muchos otros casos de exito mostra una de ellas es la particpacion de
> > > Eleazar Pacho en evento organizado por la embajada de EEUU hace unos
> dias
> > > donde  fue  expositor y otros.
> > >
> > > Con esto  no queremos menos preciar el trabajo que están haciendo  en
> el
> > > desarrollo de la plataforma  de SUGARNETWORK que me parece una buen
> > > herramienta pero que por si sola no puede funcionar ahi es donde entra
> el
> > > donce y sus capacidades de usar en el dia  a dia, Hay que considerar
> > > tambien que  DIGETE Y DIGEBIR buscan eso.
> > >
> > >
> > > Esperamos una repuesta
> > >
> > >
> > >
> > >
> > > --
> > > DaVo
> > > David E. Cruz Herrada
> > > Mail: davo en escuelabpuno.org
> > > Web: www.escuelabpuno.org
> > > Cel 994403557 - 951155060
> > > Skype davo.13
> > >
> > > * "No hay cultura sin cambio y no hay cambio sin experimento e
> > innovación."*
> > > Autor: ESCUELAB
> >
> >
> > --
> > Sebastian Silva <sebastian en somosazucar.org>
> >
> ------------ próxima parte ------------
> Se ha borrado un adjunto en formato HTML...
> URL: <
> http://lists.sugarlabs.org/archive/somosazucar/attachments/20120413/15341295/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Fri, 13 Apr 2012 13:04:30 +0100
> From: "Eduardo H. Silva" <hoboprimate en gmail.com>
> To: Aleksey Lim <alsroot en sugarlabs.org>
> Cc: somosazucar en lists.sugarlabs.org, sugar-devel en lists.sugarlabs.org,
>        sugar-network en googlegroups.com, Gary C Martin <gary en garycmartin.com
> >
> Subject: Re: [somos-azucar] [Sugar-devel] [DESIGN] Home views (was:
>        Request for Sweets Distribution logo)
> Message-ID:
>        <CAM0XGOdoBHm8wPgdc7KrRCdZxjR+7o8PX8qf3f9NCKFf6rFvSw en mail.gmail.com
> >
> Content-Type: text/plain; charset=UTF-8
>
> No dia 13 de Abril de 2012 06:02, Aleksey Lim <alsroot en sugarlabs.org>
> escreveu:
> > On Thu, Apr 12, 2012 at 09:54:10AM -0400, Frederick Grose wrote:
> >> On Thu, Apr 12, 2012 at 2:29 AM, Aleksey Lim <alsroot en sugarlabs.org>
> wrote:
> >>
> >> > On Thu, Apr 12, 2012 at 06:05:56AM +0000, Aleksey Lim wrote:
> >> > > On Wed, Apr 11, 2012 at 12:00:37PM -0400, Frederick Grose wrote:
> >> > > >
> >> > > > This segregation is not  so 'harmonic'.
> >> > >
> >> > > Yeah, thats right...
> >> > >
> >> > > > Would this be a situation where a global emblem could be applied
> to the
> >> > > > Activity icon of globally sourced Activities?
> >> > >
> >> > > You mean having a badge painted on activity icons for activities
> that
> >> > > came from the Sugar Network? It might be the way if we decide to
> have
> >> > > both kinds activities (local and from Sugar Network) in one list.
> >> > > Right now, it is not clear for me.
> >> > >
> >> > > > And shouldn't the Home view options be harmonized with the
> filters we
> >> > have
> >> > > > in the Journal?
> >> > > > Then one could view all in a list by removing the favorites
> toggle, or
> >> > > > filter the favorites by the menu of filters.
> >> > >
> >> > > Originally, the intention was having Sugar Network icon as a 2nd/3rd
> >> > > icon in Home view (not in activities tray how it is implemented
> right
> >> > > now). The problem was (it is possible but not trivial) with setting
> up
> >> > > interactions between Sugar Network client application (which is
> local
> >> > > Web application) and Sugar Shell, also, making it easy to run Sugar
> >> > > Network client in standalone mode.
> >> > >
> >> > > But maybe having exactly Sugar Network view embodied to Home, is the
> >> > > right way to go. We can, reserver a place for Sugar Network icon in
> Home
> >> > > view and move client there after completing more needed work.
> >> > >
> >> > > The original problem is, Sugar Network exists in parallel with
> F1/F2/F3
> >> > > views:
> >> >
> >>
> >> This is a key feature, which suggests that one always has the relevant
> >> Sugar Network services at hand (nomodes), at least as a design goal.
> >
> > Yeah. For example, I'm not quite happy with current implementation when
> > Sugar Network icon is in activities tray: it is not an activity (but
> > rather a general service) and, e.g., it is hard to fast switch between
> > Sugar Network view and current activity.
> >
> >> Global features could be revealed from a button in the Neighborhood view
> >> toolbar, or triggered by touching the Neighborhood view icon (a
> subsequent
> >> touch would reveal the traditional Neighborhood).
> >>
> >> Group level features could be revealed from 'project or thread' icons in
> >> the Group view field.
> >
> > If I got you you right, you are talking about:
> >
> >    If we have the current status quo:
> >
> >    * F1, global view
> >    * F2, group view
> >    * F3, local/personal view
> >
> >    And need to embody Sugar Network to basic Sugar Shell UI,
> >    we can scatter Sugar Network UI between these three levels?
> >
> >    * F1, a toolbar button (or a subsequent touch for frame button)
> >      to switch between current F1 view and Sugar Network view with
> >      exposing all the content accessible globally (if we are connected
> >      to the server)
> >    * F2, the same switch mechanism for group related functionality (if
> >      it will exist) of Sugar Network
> >    * F3, the same switch mechanism to see Sugar Network content
> >      accessible in off-line
> >
> >> Offline copies would be identified with badges in the Journal and Home
> >> views.  Filters could segregate them if desired.
> >
> > +1, it should be really useful to save screen space, even for setting
> > off-line/on-line mode, e.g., if cursor is hovering over the left-bottom
> > corner of the activity icon, UI might expose possibility to set this
> flag.
> >
> >> When offline copies are created from a Global-or-Group-view-triggered
> >> screen, a notification like the download notification would offer to
> take
> >> you to the new object's local instance for verification or immediate
> >> action, if desired.
> >
> > From one side, having an alert (like with downloads from Browse) is not
> > needed all time. The SN client library keeps a cache of bundles and if
> > you started the activity, you are trying to make off-line accessible,
> > recently, the process will be immediate.
>
> But some info should be given of the downloading going on when
> launching an uncached activity. Perhaps show some progress bar in the
> activity splash screen?
>
> > From another side, alert
> > might be useful if we need to expose the fact that user is going to
> > persistently take "n bytes" of disk space. But, if we will expose those
> > "n bytes" somewhere in the UI (for "X" Home mode, in popup palette), we
> > don't need alerts (might be annoying) at all.
> >
> > Also we don't need alert to "to take you to the new object's local
> instance".
> > Because the only difference between remote and local activities is a
> > badge, i.e., being off-line user will find activity exactly in the same
> > place where he made it off-line being on-line.
> >
> >> An interim modal version of the Sugar Network may seem to be an
> efficient
> >> construction plan, however, I think that it could severely, and subtly,
> >> limit innovation and integration of the design--if not in the minds of
> >> developers, certainly in the minds of many reviewers.
> >>
> >>         --Fred
> >
> > --
> > Aleksey
> > _______________________________________________
> > Sugar-devel mailing list
> > Sugar-devel en lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
> I wonder if the the bulletin board key could be useful in this
> context, when pressed inside a activity, it would open directly the
> reviews/comments view.
> Oh, and the help icon could have a link to the help/guides view.
>
> Eduardo
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 13 Apr 2012 15:06:48 -0500
> From: Laura Vargas <laura en somosazucar.org>
> To: Aleksey Lim <alsroot en sugarlabs.org>
> Cc: todos <todos en somosazucar.org>, Sebastian Silva
>        <sebastian en somosazucar.org>, Alfredo Gutiérrez
>        <alfredo en somosazucar.org>,      Koke Contreras <
> koke en somosazucar.org>
> Subject: Re: [somos-azucar] Aleksey's Benefits Request
> Message-ID:
>        <CAHbZrxpkkaEMo=ohVfpuhVM+Y8n62s7-t=Gkk_536KFafr8Edg en mail.gmail.com
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> 2012/4/11 Aleksey Lim <alsroot en sugarlabs.org>
>
> > On Wed, Apr 11, 2012 at 05:10:47PM -0500, Laura Vargas wrote:
> > > 2012/4/11 Aleksey Lim <alsroot en sugarlabs.org>
> > >
> > > > On Wed, Apr 11, 2012 at 12:25:49AM -0500, Laura Vargas wrote:
> > > > >
> > > >
> > > > Just one question to avoid futher misunderstanding, is this thread
> > > > spreadsheet the plan for local Hexoquinasa project?
> > >
> > >
> > > Yes.
> > >
> > >
> > > > i.e., the financial
> > > > plan that Board will consider for approving will include other
> > projects,
> > > > how I see them (fix me if I'm wrong):
> > > >
> > > > * Escuelab Puno
> > > >  funds for processing Puno pilot
> > >
> > >
> > > As for Escuelab Puno, this is an incorporated NGO, not a SL Perú
> project
> > > and not under the supervision of the Board.
> > >
> > > There are many members of the SL Perú community located in the region
> of
> > > Puno, some of them will be playing active roles in Hexoquinasa Project
> > > Pilot and therefore they are considered in Hexoquinasa's Financial
> Plan.
> >
> > But Escuelab Puno was created exactly to process Puno deployment(s),
> > and if I got the last SL Peru meeting right, the agreement was that
> > Escuelab Puno is part of global Peruvian community (thus, a part of SL
> > Peru)
> > and there is an intention to work within the one effort (as one of SL
> Peru
> > projects) on Puno pilot of Hexoquinasa project?
> >
> > In other words, Escuelab Puno, to successfully process Puno pilot, needs
> > to request funds from SL Peru Board, i.e., create funding request ticket
> > when it needs to mention the timeline for finding, the purpose of
> > finding, the benefits for SL Peru community, and how to revise results
> > (as all other projects, i.e., Hexoquinasa and Harmonic Distribution).
> >
> > > * Harmonic Distribution
> > > >  funds for releasing the first candidate (v0.3) that will be used as
> > > >  a basis for Hexoquinasa distribution to use in Puno pilot
> > > >
> > > >
> > > Harmonic Distribution in not a SL Perú project either, instead we have
> > > allocated your contribution (as Upstream Developer) within the
> > Hexoquinasa
> > > Financial Plan.
> >
> > Keeping in mind the whole this thread, I can only repeat myself. Why
> global
> > SL funding workflow is broken (and SL Peru does not take into account all
> > lessons, at least from my pov) is because:
> >
> > * the full process is not well represented for community
> >  (on ML and Wiki)
> > * the funding strategy is not-clear/absent-at-all for all community
> >  participants
> >
> > Since the process (SL Peru) started as a community driven process (not a
> > process of close group of people), the clear picture about whats going
> > on and for what reason, and how it is turned to the current status,
> > is critically important. It is similar to how ideal state government
> should
> > happen: the citizens are not being managed by the government, but
> > citizens hired managers to better manage existing funds (in the name of
> > citizens themselves). It should not happen (how it happens in my country
> > at least) because managers assure citizens that they (managers) do
> > everything right, but because the whole process is transparent and
> > everyone can monitor it.
> >
> > What I see right now (from spreadsheet), Hexoquinasa is not a local
> > project,
> > it behaves like the only project within the SL Peru (I guess the
> > original conflict with Escuelab Puno was exactly due to situation like
> > that). Keeping all things in one place make it really messy and bad
> > understanding for community.
> >
> > From my point of view, it is better to:
> >
> > * clearly separate [sub]projects
> >
>
> Granted. We will clearly separate Hexoquinasa's Production from
> Hexoquinasa's Pilots.
>
> * well document each [sub]project
> >
>
> We (the somos azúcar team) can only take responsibility (as for now) for
> Hexoquinasa's Production.
>
>
> > * expose the roadmap/timeline for each [sub]projects
> >
>
> We are learning to make documentation. Hopefully we will be improving with
> practice.
>
>
> > * clearly say who is responsible for processing each [sub]projects
> >
>
> Agree.
>
> * and how to revise each [sub]project's results
> >
>
> Agree.
>
> >
> > From the technical (not people) point of view, it might be:
> >
> > * developing Harmonic Distribution candidate
> >  goal: the technical basis for Hexoquinasa distribution
> >  responsibility: alsroot
> >  timeline: HD-0.3 until June
> >  funds needed: ...
> >
> >
> +1
>
>
> > * developing Hexoquinasa candidate
> >  goal: complete product to support edu deployments
> >  responsibility: icarito, kameetza
> >  timeline: Hexoquinasa-0.3 until June
> >  funds needed: ...
> >
> > +1
>
>
> > * processing Sugar Camp Puno (Escuelab Puno)
> >  goal: complete i18n, mobilize people that will take part in Puno, make
> > sure that Hexoquinasa candidate works
> >  responsibility: david, eleazar, neyder
> >  timeline: ...
> >  funds needed: ...
> >
> >
> This is not confirmed at this point. Edgar Quispe and other members of SL
> community (that are not Escuelab Puno) are willing to perform as well.
>
> * train chaski (Escuelab Puno)
> >  goal: train people who will provide tech support to one-teachers schools
> >  responsibility: david, eleazar, neyder
> >  timeline: ...
> >  funds needed: ...
> >
> >
> This is not confirmed at this point either. So far, Icarito is taking
> responsibility for this as well.
>
> * ...
> >
> > So, we will get:
> >
> > * the full process (not only current state) is clear for community
> >
> > * for possible funding requesters, it will be clear can they afford to
> >  ask for funding or not (are their projects important enough to couple
> >  existing funds)
> >
> > * possible donators can see what ongoing projects are and make
> >  targeted donations
> >
> > --
> > Aleksey
> >
> ------------ próxima parte ------------
> Se ha borrado un adjunto en formato HTML...
> URL: <
> http://lists.sugarlabs.org/archive/somosazucar/attachments/20120413/ec600430/attachment.html
> >
>
> ------------------------------
>
> _______________________________________________
> somosazucar mailing list
> somosazucar en lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/somosazucar
>
>
> Fin de Resumen de somosazucar, Vol 24, Envío 24
> ***********************************************
>
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <http://lists.sugarlabs.org/archive/sugar-sur/attachments/20120413/1436ebd7/attachment.html>