Re: [Sugar-devel] Music Blocks v3.0 is released.

[James Cameron]

On Wed, Mar 04, 2020 at 07:25:58AM -0500, Walter Bender wrote:
> 
> On Tue, Mar 3, 2020 at 8:52 PM Walter Bender <[1]walter.ben...@gmail.com>
> wrote:
> 
> Sugar yes. The new version of Browse should work nicely.
> Sugarizer, no. Lionel has said it is too large.
> 
> On Tue, Mar 3, 2020 at 7:53 PM James Cameron <[2]qu...@laptop.org> wrote:
> 
> Are there any plans to add Music Blocks to Sugarizer or Sugar?
> 
> At James: What is the recommended approach to embedding inside Browse these
> days?

It depends on what browser features the application needs.  If those
features are contained within WebKit2.WebView, then not much is
needed.  List the features; e.g. touch events, mouse clicks, keyboard
events, back and forward button, reload, etc.

HelpActivity and JupyterLabs both instantiate a WebKit2.WebView.

WikipediaActivity does a sideways import of Browse.

Sugar Web activities have a WebKit2.WebView instantiated for them by
Sugar when exec is /usr/bin/sugar-web-activity.

> In the past, I simply modified the HOME_PAGE_GCONF_KEY to use a copy
> of musicblocks included in the bundle.

The port from GConf to Gio.Settings brought with it a design
inadequacy, that configuration keys needed to be defined in a schema
before the program ran, and GNOME project envisaged this would be most
commonly handled by running glib-compile-schemas at package install.

Sugar activity bundles don't have that available to them.

There was a way around it; define a schema at runtime, but that meant
the URL is stored inside the activity root directory.  Details are in
_get_local_settings in browser.py.

> Do you recommend removing some unrelated Browse functionality, such
> as the search bar?

It is best to offer only user interface elements that are meaningful
to use of the application.

> Do you think it is worth modifying Browse itself to make it easier
> to do this sort of embedding?

That depends on what user interface elements are needed, and that
depends on what browser features are needed.

The choice will be somewhere on this spectrum;

* use a WebKit2.WebView with no significant user interface elements,

* use a WebKit2.WebView with a few user interface elements,

* use the WebActivity and disabled a few user interface elements,

* use the WebActivity with a change to default page,

* start the WebActivity.

> 
> regards.
> 
> -walter
> 
> On Tue, Mar 03, 2020 at 07:33:46PM -0500, Walter Bender wrote:
> > The release reflects the contributions made during Google Code-in
> 2019-2020. It
> > is being designated as a major release since there are numerous
> changes to the
> > user experience (e.g., Widget UX) and many underlying structural
> changes (e.g.,
> > the new Block API and storage mechanism) that impact developers. An
> overhaul of
> > the graphics update mechanism has lead to a major reduction in CPU
> usage. As
> > far as I know, there is only one "incompatibility" with previous
> versions; it
> > is in regard to synchronization: there are some projects that worked
> previously
> > that may now require the use of either the Sync block or the 
> No-clock
> block.
> > (Details are outlined in the release notes.)
> >
> > A tip of the hat to some of the GCI participants who worked so hard
> to make
> > this release possible: Bottersnike, AndreaGon, Pidddgy and
> Nepaltechguy2. They
> > not only contributed code, but also insights into the design and
> > implementation. Also, thanks to the community members who provided
> them with
> > code reviews and feedback (notably @eohomegrownapps, @fakela, and
> @pikurasa).
> > It is also important to acknowledge some of our users, Teddy Dildine
> and Henry
> > Rico, who have been inspiring much of the recent developments and 
> bug
> fixes.
> > Look for some of their work on the Planet. Karin Kinoshita at Gakken
> has also
> > done testing and translation work.
> >
> > [1] [1][3]https://github.com/sugarlabs/musicblocks/releases/tag/v3.0
> >
> > -walter
> >
> > --
> > Walter Bender
> > Sugar Labs
> > [2][4]http://www.sugarlabs.org
> > [3]
> >
> > References:
> >
> > [1] [5]https://github.com/sugarlabs/musicblocks/releases/tag/v3.0
> > [2] [6]http://www.sugarlabs.org/
> > [3] [7]http://www.sugarlabs.org/
> 
> > ___
> > Sugar-devel mailing list
> > [8]Sugar-devel@lists.sugarlabs.org
> > [9]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> James Cameron
> [10]http://quozl.netrek.org/
> ___
> 

Re: [Sugar-devel] Proposal to move communication to other platform

[D. Joe]

On Thu, Mar 05, 2020 at 02:51:09AM +0530, Sumit Srivastava wrote:

> About three years down the line, here's what I learnt:
> 
> 1. Installed two IRC clients for mobile access: Riot.im and IRCCloud

Just a point of clarification: Riot.im is a matrix client, not an IRC client. 

The team leading matrix development and the freenode network hosting #sugar 
cooperate to provide and manage a bridge between the two systems. Riot taps 
into the matrix side of that bridge.

IRCCloud can be considered an IRC client, I guess, but it's also more than 
that: It's a service with multiple tiers, including free-of-charge and 
fee-for-service, to provide yet another app and web front end for those who 
want such things. Some people seem to like it.





 
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar Labs has been accepted into GSoC 2020

[Carlos mauro]

Dear Friend

I want to be a mentor in SugarLabs again in the project port to Python 3
may be is the time to migrate and review the pendings.

I review the code may be is necessary make a litle workload about this
request.

Best Regards.

El jue., 20 feb. 2020 a las 23:21, Jaskirat Singh ()
escribió:

> Thanks I am looking forward to work as an assistant mentor.
>
> On Fri, 21 Feb 2020, 9:43 am James Cameron,  wrote:
>
>> Would those hoping to be mentors please read and review our
>> introduction page, project ideas page, and proposal template,
>> https://github.com/sugarlabs/GSoC
>>
>> And reply here on the mailing list letting us know how you fit the
>> requirements for being mentors.
>>
>> --
>> James Cameron
>> http://quozl.netrek.org/
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>


-- 
Ing. Carlos Mauro Cárdenas Fernández.
CIP Nr 116251.
Casa: 4815857
Claro: 980525716 || RPM: #999314206 || Nextel 121*2502
Creo en el Amor de los Seres Humanos
http://unimauro.blogspot.com.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Mascot for sugar

[James Cameron]

During recent GCI we had much feedback from mentors suggesting that
using a sugarcube does not express the organisation's mission very
well.

The child logo could be animated; make it put down the book, sit up
from cross-legged position, and walk around.

But the original design intent was that the child logo would represent
a user (child learner), not a mascot.

I think a mascot has to be needed before a graphic design can be
chosen.  Apart from using it on a web site, I don't have any ideas how
to need a mascot.

On Wed, Mar 04, 2020 at 04:33:19PM -0500, Devin Ulibarri wrote:
> So far, we have turtle (turtle blocks) and mice (music blocks).
> 
> Maybe a sugarcube? (that would be kind of silly, but who knows?)
> 
> On Wed, 2020-03-04 at 23:31 +0300, Srevin Saju wrote:
> 
> Sugarlabs needs a mascot to welcome new users of the sugar desktop,
> This can be an important part of outreaching sugar to daily desktop users.
> One way of creating a mascot for sugar is to use a competition. The
> benefits are two hold, one is the more people come to know of Sugarlabs 
> and
> their non-profit collective education systems. The other is, we are 
> getting
> a mascot personalized to sugar. Most open source companies have mascots
> too. So its a subject to be brought to discussion, if anyone is interested
> V/r
> 
> [bitmap802]
> SREVIN SAJU
> [1]https://srevinsaju.github.io
> 
> ___
> Sugar-devel mailing list
> [2]Sugar-devel@lists.sugarlabs.org
> [3]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] https://srevinsaju.github.io/
> [2] mailto:Sugar-devel@lists.sugarlabs.org
> [3] http://lists.sugarlabs.org/listinfo/sugar-devel

> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel


-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [IAEP] New logo for Sugar Labs

[Claudia Urrea]

Thank you all for the hours and the effort to design these logos. This
somehow assumes we want to change the logo... perhaps we do, but it would
be great to hear the story behind each of the designs, so we can use it for
branding. We also need to understand the assumptions that were made
regarding the existing logo, what needs to be preserved and what needs to
change, etc. (I have been part of a re-branding process and we began with a
study of the current logo and detected opportunities for the design.)

Would it be ok for the groups to record a short video with those ideas?
Should the community vote on the existing logo vs. these designs?

Thanks again,

Claudia



On Mon, Feb 10, 2020 at 1:04 PM Vipul Gupta 
wrote:

> Hello folks,
> Thanks Peace for the push behind designing a new brand image for Sugar
> Labs. I too like Option 3 with the flexibility it provides.
> I see a lot of potential with that, thanks!
>
>
> On Sun, Feb 9, 2020 at 10:31 PM Peace Ojemeh 
> wrote:
>
>> Hi everyone,
>>
>>
>> I mentioned this earlier a few weeks ago.
>>
>>
>> In the last couple weeks, I’ve been working with a small group of design
>> volunteers(all cc'ed) to come up with a couple of new logo options for
>> Sugar Labs given the fact that there wasn’t really a good design output
>> from the last Google Code-In.
>>
>>
>> We conducted a design sprint in Port Harcourt, Nigeria and we came up
>> with 3 options after several iterations, at this point I would want to
>> share with the community what we've done so the community can decide
>> what logo we should go on with.
>>
>>
>>
>> Regard.
>> --
>> *Peace Ojemeh*(Perrie)
>> Twitter  | Website
>> 
>>
>>
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
>
> --
> Best,
> Vipul Gupta
> Mixster  | Github
> 
>
> ___
> IAEP -- It's An Education Project (not a laptop project!)
> i...@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Mascot for sugar

[Devin Ulibarri]

So far, we have turtle (turtle blocks) and mice (music blocks).
Maybe a sugarcube? (that would be kind of silly, but who knows?)
On Wed, 2020-03-04 at 23:31 +0300, Srevin Saju wrote:
> Sugarlabs needs a mascot to welcome new users of the sugar desktop,
> This can be an important part of outreaching sugar to daily desktop
> users. One way of creating a mascot for sugar is to use a
> competition. The benefits are two hold, one is the more people come
> to know of Sugarlabs and their non-profit collective education
> systems. The other is, we are getting a mascot personalized to sugar.
> Most open source companies have mascots too. So its a subject to be
> brought to discussion, if anyone is interested
> V/r
> 
> 
> SREVIN SAJU
> https://srevinsaju.github.io
> 
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Proposal to move communication to other platform

[James Cameron]

Yes.  Please use webchat.freenode.net as it is better maintained.  I'd
be fine with changing any links.

On Wed, Mar 04, 2020 at 07:57:00PM +, Bottersnike wrote:
> With regards to [1]chat.sugarlabs.org, the version of qwebirc it runs is 10
> years out of date, and it has an SSL certificate that expired 4 years ago. I
> really don't think there's any reason it should ever be recommended to new
> users (over just using freenode) unless it receives a serious update.
> 
> On Wed, Mar 4, 2020 at 7:46 PM Bottersnike <[2]bottersnike...@gmail.com> 
> wrote:
> 
> I think one of the main issues with IRC is the onboarding experience, or
> rather lack thereof. For new users, they're faced with an entirely blank
> screen, with no trivial way to search for past questions, see if a topic
> has been brought up before, or even just read through history to get a
> general idea of the way the organization operates. Sure, there may be
> archives maintained, but for someone who has just discovered SugarLabs and
> wants to contribute, that really isn't going to be a viable solution,
> because it takes significant effort to hunt them down and search through
> them. For established teams, this isn't much of an issue, but it can make
> SugarLabs an incredibly daunting organization for young students from, say
> GCI, or people looking around at different organizations for GSoC.
> 
> > I use Quassel, as it keeps backlog.
> 
> Most clients keep a backlog, but only if your computer is on. That's not
> the situation 24/7 for a lot of people.
> 
> (Sorry for the double message, James. I accidentally used Reply not Reply
> All)
> 
> On Wed, Mar 4, 2020 at 7:15 PM James Cameron <[3]qu...@laptop.org> wrote:
> 
> Thanks for asking.
> 
> For real-time presence messaging, please use IRC channel #sugar on
> [4]freenode.net.  Your choice of client.  I use Quassel, as it keeps
> backlog.
> 
> For store and forward messaging, please use the mailing list.  Your
> choice of client.
> 
> You'll get a voice on choice of tools once you've been working with us
> for a few months.  Until then we can't trust that you've assessed the
> situation accurately.
> 
> Gitter.im was yet another attempt to split our community into the
> haves and the have-nots.  I'm almost ready to ditch my account there
> because it has way less benefit than the cost.  Of receiving a mail
> notification, logging in, and answering the same old questions.  It is
> quite boring.  You can see that if you look through the previous
> discussion, which you'll find was entirely sporadic; someone
> has a question, I answer, nothing else happens.  It could have been
> done in mail.  It costs so much memory and screen real-estate that I
> can't see myself staying connected.  I certainly don't want it
> promoted for Sugar Labs, but I'm willing to keep it available in case
> it turns out to be useful for working with anyone who can't figure out
> how to use IRC.  We must allow for the possibility that someone with a
> disability has been given access to Gitter.im but not to IRC.  So a
> matter of inclusiveness, but not emphasis.
> 
> On Wed, Mar 04, 2020 at 08:03:31PM +0530, Prashant Sengar wrote:
> > Hi,
> >
> > I am sure this request must have been raised earlier as well. I
> wanted to ask
> > if Sugar could create a communication channel on another platform
> such as a
> > discord server, Slack or Telegram instead of IRC to make
> communication easier.
> >
> > The reason why others will be a better option:
> > 1. The chats will be accessible even if I am offline for a while,
> unlike IRC
> > where I cannot see any earlier data.
> > 2. IRC cannot be used on mobile devices, so it creates a barrier in
> > communication. On the other hand, the other chat applications are
> available on
> > all platforms for everyone to use.
> >
> > I would like to request the team to please consider this request. If
> such
> > request has been made earlier and denied due to some reasons, then I
> would like
> > to know them so that I can understand the reasons and work
> accordingly.
> >
> > Regards.
> > Prashant Sengar
> 
> > ___
> > Sugar-devel mailing list
> > [5]Sugar-devel@lists.sugarlabs.org
> > [6]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> James Cameron
> [7]http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> [8]Sugar-devel@lists.sugarlabs.org

Re: [Sugar-devel] Proposal to move communication to other platform

[James Cameron]

On Wed, Mar 04, 2020 at 08:02:42PM +, Bottersnike wrote:
> >Quassel core is a server that keeps the backlog.  I don't need my
> >computer on, and I can view the backlog from any device.
> 
> Without being rude, most people don't have a spare server lying
> around they can spin up an IRC backlog on, especially not people
> interested in reading backlogged messages from before they joined
> the IRC for the first time.

We have an instance of Quassel core on sunjammer.sugarlabs.org, but I
don't know who administers it.

Otherwise, there are other people who run an instance, or you can spin
up a VM in the cloud, which most people seem to do these days with
such a wide variety of software available.

> On Wed, Mar 4, 2020 at 7:59 PM James Cameron <[1]qu...@laptop.org> wrote:
> 
> Thanks for your thoughts.
> 
> Quassel core is a server that keeps the backlog.  I don't need my
> computer on, and I can view the backlog from any device.
> 
> Yes, there are better onboarding experiences.
> 
> However, if people want to talk with us, they'll know where to find
> us.  We're here to get the job done, not provide better experiences
> for developers.
> 
> We do still get students who can use IRC, so I know it is not a
> significant hindrance.
> 
> On Wed, Mar 04, 2020 at 07:46:10PM +, Bottersnike wrote:
> > I think one of the main issues with IRC is the onboarding experience, or
> rather
> > lack thereof. For new users, they're faced with an entirely blank 
> screen,
> with
> > no trivial way to search for past questions, see if a topic has been
> brought up
> > before, or even just read through history to get a general idea of the
> way the
> > organization operates. Sure, there may be archives maintained, but for
> someone
> > who has just discovered SugarLabs and wants to contribute, that really
> isn't
> > going to be a viable solution, because it takes significant effort to
> hunt them
> > down and search through them. For established teams, this isn't much of
> an
> > issue, but it can make SugarLabs an incredibly daunting organization for
> young
> > students from, say GCI, or people looking around at different
> organizations for
> > GSoC.
> >
> > > I use Quassel, as it keeps backlog.
> >
> > Most clients keep a backlog, but only if your computer is on. That's not
> the
> > situation 24/7 for a lot of people.
> >
> > (Sorry for the double message, James. I accidentally used Reply not 
> Reply
> All)
> >
> > On Wed, Mar 4, 2020 at 7:15 PM James Cameron <[1][2]qu...@laptop.org>
> wrote:
> >
> >     Thanks for asking.
> >
> >     For real-time presence messaging, please use IRC channel #sugar on
> >     [2][3]freenode.net.  Your choice of client.  I use Quassel, as it
> keeps
> >     backlog.
> >
> >     For store and forward messaging, please use the mailing list.  Your
> >     choice of client.
> >
> >     You'll get a voice on choice of tools once you've been working with
> us
> >     for a few months.  Until then we can't trust that you've assessed 
> the
> >     situation accurately.
> >
> >     Gitter.im was yet another attempt to split our community into the
> >     haves and the have-nots.  I'm almost ready to ditch my account there
> >     because it has way less benefit than the cost.  Of receiving a mail
> >     notification, logging in, and answering the same old questions.  It
> is
> >     quite boring.  You can see that if you look through the previous
> >     discussion, which you'll find was entirely sporadic; someone
> >     has a question, I answer, nothing else happens.  It could have been
> >     done in mail.  It costs so much memory and screen real-estate that I
> >     can't see myself staying connected.  I certainly don't want it
> >     promoted for Sugar Labs, but I'm willing to keep it available in 
> case
> >     it turns out to be useful for working with anyone who can't figure
> out
> >     how to use IRC.  We must allow for the possibility that someone with
> a
> >     disability has been given access to Gitter.im but not to IRC.  So a
> >     matter of inclusiveness, but not emphasis.
> >
> >     On Wed, Mar 04, 2020 at 08:03:31PM +0530, Prashant Sengar wrote:
> >     > Hi,
> >     >
> >     > I am sure this request must have been raised earlier as well. I
> wanted to
> >     ask
> >     > if Sugar could create a communication channel on another platform
> such as
> >     a
> >     > discord server, Slack or Telegram instead of IRC to make
> communication
> >     easier.
> >     >
> >     > The reason why others will be a better option:
> >     > 1. The chats will be accessible even if I am offline for a while,
>   

Re: [Sugar-devel] Proposal to move communication to other platform

[Sumit Srivastava]

Hi,

It was me, back in 2018, started the conversation of switching to Gitter. [
http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055061.html]

Back then, I was as new to the community as Bottersnike, Prashant, and
Srevin are now.

I had just come from SymPy organisation that used Gitter as their primary
communication channel.

A huge round of appreciation to James for being on Gitter answering all the
incoming questions.

About three years down the line, here's what I learnt:

1. Installed two IRC clients for mobile access: Riot.im and IRCCloud

2. IRC is still a pain to use, and I still prefer (enjoy) answering
questions over the mailing list.

3. It's hard to switch a community to a communication tool 2, unless you
totally ban the original communication tool 1 and end supporting the
original communication tool. Infact, it becomes worse when you have limited
resources and people (something I wasn't aware of when I joined the
community) because the James now has to spend his headspace for answering
questions on IRC, Gitter, mailing list, and has to spend time maintaining
the codebase. Headspace is valuable and limited.

Now that I've made you aware of the actual constraints of the problem, I
think you may want to spend more of your time this GSoC on Gitter answering
questions of the newcomers. :)

I would love to hear new viewpoints from other community members.

PS: Thanks to everyone who answers questions from people new to SugarLabs.

On Thu, Mar 5, 2020, 1:33 AM Bottersnike  wrote:

> >Quassel core is a server that keeps the backlog.  I don't need my
> >computer on, and I can view the backlog from any device.
>
> Without being rude, most people don't have a spare server lying around
> they can spin up an IRC backlog on, especially not people interested in
> reading backlogged messages from *before* they joined the IRC for the
> first time.
>
> On Wed, Mar 4, 2020 at 7:59 PM James Cameron  wrote:
>
>> Thanks for your thoughts.
>>
>> Quassel core is a server that keeps the backlog.  I don't need my
>> computer on, and I can view the backlog from any device.
>>
>> Yes, there are better onboarding experiences.
>>
>> However, if people want to talk with us, they'll know where to find
>> us.  We're here to get the job done, not provide better experiences
>> for developers.
>>
>> We do still get students who can use IRC, so I know it is not a
>> significant hindrance.
>>
>> On Wed, Mar 04, 2020 at 07:46:10PM +, Bottersnike wrote:
>> > I think one of the main issues with IRC is the onboarding experience,
>> or rather
>> > lack thereof. For new users, they're faced with an entirely blank
>> screen, with
>> > no trivial way to search for past questions, see if a topic has been
>> brought up
>> > before, or even just read through history to get a general idea of the
>> way the
>> > organization operates. Sure, there may be archives maintained, but for
>> someone
>> > who has just discovered SugarLabs and wants to contribute, that really
>> isn't
>> > going to be a viable solution, because it takes significant effort to
>> hunt them
>> > down and search through them. For established teams, this isn't much of
>> an
>> > issue, but it can make SugarLabs an incredibly daunting organization
>> for young
>> > students from, say GCI, or people looking around at different
>> organizations for
>> > GSoC.
>> >
>> > > I use Quassel, as it keeps backlog.
>> >
>> > Most clients keep a backlog, but only if your computer is on. That's
>> not the
>> > situation 24/7 for a lot of people.
>> >
>> > (Sorry for the double message, James. I accidentally used Reply not
>> Reply All)
>> >
>> > On Wed, Mar 4, 2020 at 7:15 PM James Cameron <[1]qu...@laptop.org>
>> wrote:
>> >
>> > Thanks for asking.
>> >
>> > For real-time presence messaging, please use IRC channel #sugar on
>> > [2]freenode.net.  Your choice of client.  I use Quassel, as it
>> keeps
>> > backlog.
>> >
>> > For store and forward messaging, please use the mailing list.  Your
>> > choice of client.
>> >
>> > You'll get a voice on choice of tools once you've been working with
>> us
>> > for a few months.  Until then we can't trust that you've assessed
>> the
>> > situation accurately.
>> >
>> > Gitter.im was yet another attempt to split our community into the
>> > haves and the have-nots.  I'm almost ready to ditch my account there
>> > because it has way less benefit than the cost.  Of receiving a mail
>> > notification, logging in, and answering the same old questions.  It
>> is
>> > quite boring.  You can see that if you look through the previous
>> > discussion, which you'll find was entirely sporadic; someone
>> > has a question, I answer, nothing else happens.  It could have been
>> > done in mail.  It costs so much memory and screen real-estate that I
>> > can't see myself staying connected.  I certainly don't want it
>> > promoted for Sugar Labs, but I'm willing to keep it 

[Sugar-devel] Mascot for sugar

[Srevin Saju]

Sugarlabs needs a mascot to welcome new users of the sugar desktop,
This can be an important part of outreaching sugar to daily desktop users.
One way of creating a mascot for sugar is to use a competition. The
benefits are two hold, one is the more people come to know of Sugarlabs and
their non-profit collective education systems. The other is, we are getting
a mascot personalized to sugar. Most open source companies have mascots
too. So its a subject to be brought to discussion, if anyone is interested
V/r


*SREVIN SAJU*
*https://srevinsaju.github.io *
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Proposal to move communication to other platform

[Bottersnike]

>Quassel core is a server that keeps the backlog.  I don't need my
>computer on, and I can view the backlog from any device.

Without being rude, most people don't have a spare server lying around they
can spin up an IRC backlog on, especially not people interested in reading
backlogged messages from *before* they joined the IRC for the first time.

On Wed, Mar 4, 2020 at 7:59 PM James Cameron  wrote:

> Thanks for your thoughts.
>
> Quassel core is a server that keeps the backlog.  I don't need my
> computer on, and I can view the backlog from any device.
>
> Yes, there are better onboarding experiences.
>
> However, if people want to talk with us, they'll know where to find
> us.  We're here to get the job done, not provide better experiences
> for developers.
>
> We do still get students who can use IRC, so I know it is not a
> significant hindrance.
>
> On Wed, Mar 04, 2020 at 07:46:10PM +, Bottersnike wrote:
> > I think one of the main issues with IRC is the onboarding experience, or
> rather
> > lack thereof. For new users, they're faced with an entirely blank
> screen, with
> > no trivial way to search for past questions, see if a topic has been
> brought up
> > before, or even just read through history to get a general idea of the
> way the
> > organization operates. Sure, there may be archives maintained, but for
> someone
> > who has just discovered SugarLabs and wants to contribute, that really
> isn't
> > going to be a viable solution, because it takes significant effort to
> hunt them
> > down and search through them. For established teams, this isn't much of
> an
> > issue, but it can make SugarLabs an incredibly daunting organization for
> young
> > students from, say GCI, or people looking around at different
> organizations for
> > GSoC.
> >
> > > I use Quassel, as it keeps backlog.
> >
> > Most clients keep a backlog, but only if your computer is on. That's not
> the
> > situation 24/7 for a lot of people.
> >
> > (Sorry for the double message, James. I accidentally used Reply not
> Reply All)
> >
> > On Wed, Mar 4, 2020 at 7:15 PM James Cameron <[1]qu...@laptop.org>
> wrote:
> >
> > Thanks for asking.
> >
> > For real-time presence messaging, please use IRC channel #sugar on
> > [2]freenode.net.  Your choice of client.  I use Quassel, as it keeps
> > backlog.
> >
> > For store and forward messaging, please use the mailing list.  Your
> > choice of client.
> >
> > You'll get a voice on choice of tools once you've been working with
> us
> > for a few months.  Until then we can't trust that you've assessed the
> > situation accurately.
> >
> > Gitter.im was yet another attempt to split our community into the
> > haves and the have-nots.  I'm almost ready to ditch my account there
> > because it has way less benefit than the cost.  Of receiving a mail
> > notification, logging in, and answering the same old questions.  It
> is
> > quite boring.  You can see that if you look through the previous
> > discussion, which you'll find was entirely sporadic; someone
> > has a question, I answer, nothing else happens.  It could have been
> > done in mail.  It costs so much memory and screen real-estate that I
> > can't see myself staying connected.  I certainly don't want it
> > promoted for Sugar Labs, but I'm willing to keep it available in case
> > it turns out to be useful for working with anyone who can't figure
> out
> > how to use IRC.  We must allow for the possibility that someone with
> a
> > disability has been given access to Gitter.im but not to IRC.  So a
> > matter of inclusiveness, but not emphasis.
> >
> > On Wed, Mar 04, 2020 at 08:03:31PM +0530, Prashant Sengar wrote:
> > > Hi,
> > >
> > > I am sure this request must have been raised earlier as well. I
> wanted to
> > ask
> > > if Sugar could create a communication channel on another platform
> such as
> > a
> > > discord server, Slack or Telegram instead of IRC to make
> communication
> > easier.
> > >
> > > The reason why others will be a better option:
> > > 1. The chats will be accessible even if I am offline for a while,
> unlike
> > IRC
> > > where I cannot see any earlier data.
> > > 2. IRC cannot be used on mobile devices, so it creates a barrier in
> > > communication. On the other hand, the other chat applications are
> > available on
> > > all platforms for everyone to use.
> > >
> > > I would like to request the team to please consider this request.
> If such
> > > request has been made earlier and denied due to some reasons, then
> I
> > would like
> > > to know them so that I can understand the reasons and work
> accordingly.
> > >
> > > Regards.
> > > Prashant Sengar
> >
> > > ___
> > > Sugar-devel mailing list
> > > [3]Sugar-devel@lists.sugarlabs.org
> > > 

Re: [Sugar-devel] Proposal to move communication to other platform

[James Cameron]

Thanks for your thoughts.

Quassel core is a server that keeps the backlog.  I don't need my
computer on, and I can view the backlog from any device.

Yes, there are better onboarding experiences.

However, if people want to talk with us, they'll know where to find
us.  We're here to get the job done, not provide better experiences
for developers.

We do still get students who can use IRC, so I know it is not a
significant hindrance.

On Wed, Mar 04, 2020 at 07:46:10PM +, Bottersnike wrote:
> I think one of the main issues with IRC is the onboarding experience, or 
> rather
> lack thereof. For new users, they're faced with an entirely blank screen, with
> no trivial way to search for past questions, see if a topic has been brought 
> up
> before, or even just read through history to get a general idea of the way the
> organization operates. Sure, there may be archives maintained, but for someone
> who has just discovered SugarLabs and wants to contribute, that really isn't
> going to be a viable solution, because it takes significant effort to hunt 
> them
> down and search through them. For established teams, this isn't much of an
> issue, but it can make SugarLabs an incredibly daunting organization for young
> students from, say GCI, or people looking around at different organizations 
> for
> GSoC.
> 
> > I use Quassel, as it keeps backlog.
> 
> Most clients keep a backlog, but only if your computer is on. That's not the
> situation 24/7 for a lot of people.
> 
> (Sorry for the double message, James. I accidentally used Reply not Reply All)
> 
> On Wed, Mar 4, 2020 at 7:15 PM James Cameron <[1]qu...@laptop.org> wrote:
> 
> Thanks for asking.
> 
> For real-time presence messaging, please use IRC channel #sugar on
> [2]freenode.net.  Your choice of client.  I use Quassel, as it keeps
> backlog.
> 
> For store and forward messaging, please use the mailing list.  Your
> choice of client.
> 
> You'll get a voice on choice of tools once you've been working with us
> for a few months.  Until then we can't trust that you've assessed the
> situation accurately.
> 
> Gitter.im was yet another attempt to split our community into the
> haves and the have-nots.  I'm almost ready to ditch my account there
> because it has way less benefit than the cost.  Of receiving a mail
> notification, logging in, and answering the same old questions.  It is
> quite boring.  You can see that if you look through the previous
> discussion, which you'll find was entirely sporadic; someone
> has a question, I answer, nothing else happens.  It could have been
> done in mail.  It costs so much memory and screen real-estate that I
> can't see myself staying connected.  I certainly don't want it
> promoted for Sugar Labs, but I'm willing to keep it available in case
> it turns out to be useful for working with anyone who can't figure out
> how to use IRC.  We must allow for the possibility that someone with a
> disability has been given access to Gitter.im but not to IRC.  So a
> matter of inclusiveness, but not emphasis.
> 
> On Wed, Mar 04, 2020 at 08:03:31PM +0530, Prashant Sengar wrote:
> > Hi,
> >
> > I am sure this request must have been raised earlier as well. I wanted 
> to
> ask
> > if Sugar could create a communication channel on another platform such 
> as
> a
> > discord server, Slack or Telegram instead of IRC to make communication
> easier.
> >
> > The reason why others will be a better option:
> > 1. The chats will be accessible even if I am offline for a while, unlike
> IRC
> > where I cannot see any earlier data.
> > 2. IRC cannot be used on mobile devices, so it creates a barrier in
> > communication. On the other hand, the other chat applications are
> available on
> > all platforms for everyone to use.
> >
> > I would like to request the team to please consider this request. If 
> such
> > request has been made earlier and denied due to some reasons, then I
> would like
> > to know them so that I can understand the reasons and work accordingly.
> >
> > Regards.
> > Prashant Sengar
> 
> > ___
> > Sugar-devel mailing list
> > [3]Sugar-devel@lists.sugarlabs.org
> > [4]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> --
> James Cameron
> [5]http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> [6]Sugar-devel@lists.sugarlabs.org
> [7]http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> References:
> 
> [1] mailto:qu...@laptop.org
> [2] http://freenode.net/
> [3] mailto:Sugar-devel@lists.sugarlabs.org
> [4] http://lists.sugarlabs.org/listinfo/sugar-devel
> [5] http://quozl.netrek.org/
> [6] mailto:Sugar-devel@lists.sugarlabs.org
> [7] http://lists.sugarlabs.org/listinfo/sugar-devel

-- 

Re: [Sugar-devel] Proposal to move communication to other platform

[Bottersnike]

With regards to chat.sugarlabs.org, the version of qwebirc it runs is 10
years out of date, and it has an SSL certificate that expired 4 years ago.
I really don't think there's any reason it should ever be recommended to
new users (over just using freenode) unless it receives a serious update.

On Wed, Mar 4, 2020 at 7:46 PM Bottersnike  wrote:

> I think one of the main issues with IRC is the onboarding experience, or
> rather lack thereof. For new users, they're faced with an entirely blank
> screen, with no trivial way to search for past questions, see if a topic
> has been brought up before, or even just read through history to get a
> general idea of the way the organization operates. Sure, there may be
> archives maintained, but for someone who has just discovered SugarLabs and
> wants to contribute, that really isn't going to be a viable solution,
> because it takes significant effort to hunt them down and search through
> them. For established teams, this isn't much of an issue, but it can make
> SugarLabs an incredibly daunting organization for young students from, say
> GCI, or people looking around at different organizations for GSoC.
>
> > I use Quassel, as it keeps backlog.
>
> Most clients keep a backlog, but only if your computer is on. That's not
> the situation 24/7 for a lot of people.
>
> (Sorry for the double message, James. I accidentally used Reply not Reply
> All)
>
> On Wed, Mar 4, 2020 at 7:15 PM James Cameron  wrote:
>
>> Thanks for asking.
>>
>> For real-time presence messaging, please use IRC channel #sugar on
>> freenode.net.  Your choice of client.  I use Quassel, as it keeps
>> backlog.
>>
>> For store and forward messaging, please use the mailing list.  Your
>> choice of client.
>>
>> You'll get a voice on choice of tools once you've been working with us
>> for a few months.  Until then we can't trust that you've assessed the
>> situation accurately.
>>
>> Gitter.im was yet another attempt to split our community into the
>> haves and the have-nots.  I'm almost ready to ditch my account there
>> because it has way less benefit than the cost.  Of receiving a mail
>> notification, logging in, and answering the same old questions.  It is
>> quite boring.  You can see that if you look through the previous
>> discussion, which you'll find was entirely sporadic; someone
>> has a question, I answer, nothing else happens.  It could have been
>> done in mail.  It costs so much memory and screen real-estate that I
>> can't see myself staying connected.  I certainly don't want it
>> promoted for Sugar Labs, but I'm willing to keep it available in case
>> it turns out to be useful for working with anyone who can't figure out
>> how to use IRC.  We must allow for the possibility that someone with a
>> disability has been given access to Gitter.im but not to IRC.  So a
>> matter of inclusiveness, but not emphasis.
>>
>> On Wed, Mar 04, 2020 at 08:03:31PM +0530, Prashant Sengar wrote:
>> > Hi,
>> >
>> > I am sure this request must have been raised earlier as well. I wanted
>> to ask
>> > if Sugar could create a communication channel on another platform such
>> as a
>> > discord server, Slack or Telegram instead of IRC to make communication
>> easier.
>> >
>> > The reason why others will be a better option:
>> > 1. The chats will be accessible even if I am offline for a while,
>> unlike IRC
>> > where I cannot see any earlier data.
>> > 2. IRC cannot be used on mobile devices, so it creates a barrier in
>> > communication. On the other hand, the other chat applications are
>> available on
>> > all platforms for everyone to use.
>> >
>> > I would like to request the team to please consider this request. If
>> such
>> > request has been made earlier and denied due to some reasons, then I
>> would like
>> > to know them so that I can understand the reasons and work accordingly.
>> >
>> > Regards.
>> > Prashant Sengar
>>
>> > ___
>> > Sugar-devel mailing list
>> > Sugar-devel@lists.sugarlabs.org
>> > http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>> --
>> James Cameron
>> http://quozl.netrek.org/
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Proposal to move communication to other platform

[Bottersnike]

I think one of the main issues with IRC is the onboarding experience, or
rather lack thereof. For new users, they're faced with an entirely blank
screen, with no trivial way to search for past questions, see if a topic
has been brought up before, or even just read through history to get a
general idea of the way the organization operates. Sure, there may be
archives maintained, but for someone who has just discovered SugarLabs and
wants to contribute, that really isn't going to be a viable solution,
because it takes significant effort to hunt them down and search through
them. For established teams, this isn't much of an issue, but it can make
SugarLabs an incredibly daunting organization for young students from, say
GCI, or people looking around at different organizations for GSoC.

> I use Quassel, as it keeps backlog.

Most clients keep a backlog, but only if your computer is on. That's not
the situation 24/7 for a lot of people.

(Sorry for the double message, James. I accidentally used Reply not Reply
All)

On Wed, Mar 4, 2020 at 7:15 PM James Cameron  wrote:

> Thanks for asking.
>
> For real-time presence messaging, please use IRC channel #sugar on
> freenode.net.  Your choice of client.  I use Quassel, as it keeps
> backlog.
>
> For store and forward messaging, please use the mailing list.  Your
> choice of client.
>
> You'll get a voice on choice of tools once you've been working with us
> for a few months.  Until then we can't trust that you've assessed the
> situation accurately.
>
> Gitter.im was yet another attempt to split our community into the
> haves and the have-nots.  I'm almost ready to ditch my account there
> because it has way less benefit than the cost.  Of receiving a mail
> notification, logging in, and answering the same old questions.  It is
> quite boring.  You can see that if you look through the previous
> discussion, which you'll find was entirely sporadic; someone
> has a question, I answer, nothing else happens.  It could have been
> done in mail.  It costs so much memory and screen real-estate that I
> can't see myself staying connected.  I certainly don't want it
> promoted for Sugar Labs, but I'm willing to keep it available in case
> it turns out to be useful for working with anyone who can't figure out
> how to use IRC.  We must allow for the possibility that someone with a
> disability has been given access to Gitter.im but not to IRC.  So a
> matter of inclusiveness, but not emphasis.
>
> On Wed, Mar 04, 2020 at 08:03:31PM +0530, Prashant Sengar wrote:
> > Hi,
> >
> > I am sure this request must have been raised earlier as well. I wanted
> to ask
> > if Sugar could create a communication channel on another platform such
> as a
> > discord server, Slack or Telegram instead of IRC to make communication
> easier.
> >
> > The reason why others will be a better option:
> > 1. The chats will be accessible even if I am offline for a while, unlike
> IRC
> > where I cannot see any earlier data.
> > 2. IRC cannot be used on mobile devices, so it creates a barrier in
> > communication. On the other hand, the other chat applications are
> available on
> > all platforms for everyone to use.
> >
> > I would like to request the team to please consider this request. If such
> > request has been made earlier and denied due to some reasons, then I
> would like
> > to know them so that I can understand the reasons and work accordingly.
> >
> > Regards.
> > Prashant Sengar
>
> > ___
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
> --
> James Cameron
> http://quozl.netrek.org/
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugar-devel Digest, Vol 137, Issue 6

[J T]

Sent from my Sprint Samsung Galaxy Note10+.



 Original message 
From: sugar-devel-requ...@lists.sugarlabs.org
Date: 3/4/20 12:00 PM (GMT-05:00)
To: sugar-devel@lists.sugarlabs.org
Subject: Sugar-devel Digest, Vol 137, Issue 6

Send Sugar-devel mailing list submissions to
sugar-devel@lists.sugarlabs.org

To subscribe or unsubscribe via the World Wide Web, visit

https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.sugarlabs.org%2Flistinfo%2Fsugar-develdata=02%7C01%7C%7C94535be827e74c56daf308d7c05d7ec9%7C84df9e7fe9f640afb435%7C1%7C0%7C637189380104419961sdata=X6RZMk3nEZEnOeChCWaXxUwRj7ekKP6X3BGHuwsBCNI%3Dreserved=0
or, via email, send a message with subject or body 'help' to
sugar-devel-requ...@lists.sugarlabs.org

You can reach the person managing the list at
sugar-devel-ow...@lists.sugarlabs.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Sugar-devel digest..."


Today's Topics:

   1. User Experience for keyboard shortcuts (Redo Button) (Ryan Van)
   2. Re: Music Blocks v3.0 is released. (Walter Bender)
   3. Proposal to move communication to other platform (Prashant Sengar)


--

Message: 1
Date: Tue, 3 Mar 2020 22:30:16 -0800
From: Ryan Van 
To: sugar-devel@lists.sugarlabs.org
Subject: [Sugar-devel] User Experience for keyboard shortcuts (Redo
Button)
Message-ID:

Content-Type: text/plain; charset="utf-8"

As of right now there exists a redo button without keyboard shortcuts. What
are your opinions on whether or not Ctrl +Shift+Z or Ctrl+Y would be more
appropriate (the logic to have both might be too complex and not worth the
time to implement)?

Thanks!
-- next part --
An HTML attachment was scrubbed...
URL: 


--

Message: 2
Date: Wed, 4 Mar 2020 07:25:58 -0500
From: Walter Bender 
To: James Cameron 
Cc: Sugar-dev Devel 
Subject: Re: [Sugar-devel] Music Blocks v3.0 is released.
Message-ID:

Content-Type: text/plain; charset="utf-8"

On Tue, Mar 3, 2020 at 8:52 PM Walter Bender 
wrote:

> Sugar yes. The new version of Browse should work nicely.
> Sugarizer, no. Lionel has said it is too large.
>
> On Tue, Mar 3, 2020 at 7:53 PM James Cameron  wrote:
>
>> Are there any plans to add Music Blocks to Sugarizer or Sugar?
>>
>
At James: What is the recommended approach to embedding inside Browse these
days?
In the past, I simply modified the HOME_PAGE_GCONF_KEY to use a copy of
musicblocks included in the bundle. Do you recommend removing some
unrelated Browse functionality, such as the search bar? Do you think it is
worth modifying Browse itself to make it easier to do this sort of
embedding?

regards.

-walter

>
>> On Tue, Mar 03, 2020 at 07:33:46PM -0500, Walter Bender wrote:
>> > The release reflects the contributions made during Google Code-in
>> 2019-2020. It
>> > is being designated as a major release since there are numerous changes
>> to the
>> > user experience (e.g., Widget UX) and many underlying structural
>> changes (e.g.,
>> > the new Block API and storage mechanism) that impact developers. An
>> overhaul of
>> > the graphics update mechanism has lead to a major reduction in CPU
>> usage. As
>> > far as I know, there is only one "incompatibility" with previous
>> versions; it
>> > is in regard to synchronization: there are some projects that worked
>> previously
>> > that may now require the use of either the Sync block or the No-clock
>> block.
>> > (Details are outlined in the release notes.)
>> >
>> > A tip of the hat to some of the GCI participants who worked so hard to
>> make
>> > this release possible: Bottersnike, AndreaGon, Pidddgy and
>> Nepaltechguy2. They
>> > not only contributed code, but also insights into the design and
>> > implementation. Also, thanks to the community members who provided them
>> with
>> > code reviews and feedback (notably @eohomegrownapps, @fakela, and
>> @pikurasa).
>> > It is also important to acknowledge some of our users, Teddy Dildine
>> and Henry
>> > Rico, who have been inspiring much of the recent developments and bug
>> fixes.
>> > Look for some of their work on the Planet. Karin Kinoshita at Gakken
>> has also
>> > done testing and translation work.
>> >
>> > [1] 
>> > 

Re: [Sugar-devel] Proposal to move communication to other platform

[James Cameron]

Thanks for asking.

For real-time presence messaging, please use IRC channel #sugar on
freenode.net.  Your choice of client.  I use Quassel, as it keeps
backlog.

For store and forward messaging, please use the mailing list.  Your
choice of client.

You'll get a voice on choice of tools once you've been working with us
for a few months.  Until then we can't trust that you've assessed the
situation accurately.

Gitter.im was yet another attempt to split our community into the
haves and the have-nots.  I'm almost ready to ditch my account there
because it has way less benefit than the cost.  Of receiving a mail
notification, logging in, and answering the same old questions.  It is
quite boring.  You can see that if you look through the previous
discussion, which you'll find was entirely sporadic; someone
has a question, I answer, nothing else happens.  It could have been
done in mail.  It costs so much memory and screen real-estate that I
can't see myself staying connected.  I certainly don't want it
promoted for Sugar Labs, but I'm willing to keep it available in case
it turns out to be useful for working with anyone who can't figure out
how to use IRC.  We must allow for the possibility that someone with a
disability has been given access to Gitter.im but not to IRC.  So a
matter of inclusiveness, but not emphasis.

On Wed, Mar 04, 2020 at 08:03:31PM +0530, Prashant Sengar wrote:
> Hi,
> 
> I am sure this request must have been raised earlier as well. I wanted to ask
> if Sugar could create a communication channel on another platform such as a
> discord server, Slack or Telegram instead of IRC to make communication easier.
> 
> The reason why others will be a better option:
> 1. The chats will be accessible even if I am offline for a while, unlike IRC
> where I cannot see any earlier data.
> 2. IRC cannot be used on mobile devices, so it creates a barrier in
> communication. On the other hand, the other chat applications are available on
> all platforms for everyone to use.
> 
> I would like to request the team to please consider this request. If such
> request has been made earlier and denied due to some reasons, then I would 
> like
> to know them so that I can understand the reasons and work accordingly.
> 
> Regards.
> Prashant Sengar

> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel


-- 
James Cameron
http://quozl.netrek.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Proposal to move communication to other platform

[Prashant Sengar]

Hi Alex,

Yes I have used IRC before and I still don't really like it. I have tried
and used multiple IRC chat apps on my Android device and none of them
worked stably. I completely understand your reasons of not using other
platforms and I had read the few reasons mentioned in the docs.

As per suggestions, I will keep trying to learn more about IRC and get more
familiar with it.

Thanks for your response.

Prashant Sengar


On Wed, Mar 4, 2020, 11:37 PM Alex Perez  wrote:

> Prashant,
>
> We also offer our own Sugar Labs specific IRC chat gateway, at
> http://chat.sugarlabs.org:9090/
>
> I'd like to understand more fully why you believe IRC is hard for you to
> use. Is it hard because you've never used it before? Is it hard because you
> have no familiarity with it? IRC can absolutely be used on mobile devices,
> and this basic misunderstanding shows me that you're not particularly
> familiar with some basic IRC facts, nor have you bothered to open your
> mobile phone up, go to the app store, and type "IRC" in to the search
> field. Which mobile platform are you using? Android? iOS? If you tell us,
> we can recommend some clients for you.
>
> The issue of loss-of-state when you're disconnected from IRC is a known
> problem for 25+ years, and many ways to address it have been developed over
> that period of time.  There are IRC bouncers, web-based IRC clients, and
> all sorts of other solutions to these problems, if you can be bothered to
> search for them, instead of assuming that no solution exists, which is
> sorta what seems to have happened here.
>
> There are several reasons why we don't use Slack, Discord, or other
> proprietary messaging systems, which I'm not going to get into the details
> of here, but since they are corporate owned-and-operated pieces of
> infrastructure, they may or may not exist in the future.
>
> The primary problem with using Gitter is that it requires you to have a
> GitHub account, and has no other authentication mechanism. Developers are
> not the only people we care about, and IRC is accessible to all, and is
> fundamentally democratic.
>
> Prashant Sengar 
> March 4, 2020 at 6:33 AM
> Hi,
>
> I am sure this request must have been raised earlier as well. I wanted to
> ask if Sugar could create a communication channel on another platform such
> as a discord server, Slack or Telegram instead of IRC to make communication
> easier.
>
> The reason why others will be a better option:
> 1. The chats will be accessible even if I am offline for a while, unlike
> IRC where I cannot see any earlier data.
> 2. IRC cannot be used on mobile devices, so it creates a barrier in
> communication. On the other hand, the other chat applications are available
> on all platforms for everyone to use.
>
> I would like to request the team to please consider this request. If such
> request has been made earlier and denied due to some reasons, then I would
> like to know them so that I can understand the reasons and work accordingly.
>
> Regards.
> Prashant Sengar
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Proposal to move communication to other platform

[D. Joe]

Please consider also using the freenode Matrix bridge to the IRC channels, 
which gives a lot of the advantages people seek from the locked-in, 
single-vendor, centralized, proprietary services.

Mozilla has very recently gone through the process of re-evaluating their needs 
in this regard and decided to use Matrix entirely.

That gitter is being used is a good demonstration of the fact that this project 
isn't really in a position to decide what people use. People decide that on 
their own and we do the best with it that we can. 

For example, I'll acknowledge that our Gitter users have established it as yet 
another glinting shard on the great fractured disco ball of haphazardly 
connected sites and services and projects that is Sugarlabs.

The Mozilla and Gitter developments are the recent updates, but beyond that I'm 
not going to repeat myself, but rather refer back to previous iterations of 
this conversation through this link and the discussion before it to which it, 
in turn, also refers:

http://lists.sugarlabs.org/archive/sugar-devel/2018-February/055064.html

If a Gitter-IRC bridge has been stood up and is being maintained by anyone, 
please let me know. 

-- 
Joe


On Wed, Mar 04, 2020 at 11:00:00PM +0530, Prashant Sengar wrote:
> Thanks a log for your response. I completely understand the transparency
> maintained by sugar and value it. I did not know about the gitter chat room as
> I didn't find it in the wiki. I will be happy to add it in the wiki if it 
> isn't
> really there and I did not make a mistake.
> 
> 
> Thanks and regards,
> Prashant Sengar
>  
> On Wed, Mar 4, 2020, 10:45 PM Chihurumnaya Ibiam <
> ibiamchihurumn...@sugarlabs.org> wrote:
> 
> Hi Prashant,
> 
> 1. We have a gitter chat room which you can use, James is quite active
> there so he'll see your messages if you sent any.
> 2. IRC can be used on android devices and they're various clients, I use
> androirc you can check it out.
> 
> We prefer communication be done on the mailing list for transparency as a
> lot of people are subscribed to it and not everyone is on other platforms.
> 
> On Wed, Mar 4, 2020 at 3:33 PM Prashant Sengar 
> wrote:
> 
> Hi,
> 
> I am sure this request must have been raised earlier as well. I wanted
> to ask if Sugar could create a communication channel on another
> platform such as a discord server, Slack or Telegram instead of IRC to
> make communication easier.
> 
> The reason why others will be a better option:
> 1. The chats will be accessible even if I am offline for a while,
> unlike IRC where I cannot see any earlier data.
> 2. IRC cannot be used on mobile devices, so it creates a barrier in
> communication. On the other hand, the other chat applications are
> available on all platforms for everyone to use.
> 
> I would like to request the team to please consider this request. If
> such request has been made earlier and denied due to some reasons, 
> then
> I would like to know them so that I can understand the reasons and 
> work
> accordingly.
> 
> Regards.
> Prashant Sengar
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
> 

> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel


-- 
-- 
Joe   On ceding power to tech companies: http://xkcd.com/1118/
man screen | grep -A2 weird
  A weird imagination is most useful to gain full advantage of
  all the features.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Proposal to move communication to other platform

[Alex Perez]

Srevin,

Srevin Saju 
March 4, 2020 at 10:07 AM
I agree to Prashant. To me Slack seems to be a viable option, and 
indeed popular too. But unfortunately due to historical reasons, we 
might not move to another platform. Nevertheless, it might be of 
interest to other developers in the community
We will not be moving our real-time communication mechanism to Slack, or 
any other proprietary chat platform. See my other e-mail for a bit more 
of an explanation as to why, or, if you've got 20 minutes, please read 
this article: 
https://sneak.berlin/20200220/discord-is-not-an-acceptable-choice-for-free-software-projects/


I use slack daily for communications with work colleagues, and don't 
hate it, though I wish their stand-alone clients didn't use a shitload 
of RAM (they're Electron-based browser apps)
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Proposal to move communication to other platform

[Alex Perez]

Prashant,

We also offer our own Sugar Labs specific IRC chat gateway, at 
http://chat.sugarlabs.org:9090/


I'd like to understand more fully why you believe IRC is hard for you to 
use. Is it hard because you've never used it before? Is it hard because 
you have no familiarity with it? IRC can absolutely be used on mobile 
devices, and this basic misunderstanding shows me that you're not 
particularly familiar with some basic IRC facts, nor have you bothered 
to open your mobile phone up, go to the app store, and type "IRC" in to 
the search field. Which mobile platform are you using? Android? iOS? If 
you tell us, we can recommend some clients for you.


The issue of loss-of-state when you're disconnected from IRC is a known 
problem for 25+ years, and many ways to address it have been developed 
over that period of time.  There are IRC bouncers, web-based IRC 
clients, and all sorts of other solutions to these problems, if you can 
be bothered to search for them, instead of assuming that no solution 
exists, which is sorta what seems to have happened here.


There are several reasons why we don't use Slack, Discord, or other 
proprietary messaging systems, which I'm not going to get into the 
details of here, but since they are corporate owned-and-operated pieces 
of infrastructure, they may or may not exist in the future.


The primary problem with using Gitter is that it requires you to have a 
GitHub account, and has no other authentication mechanism. Developers 
are not the only people we care about, and IRC is accessible to all, and 
is fundamentally democratic.



Prashant Sengar 
March 4, 2020 at 6:33 AM
Hi,

I am sure this request must have been raised earlier as well. I wanted 
to ask if Sugar could create a communication channel on another 
platform such as a discord server, Slack or Telegram instead of IRC to 
make communication easier.


The reason why others will be a better option:
1. The chats will be accessible even if I am offline for a while, 
unlike IRC where I cannot see any earlier data.
2. IRC cannot be used on mobile devices, so it creates a barrier in 
communication. On the other hand, the other chat applications are 
available on all platforms for everyone to use.


I would like to request the team to please consider this request. If 
such request has been made earlier and denied due to some reasons, 
then I would like to know them so that I can understand the reasons 
and work accordingly.


Regards.
Prashant Sengar


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Proposal to move communication to other platform

[Srevin Saju]

I agree to Prashant. To me Slack seems to be a viable option, and indeed
popular too. But unfortunately due to historical reasons, we might not move
to another platform. Nevertheless, it might be of interest to other
developers in the community

I am sure this request must have been raised earlier as well. I wanted to
> ask if Sugar could create a communication channel on another platform such
> as a discord server, Slack or Telegram instead of IRC to make communication
> easier.
>
> The reason why others will be a better option:
> 1. The chats will be accessible even if I am offline for a while, unlike
> IRC where I cannot see any earlier data.
> 2. IRC cannot be used on mobile devices, so it creates a barrier in
> communication. On the other hand, the other chat applications are available
> on all platforms for everyone to use.
>
> I would like to request the team to please consider this request. If such
> request has been made earlier and denied due to some reasons, then I would
> like to know them so that I can understand the reasons and work
> accordingly.
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Proposal to move communication to other platform

[Prashant Sengar]

Thanks a log for your response. I completely understand the transparency
maintained by sugar and value it. I did not know about the gitter chat room
as I didn't find it in the wiki. I will be happy to add it in the wiki if
it isn't really there and I did not make a mistake.


Thanks and regards,
Prashant Sengar

On Wed, Mar 4, 2020, 10:45 PM Chihurumnaya Ibiam <
ibiamchihurumn...@sugarlabs.org> wrote:

> Hi Prashant,
>
> 1. We have a gitter chat room 
> which you can use, James is quite active there so he'll see your messages
> if you sent any.
> 2. IRC can be used on android devices and they're various clients, I use
> androirc
>  you
> can check it out.
>
> We prefer communication be done on the mailing list for transparency as a
> lot of people are subscribed to it and not everyone is on other platforms.
>
> On Wed, Mar 4, 2020 at 3:33 PM Prashant Sengar 
> wrote:
>
>> Hi,
>>
>> I am sure this request must have been raised earlier as well. I wanted to
>> ask if Sugar could create a communication channel on another platform such
>> as a discord server, Slack or Telegram instead of IRC to make communication
>> easier.
>>
>> The reason why others will be a better option:
>> 1. The chats will be accessible even if I am offline for a while, unlike
>> IRC where I cannot see any earlier data.
>> 2. IRC cannot be used on mobile devices, so it creates a barrier in
>> communication. On the other hand, the other chat applications are available
>> on all platforms for everyone to use.
>>
>> I would like to request the team to please consider this request. If such
>> request has been made earlier and denied due to some reasons, then I would
>> like to know them so that I can understand the reasons and work accordingly.
>>
>> Regards.
>> Prashant Sengar
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Proposal to move communication to other platform

[Chihurumnaya Ibiam]

Hi Prashant,

1. We have a gitter chat room 
which you can use, James is quite active there so he'll see your messages
if you sent any.
2. IRC can be used on android devices and they're various clients, I use
androirc
 you
can check it out.

We prefer communication be done on the mailing list for transparency as a
lot of people are subscribed to it and not everyone is on other platforms.

On Wed, Mar 4, 2020 at 3:33 PM Prashant Sengar 
wrote:

> Hi,
>
> I am sure this request must have been raised earlier as well. I wanted to
> ask if Sugar could create a communication channel on another platform such
> as a discord server, Slack or Telegram instead of IRC to make communication
> easier.
>
> The reason why others will be a better option:
> 1. The chats will be accessible even if I am offline for a while, unlike
> IRC where I cannot see any earlier data.
> 2. IRC cannot be used on mobile devices, so it creates a barrier in
> communication. On the other hand, the other chat applications are available
> on all platforms for everyone to use.
>
> I would like to request the team to please consider this request. If such
> request has been made earlier and denied due to some reasons, then I would
> like to know them so that I can understand the reasons and work accordingly.
>
> Regards.
> Prashant Sengar
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Proposal to move communication to other platform

[Prashant Sengar]

Hi,

I am sure this request must have been raised earlier as well. I wanted to
ask if Sugar could create a communication channel on another platform such
as a discord server, Slack or Telegram instead of IRC to make communication
easier.

The reason why others will be a better option:
1. The chats will be accessible even if I am offline for a while, unlike
IRC where I cannot see any earlier data.
2. IRC cannot be used on mobile devices, so it creates a barrier in
communication. On the other hand, the other chat applications are available
on all platforms for everyone to use.

I would like to request the team to please consider this request. If such
request has been made earlier and denied due to some reasons, then I would
like to know them so that I can understand the reasons and work accordingly.

Regards.
Prashant Sengar
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Music Blocks v3.0 is released.

[Walter Bender]

On Tue, Mar 3, 2020 at 8:52 PM Walter Bender 
wrote:

> Sugar yes. The new version of Browse should work nicely.
> Sugarizer, no. Lionel has said it is too large.
>
> On Tue, Mar 3, 2020 at 7:53 PM James Cameron  wrote:
>
>> Are there any plans to add Music Blocks to Sugarizer or Sugar?
>>
>
At James: What is the recommended approach to embedding inside Browse these
days?
In the past, I simply modified the HOME_PAGE_GCONF_KEY to use a copy of
musicblocks included in the bundle. Do you recommend removing some
unrelated Browse functionality, such as the search bar? Do you think it is
worth modifying Browse itself to make it easier to do this sort of
embedding?

regards.

-walter

>
>> On Tue, Mar 03, 2020 at 07:33:46PM -0500, Walter Bender wrote:
>> > The release reflects the contributions made during Google Code-in
>> 2019-2020. It
>> > is being designated as a major release since there are numerous changes
>> to the
>> > user experience (e.g., Widget UX) and many underlying structural
>> changes (e.g.,
>> > the new Block API and storage mechanism) that impact developers. An
>> overhaul of
>> > the graphics update mechanism has lead to a major reduction in CPU
>> usage. As
>> > far as I know, there is only one "incompatibility" with previous
>> versions; it
>> > is in regard to synchronization: there are some projects that worked
>> previously
>> > that may now require the use of either the Sync block or the No-clock
>> block.
>> > (Details are outlined in the release notes.)
>> >
>> > A tip of the hat to some of the GCI participants who worked so hard to
>> make
>> > this release possible: Bottersnike, AndreaGon, Pidddgy and
>> Nepaltechguy2. They
>> > not only contributed code, but also insights into the design and
>> > implementation. Also, thanks to the community members who provided them
>> with
>> > code reviews and feedback (notably @eohomegrownapps, @fakela, and
>> @pikurasa).
>> > It is also important to acknowledge some of our users, Teddy Dildine
>> and Henry
>> > Rico, who have been inspiring much of the recent developments and bug
>> fixes.
>> > Look for some of their work on the Planet. Karin Kinoshita at Gakken
>> has also
>> > done testing and translation work.
>> >
>> > [1] [1]https://github.com/sugarlabs/musicblocks/releases/tag/v3.0
>> >
>> > -walter
>> >
>> > --
>> > Walter Bender
>> > Sugar Labs
>> > [2]http://www.sugarlabs.org
>> > [3]
>> >
>> > References:
>> >
>> > [1] https://github.com/sugarlabs/musicblocks/releases/tag/v3.0
>> > [2] http://www.sugarlabs.org/
>> > [3] http://www.sugarlabs.org/
>>
>> > ___
>> > Sugar-devel mailing list
>> > Sugar-devel@lists.sugarlabs.org
>> > http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>>
>> --
>> James Cameron
>> http://quozl.netrek.org/
>> ___
>> Sugar-devel mailing list
>> Sugar-devel@lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>>
>
>
> --
> Walter Bender
> Sugar Labs
> http://www.sugarlabs.org
> 
>


-- 
Walter Bender
Sugar Labs
http://www.sugarlabs.org

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel