Re: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up!
On 1/27/21 8:30 AM, James Cameron wrote:
On Wed, Jan 27, 2021 at 08:04:41AM +0300, Srevin Saju wrote:
reply inline.
me too.
On 1/27/21 3:09 AM, James Cameron wrote:
On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote:
And now, (Thanks bernie_!), we can use
https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting
sugar's microformat update system as mentioned below:
* support Sugar's microformat software upgrade feature in My
Settings, (Sugar 0.116 is configured
in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater
in|src/jarabe/model/update/aslo.py|which reaches out to a PHP
script|update-aslo.php|, and will instead be configured to
use|src/jarabe/model/update/microformat.py|),
I've reviewed the output of update-aslo.php briefly. For Implode it
gives a minVersion of 0.116 and a maxVersion of 0.117. How does an
activity author specify these values?
Right now, its hardcoded into
https://github.com/sugarlabs/aslo-v4/blob/a1ac5dac02030f38dca863eea3c70b978ebd8ad1/aslo4/rdf/rdf.py#L55.
Let me know what would be the best implementation.
I'm in doubt. I had previously asked that we not be required to
change activity metadata, yet activity metadata is a great place to
put this. What do you think?
Agreed. That would reduce a lot of complexities. Its ideal to extract
every information from the bundle itself. Also, it would be nice to keep
an `activityInfoVersion` which would define the specification of the
activity.info, so that, we can run a migrate function to update old
activity.info to new activity.info and vice-versa.
Perhaps each new release should be interpreted as being for the
current version, if such metadata is missing.
Agreed, that would do.
https://developer.sugarlabs.org/sugar3/sugar3.bundle.html is our
activity metadata documentation.
https://wiki.sugarlabs.org/go/Development_Team/Almanac/Activity_Bundles
is also documentation.
In the history of edits to the Wiki, we had a host_version metadata
item to specify the version of Sugar, but it was not implemented.
So perhaps min_sugar_version and max_sugar_version are needed.
Yes.
On the other hand, aslo.py does _not check_ the minVersion and
maxVersion values.
For the time being, you can set them both to 0.118.
With aslo.py not checking the value, it doesn't yet matter.
Updated, as of e071af059cdbac9bb903b9543beec89033f35cd6 commit on
sugarlabs/aslo-v4
http://www.w3.org/1999/02/22-rdf-syntax-ns#;
xmlns:em="http://www.mozilla.org/2004/em-rdf#;>
20.1.1~quozl
{9e5ecf85-6bb9-4403-bae8-d6865f19677b}
0.116
0.117
https://v4.activities.sugarlabs.org/bundles/Implode-20.1.1~quozl.xo
198
https://v4.activities.sugarlabs.org/app/com.jotaro.ImplodeActivity.html
sha256:18be1821a7f2e6bfb9de59b11d3ae18b92271b354bb8b38f8a06e9d99a37a6fe
On 1/21/21 10:03 AM, Srevin Saju wrote:
Right. I will configure ASLO-v4 to email sugar-devel@ with release
notifications.
Thanks to all developers, mentors who helped me out with this. Had a
great experience working with it!!!
On 1/21/21 10:00 AM, James Cameron wrote:
Thanks, great work. Merged 204.
I've also updated Browse.
https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac
I would prefer new version notifications to go to
sugar-devel@lists.sugarlabs.org, as that's one place we've seen them
previously. a...@lists.sugarlabs.org was for handling by library
editors, but we don't have any active, and we don't have the same
process with v4.
On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote:
G'day!
ASLO-v4 is finally up at https://v4.activities.sugarlabs.org!
... with only
a few more minor tidying up, ASLO-v4 will be ready for production.
Activity maintainers can now push their bundles to ASLO-v4 by
following the
instructions on
https://wiki.sugarlabs.org/go/Service/activities4 as well
as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204.
Please feel free to reach out, so that I can improve the existing
documentation, or anything you think is too complex.
Next steps:
* Connect services/update-aslo.php and deploy a flask server (I am
trying to get a hold of some more good apache knowledge)
* Sending "new version detected" emails to a...@lists.sugarlabs.org,
or should we create a new mailing list?
--
Srevin Saju
https://srevinsaju.me
pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju)
sub RSA 4096/14479587 2020-05-19
___
Systems mailing list
syst...@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/systems
___
Sugar-devel mailing list
Re: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up!
On Wed, Jan 27, 2021 at 08:04:41AM +0300, Srevin Saju wrote:
> reply inline.
me too.
>
> On 1/27/21 3:09 AM, James Cameron wrote:
> > On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote:
> > > And now, (Thanks bernie_!), we can use
> > > https://v4.activities.sugarlabs.org/services/update-aslo.php for
> > > supporting
> > > sugar's microformat update system as mentioned below:
> > >
> > > >* support Sugar's microformat software upgrade feature in My
> > > > Settings, (Sugar 0.116 is configured
> > > > in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater
> > > > in|src/jarabe/model/update/aslo.py|which reaches out to a PHP
> > > > script|update-aslo.php|, and will instead be configured to
> > > > use|src/jarabe/model/update/microformat.py|),
> > I've reviewed the output of update-aslo.php briefly. For Implode it
> > gives a minVersion of 0.116 and a maxVersion of 0.117. How does an
> > activity author specify these values?
>
> Right now, its hardcoded into
> https://github.com/sugarlabs/aslo-v4/blob/a1ac5dac02030f38dca863eea3c70b978ebd8ad1/aslo4/rdf/rdf.py#L55.
> Let me know what would be the best implementation.
I'm in doubt. I had previously asked that we not be required to
change activity metadata, yet activity metadata is a great place to
put this. What do you think?
Perhaps each new release should be interpreted as being for the
current version, if such metadata is missing.
https://developer.sugarlabs.org/sugar3/sugar3.bundle.html is our
activity metadata documentation.
https://wiki.sugarlabs.org/go/Development_Team/Almanac/Activity_Bundles
is also documentation.
In the history of edits to the Wiki, we had a host_version metadata
item to specify the version of Sugar, but it was not implemented.
So perhaps min_sugar_version and max_sugar_version are needed.
On the other hand, aslo.py does _not check_ the minVersion and
maxVersion values.
For the time being, you can set them both to 0.118.
With aslo.py not checking the value, it doesn't yet matter.
>
> >
> > http://www.w3.org/1999/02/22-rdf-syntax-ns#;
> > xmlns:em="http://www.mozilla.org/2004/em-rdf#;>
> > > about="urn:mozilla:extension:com.jotaro.ImplodeActivity">
> >
> >
> > > resource="urn:mozilla:extension:com.jotaro.ImplodeActivity:20.1.1~quozl"/>
> >
> >
> >
> > > about="urn:mozilla:extension:com.jotaro.ImplodeActivity:20.1.1~quozl">
> > 20.1.1~quozl
> >
> >
> > {9e5ecf85-6bb9-4403-bae8-d6865f19677b}
> > 0.116
> > 0.117
> >
> > https://v4.activities.sugarlabs.org/bundles/Implode-20.1.1~quozl.xo
> > 198
> >
> > https://v4.activities.sugarlabs.org/app/com.jotaro.ImplodeActivity.html
> >
> > sha256:18be1821a7f2e6bfb9de59b11d3ae18b92271b354bb8b38f8a06e9d99a37a6fe
> >
> >
> >
> >
> >
> >
> > > On 1/21/21 10:03 AM, Srevin Saju wrote:
> > > > Right. I will configure ASLO-v4 to email sugar-devel@ with release
> > > > notifications.
> > > > Thanks to all developers, mentors who helped me out with this. Had a
> > > > great experience working with it!!!
> > > >
> > > > On 1/21/21 10:00 AM, James Cameron wrote:
> > > > > Thanks, great work. Merged 204.
> > > > >
> > > > > I've also updated Browse.
> > > > >
> > > > > https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac
> > > > >
> > > > >
> > > > > I would prefer new version notifications to go to
> > > > > sugar-devel@lists.sugarlabs.org, as that's one place we've seen them
> > > > > previously. a...@lists.sugarlabs.org was for handling by library
> > > > > editors, but we don't have any active, and we don't have the same
> > > > > process with v4.
> > > > >
> > > > > On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote:
> > > > > > G'day!
> > > > > >
> > > > > > ASLO-v4 is finally up at https://v4.activities.sugarlabs.org!
> > > > > > ... with only
> > > > > > a few more minor tidying up, ASLO-v4 will be ready for production.
> > > > > >
> > > > > > Activity maintainers can now push their bundles to ASLO-v4 by
> > > > > > following the
> > > > > > instructions on
> > > > > > https://wiki.sugarlabs.org/go/Service/activities4 as well
> > > > > > as, that mentioned in
> > > > > > https://github.com/sugarlabs/sugar-docs/pull/204.
> > > > > > Please feel free to reach out, so that I can improve the existing
> > > > > > documentation, or anything you think is too complex.
> > > > > >
> > > > > > Next steps:
> > > > > >
> > > > > > * Connect services/update-aslo.php and deploy a flask server (I
> > > > > > am
> > > > > > trying to get a hold of some more good apache knowledge)
> > > > > > * Sending "new version detected" emails to
> > > > > > a...@lists.sugarlabs.org,
> > > > > > or should we create a new
Re: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up!
reply inline.
On 1/27/21 3:09 AM, James Cameron wrote:
On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote:
And now, (Thanks bernie_!), we can use
https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting
sugar's microformat update system as mentioned below:
* support Sugar's microformat software upgrade feature in My
Settings, (Sugar 0.116 is configured
in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater
in|src/jarabe/model/update/aslo.py|which reaches out to a PHP
script|update-aslo.php|, and will instead be configured to
use|src/jarabe/model/update/microformat.py|),
I've reviewed the output of update-aslo.php briefly. For Implode it
gives a minVersion of 0.116 and a maxVersion of 0.117. How does an
activity author specify these values?
Right now, its hardcoded into
https://github.com/sugarlabs/aslo-v4/blob/a1ac5dac02030f38dca863eea3c70b978ebd8ad1/aslo4/rdf/rdf.py#L55.
Let me know what would be the best implementation.
http://www.w3.org/1999/02/22-rdf-syntax-ns#;
xmlns:em="http://www.mozilla.org/2004/em-rdf#;>
20.1.1~quozl
{9e5ecf85-6bb9-4403-bae8-d6865f19677b}
0.116
0.117
https://v4.activities.sugarlabs.org/bundles/Implode-20.1.1~quozl.xo
198
https://v4.activities.sugarlabs.org/app/com.jotaro.ImplodeActivity.html
sha256:18be1821a7f2e6bfb9de59b11d3ae18b92271b354bb8b38f8a06e9d99a37a6fe
On 1/21/21 10:03 AM, Srevin Saju wrote:
Right. I will configure ASLO-v4 to email sugar-devel@ with release
notifications.
Thanks to all developers, mentors who helped me out with this. Had a
great experience working with it!!!
On 1/21/21 10:00 AM, James Cameron wrote:
Thanks, great work. Merged 204.
I've also updated Browse.
https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac
I would prefer new version notifications to go to
sugar-devel@lists.sugarlabs.org, as that's one place we've seen them
previously. a...@lists.sugarlabs.org was for handling by library
editors, but we don't have any active, and we don't have the same
process with v4.
On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote:
G'day!
ASLO-v4 is finally up at https://v4.activities.sugarlabs.org!
... with only
a few more minor tidying up, ASLO-v4 will be ready for production.
Activity maintainers can now push their bundles to ASLO-v4 by
following the
instructions on
https://wiki.sugarlabs.org/go/Service/activities4 as well
as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204.
Please feel free to reach out, so that I can improve the existing
documentation, or anything you think is too complex.
Next steps:
* Connect services/update-aslo.php and deploy a flask server (I am
trying to get a hold of some more good apache knowledge)
* Sending "new version detected" emails to a...@lists.sugarlabs.org,
or should we create a new mailing list?
--
Srevin Saju
https://srevinsaju.me
pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju)
sub RSA 4096/14479587 2020-05-19
___
Systems mailing list
syst...@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/systems
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
Srevin Saju
https://srevinsaju.me
pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju)
sub RSA 4096/14479587 2020-05-19
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
Srevin Saju
https://srevinsaju.me
On 1/27/21 3:09 AM, James Cameron wrote:
On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote:
And now, (Thanks bernie_!), we can use
https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting
sugar's microformat update system as mentioned below:
* support Sugar's microformat software upgrade feature in My
Settings, (Sugar 0.116 is configured
in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater
in|src/jarabe/model/update/aslo.py|which reaches out to a PHP
script|update-aslo.php|, and will instead be configured to
use|src/jarabe/model/update/microformat.py|),
I've reviewed the output of update-aslo.php briefly. For Implode it
gives a minVersion of 0.116 and a maxVersion of 0.117. How does an
activity author specify these values?
http://www.w3.org/1999/02/22-rdf-syntax-ns#;
xmlns:em="http://www.mozilla.org/2004/em-rdf#;>
20.1.1~quozl
Re: [Sugar-devel] Spectrum
yes, its a nice software. Another one is https://rocket.chat/ On 1/27/21 2:49 AM, James Cameron wrote: I was introduced to https://spectrum.chat/ while at https://linux.conf.au/ for working with the open hardware miniconference track. Spectrum is open source. https://github.com/withspectrum -- Srevin Saju https://srevinsaju.me OpenPGP_0x1007816766D390D7.asc Description: application/pgp-keys OpenPGP_signature Description: OpenPGP digital signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up!
On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote:
> And now, (Thanks bernie_!), we can use
> https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting
> sugar's microformat update system as mentioned below:
>
> > * support Sugar's microformat software upgrade feature in My
> > Settings, (Sugar 0.116 is configured
> > in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater
> > in|src/jarabe/model/update/aslo.py|which reaches out to a PHP
> > script|update-aslo.php|, and will instead be configured to
> > use|src/jarabe/model/update/microformat.py|),
I've reviewed the output of update-aslo.php briefly. For Implode it
gives a minVersion of 0.116 and a maxVersion of 0.117. How does an
activity author specify these values?
http://www.w3.org/1999/02/22-rdf-syntax-ns#;
xmlns:em="http://www.mozilla.org/2004/em-rdf#;>
20.1.1~quozl
{9e5ecf85-6bb9-4403-bae8-d6865f19677b}
0.116
0.117
https://v4.activities.sugarlabs.org/bundles/Implode-20.1.1~quozl.xo
198
https://v4.activities.sugarlabs.org/app/com.jotaro.ImplodeActivity.html
sha256:18be1821a7f2e6bfb9de59b11d3ae18b92271b354bb8b38f8a06e9d99a37a6fe
> >
> On 1/21/21 10:03 AM, Srevin Saju wrote:
> > Right. I will configure ASLO-v4 to email sugar-devel@ with release
> > notifications.
> > Thanks to all developers, mentors who helped me out with this. Had a
> > great experience working with it!!!
> >
> > On 1/21/21 10:00 AM, James Cameron wrote:
> > > Thanks, great work. Merged 204.
> > >
> > > I've also updated Browse.
> > >
> > > https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac
> > >
> > >
> > > I would prefer new version notifications to go to
> > > sugar-devel@lists.sugarlabs.org, as that's one place we've seen them
> > > previously. a...@lists.sugarlabs.org was for handling by library
> > > editors, but we don't have any active, and we don't have the same
> > > process with v4.
> > >
> > > On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote:
> > > > G'day!
> > > >
> > > > ASLO-v4 is finally up at https://v4.activities.sugarlabs.org!
> > > > ... with only
> > > > a few more minor tidying up, ASLO-v4 will be ready for production.
> > > >
> > > > Activity maintainers can now push their bundles to ASLO-v4 by
> > > > following the
> > > > instructions on
> > > > https://wiki.sugarlabs.org/go/Service/activities4 as well
> > > > as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204.
> > > > Please feel free to reach out, so that I can improve the existing
> > > > documentation, or anything you think is too complex.
> > > >
> > > > Next steps:
> > > >
> > > > * Connect services/update-aslo.php and deploy a flask server (I am
> > > > trying to get a hold of some more good apache knowledge)
> > > > * Sending "new version detected" emails to a...@lists.sugarlabs.org,
> > > > or should we create a new mailing list?
> > > >
> > > > --
> > > > Srevin Saju
> > > > https://srevinsaju.me
> > > >
> > > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju)
> > >
> > > > sub RSA 4096/14479587 2020-05-19
> > > >
> > >
> > >
> > >
> > > > ___
> > > > Systems mailing list
> > > > syst...@lists.sugarlabs.org
> > > > http://lists.sugarlabs.org/listinfo/systems
> > >
> > >
> > > ___
> > > Sugar-devel mailing list
> > > Sugar-devel@lists.sugarlabs.org
> > > http://lists.sugarlabs.org/listinfo/sugar-devel
>
> --
> Srevin Saju
> https://srevinsaju.me
>
pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju)
> sub RSA 4096/14479587 2020-05-19
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
--
James Cameron
https://quozl.linux.org.au/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Systems] v4.activities.sugarlabs.org (ASLO-v4) is up!
On Thu, Jan 21, 2021 at 11:28:00AM +0300, Srevin Saju wrote: > And now, (Thanks bernie_!), we can use > https://v4.activities.sugarlabs.org/services/update-aslo.php for supporting > sugar's microformat update system as mentioned below: > > > * support Sugar's microformat software upgrade feature in My > > Settings, (Sugar 0.116 is configured > > in|data/org.sugarlabs.gschema.xml|to use the AsloUpdater > > in|src/jarabe/model/update/aslo.py|which reaches out to a PHP > > script|update-aslo.php|, and will instead be configured to > > use|src/jarabe/model/update/microformat.py|), https://github.com/sugarlabs/sugar/pull/939 Needs testing. I've used tcpdump and saw no evidence of connection to port 443, so I'm yet to dig into how to reconfigure my Sugar install. > > > On 1/21/21 10:03 AM, Srevin Saju wrote: > > Right. I will configure ASLO-v4 to email sugar-devel@ with release > > notifications. > > Thanks to all developers, mentors who helped me out with this. Had a > > great experience working with it!!! > > > > On 1/21/21 10:00 AM, James Cameron wrote: > > > Thanks, great work. Merged 204. > > > > > > I've also updated Browse. > > > > > > https://github.com/sugarlabs/browse-activity/commit/de3c4800ec705e5543c6be2c4d4695255d6e5aac > > > > > > > > > I would prefer new version notifications to go to > > > sugar-devel@lists.sugarlabs.org, as that's one place we've seen them > > > previously. a...@lists.sugarlabs.org was for handling by library > > > editors, but we don't have any active, and we don't have the same > > > process with v4. > > > > > > On Thu, Jan 21, 2021 at 09:16:47AM +0300, Srevin Saju wrote: > > > > G'day! > > > > > > > > ASLO-v4 is finally up at https://v4.activities.sugarlabs.org! > > > > ... with only > > > > a few more minor tidying up, ASLO-v4 will be ready for production. > > > > > > > > Activity maintainers can now push their bundles to ASLO-v4 by > > > > following the > > > > instructions on > > > > https://wiki.sugarlabs.org/go/Service/activities4 as well > > > > as, that mentioned in https://github.com/sugarlabs/sugar-docs/pull/204. > > > > Please feel free to reach out, so that I can improve the existing > > > > documentation, or anything you think is too complex. > > > > > > > > Next steps: > > > > > > > > * Connect services/update-aslo.php and deploy a flask server (I am > > > > trying to get a hold of some more good apache knowledge) > > > > * Sending "new version detected" emails to a...@lists.sugarlabs.org, > > > > or should we create a new mailing list? > > > > > > > > -- > > > > Srevin Saju > > > > https://srevinsaju.me > > > > > > > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) > > > > > > > sub RSA 4096/14479587 2020-05-19 > > > > > > > > > > > > > > > > > ___ > > > > Systems mailing list > > > > syst...@lists.sugarlabs.org > > > > http://lists.sugarlabs.org/listinfo/systems > > > > > > > > > ___ > > > Sugar-devel mailing list > > > Sugar-devel@lists.sugarlabs.org > > > http://lists.sugarlabs.org/listinfo/sugar-devel > > -- > Srevin Saju > https://srevinsaju.me > pub RSA 4096/66D390D7 2020-05-19 Srevin Saju (srevinsaju) > sub RSA 4096/14479587 2020-05-19 > > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel -- James Cameron https://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Spectrum
I was introduced to https://spectrum.chat/ while at https://linux.conf.au/ for working with the open hardware miniconference track. Spectrum is open source. https://github.com/withspectrum -- James Cameron https://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Participation in GSOC 2021
Hi Saurabh, Thanks for your interest in Sugarizer and for your contributions. As James mentioned, there is no specific request today about integrating Hindi language in Sugarizer. I tend to prefer adding features asked by the field and there is no today deployment asking for Hindi. But of course anyone can propose new features, so I will certainly accept new languages for Sugarizer. BTW localization in Sugarizer is not a programming task, it's handled using a dedicated website - more friendly for translators - on https://translate.sugarizer.org Regards. Lionel Date: Mon, 25 Jan 2021 10:29:21 +1100 > From: James Cameron > To: Saurabh Gupta > Cc: "sugar-devel@lists.sugarlabs.org" > > Subject: Re: [Sugar-devel] Participation in GSOC 2021 > Message-ID: <20210124232921.gd16...@laptop.org> > Content-Type: text/plain; charset=us-ascii > > Welcome Saurabh, > > We are a permissionless community. Why do you not add Hindi as a > language immediately? There is no issue or pull request that mentions > Hindi. There are closed pull requests that add other languages. I > doubt Lionel has any reason to refuse a language, but if you think > that may be the case, and you see no reply from him here, then ask him > directly. > > On Sat, Jan 23, 2021 at 02:30:57PM +, Saurabh Gupta wrote: > > Hi everyone, > > I hope you all are doing well > > By way of introduction, I am Saurabh, a 2nd-year student from IIT > Roorkee. I am > > contributing to Sugarizer for the last few months and have fixed some > issues. > > During this journey, I gained some knowledge about sugarizer activities > and how > > sugarizer works. > > Here, I am just eager to know if sugarizer is planning to incorporate > Hindi as > > a language in the coming future just like MusicBlocks has? > > Further, I am eagerly looking forward to participate in GSoC 2021 and > make > > valuable contributions to Sugarlabs. > > > > Regards > > Saurabh Gupta > > > ___ > > Sugar-devel mailing list > > Sugar-devel@lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > -- > James Cameron > https://quozl.linux.org.au/ > > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
