[Sugar-devel] Sugar-devel Digest, Vol 123, Issue 31
James Cameron
quozl at laptop.org
Mon Jan 21 20:00:29 EST 2019
G'day Avinash,
Thanks for that. Yes, yours was not a GSoC project.
It is an easy mistake to make.
There have been several Social projects. One in 2013, one in 2014,
and the one you were involved in last year.
Yours was a GSoC idea for 2018. We received proposals on it. None of
the proposals were accepted.
As we're at the idea design stage, it is correct to critique the idea
with respect to our GSoC obligations.
https://wiki.sugarlabs.org/go/Summer_of_Code/2018
On Tue, Jan 22, 2019 at 12:39:42AM +0530, Avinash Bharti wrote:
> Hello there,
> From few days I am observing that Social project is being taken as an example
> of an unsuccessful project just because it is not deployed yet.
> Let me clear some things-
> Social was never a GSoC Project, I started doing this project in my summer
> vacation under the mentorship of Hrishi Patel, Samson Goddy, Jaskirat Singh,
> Pericherla Seeta Rama Raju with approval from Walter Bender and thanks to
> mentors and Walter who converted this project as an internship(unpaid).
> At the end of my Internship period, I completed 95% of the proposed v1.0 of
> social.
> Since Deployment task was never under the project proposal so I never tried to
> deploy it.
>
> Thanks and Regards
> Avinash Bharti
> @avinashbharti97
>
> On Mon, Jan 21, 2019 at 11:35 PM <[1]sugar-devel-request at lists.sugarlabs.org>
> wrote:
>
> Send Sugar-devel mailing list submissions to
> [2]sugar-devel at lists.sugarlabs.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> [3]http://lists.sugarlabs.org/listinfo/sugar-devel
> or, via email, send a message with subject or body 'help' to
> [4]sugar-devel-request at lists.sugarlabs.org
>
> You can reach the person managing the list at
> [5]sugar-devel-owner at 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. Re: Suggestions for GSoC 2019 (Samson Goddy)
> 2. Re: Suggestion on moving from IRC to Gitter (Rahul Bothra)
> 3. Re: Suggestions for GSoC 2019 (Walter Bender)
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 21 Jan 2019 18:17:46 +0100
> From: Samson Goddy <[6]samsongoddy at sugarlabs.org>
> To: Rahul Bothra <[7]rrbothra at gmail.com>
> Cc: Amaan Iqbal <[8]amaaniqbal2786 at gmail.com>, Sugar-dev Devel
> <[9]sugar-devel at lists.sugarlabs.org>
> Subject: Re: [Sugar-devel] Suggestions for GSoC 2019
> Message-ID:
> <CAFN_48-L=[10]
> NpBjAnSnbZcTDUJvhM9uLeVRAeCqDNvuiHSTmuN+Q at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Just for some point of correction.
>
> Sugar Labs Social was never a GSoC project, I don't understand why you
> keep bringing it up. Any "coding" project that is related to Sugar Lab's
> goals or leads to improvement to the mission is eligible as a Gsoc
> project.
>
> Some project requires more than 3 months of coding to be called a
> successful project. I just wonder how these decisions are made. Let utilize
> the GSoC platform to improve every form of Sugar Labs as much as possible.
> Everything is as important as the other.
>
> The current tools we are building how do we measure its success?
>
> Regards
>
> On Mon, Jan 21, 2019 at 5:47 PM Rahul Bothra <[11]rrbothra at gmail.com>
> wrote:
>
> > Hello,
> >
> > On Mon, Jan 21, 2019 at 7:44 PM Amaan Iqbal <[12]amaaniqbal2786 at gmail.com
> >
> > wrote:
> > > I see we only have 6 projects so far in our Ideas list in comparison to
> > 11
> > > which were selected in GSoC last year. Being a successful Open Source
> > > organization, I sincerely hope we have the potential of having many
> more
> > > projects in GSoC this year(most probably 15+ if we can come up with
> > > such promising ideas).
> >
> > We had 12 projects last year, out of which 1 was failed officially. Many
> > projects failed to deliver what was expected out of them, including my
> > own.
> > Some projects did not involve improving our tools, Sugar Desktop,
> > Activities,
> > MusicBlocks or Sugarizer, and did add any value to the organisation.
> > This was primarily because we had more projects than we could handle,
> > and that some projects were not effectively groomed and mentored.
> >
> > I don't know what a "successful Open Source organisation" means. But I
> > don't think we should release more ideas than we can mentor. Having less
> > projects does not imply our failure in any sense, lack of existing
> > contributors
> > might indicate that.
> >
> > > Here I would suggest an idea for the renovation of our Website, blog
> > <[13]http://planet.sugarlabs.org/>, and
> > > creation of a customized/integration of existing CMS to our website
> from
> > > where admins can create articles directly.
> >
> > FWIW, our current website was also implemented as a GSoC Project. I
> > don't think it will improve our tools, or if it will actually be
> > completed. Past
> > examples show that development of such tools (Sugar Social, ASLO v3)
> > never got into deployment at the end.
> >
> > Even if we add a project for improving the website, 2 years down the line
> > we might again face a similar email pointing out the drawbacks of the new
> > model and another revamping of the website.
> >
> > Although I would be happy to see contributions made to improve the
> > website, I am not in favor of adding this as a GSoC Project.
> > FYI, there are plans of A/B testing of the website, though I don't know
> the
> > current status.
> >
> > Thanks,
> > Rahul
> > _______________________________________________
> > Sugar-devel mailing list
> > [14]Sugar-devel at lists.sugarlabs.org
> > [15]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
>
> --
> -------
> Oversight Board Member at Sugar Labs
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <[16]http://lists.sugarlabs.org/archive/sugar-devel/attachments/
> 20190121/ed366573/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 21 Jan 2019 23:12:03 +0530
> From: Rahul Bothra <[17]rrbothra at gmail.com>
> To: Alex Perez <[18]aperez at alexperez.com>
> Cc: Sugar-dev Devel <[19]sugar-devel at lists.sugarlabs.org>
> Subject: Re: [Sugar-devel] Suggestion on moving from IRC to Gitter
> Message-ID:
> <CADhofF8Vove=ubof2DyaSpgCG8Ej_BoiRPrX7PTQ_=[20]
> m60VRA3A at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Thanks James and Alex, I've reviewed all comments and suggestions.
>
> For most of the suggestions, I found no alternate but to use IRC. My
> idea was to see how many people are willing to move to Gitter, and if
> it be helpful for new contributors.
> I've observed this to the only criteria in my recent (radical) decisions
> and they've mostly been poorly thought out, for us as an organisation.
>
> I'm not in favor of keeping both Gitter and IRC, as it further splits the
> community and introduces more problems than it will solve. I have no
> personal preference for either of the two.
>
> I currently have the channel [21]https://gitter.com/Sugar-Labs setup on
> Gitter.
> I'll let SLOBs and others make the final decision. I'm too young and
> inexperienced to comment any further ;-)
>
> Thanks
> Rahul Bothra
>
> On Mon, Jan 21, 2019 at 8:40 AM Alex Perez <[22]aperez at alexperez.com>
> wrote:
>
> > As an oversight board member, for all the same reasons cited below, I am
> > 100% _not_ in favor of this proposal. It's a crude attempt at
> > re-implementing IRC, and despite being open-source, is effectively a
> > proprietary service, which there is no guarantee of continued support
> for.
> > If you want to offer to maintain a Gitter-to-IRC bridge, that's great,
> > otherwise I think this highly negative move.
> >
> > I guess the real question I have, which doesn't seem to have been
> answered
> > anywhere yet, is, why Gitter, specifically? There are other, much more
> > option options, such as Matrix, which have far more mature IRC
> integration
> > options.
> >
> > James Cameron wrote on 1/20/19 4:16 PM:
> >
> > Thanks Rahul. Please add to the plan;
> >
> > - critical people; identify the critical code maintainers and note
> > when they have engaged with Gitter.im on a continuous basis; in
> > particular we are yet to hear from Lionel and Ibiam.
> >
> > - licensing; as an open source project within the Software Freedom
> > Conservancy, we should aim to promote tools that have a compatible
> > license. Devin said the web app is licensed MIT, but the service is
> > All Rights Reserved.
> >
> > - inclusiveness of prior contributors; we have several contributors
> > who know how to use IRC, but are disinclined due to their age to
> > use the modern systems; how do we continue to include them?
> >
> > - further division; every time we start something new, we divide again
> > the group of people talking, and the new group often forgets to keep
> > the old group informed; how will the non-Gitter.im contributors be
> > kept informed? I'm not asking about the IRC contributors, but also
> > people using GitHub, Wiki, Trac, Jabber, Pootle, and the mailing
> > lists.
> >
> > - Code of Conduct; how to make this more obvious in Gitter.im?
> > Especially "If you come across a post that is in an incorrect forum,
> > please respectfully redirect the poster to the appropriate" (as has
> > happened already), and making sure to consult others.
> >
> > I've briefly authorised and looked at Gitter.im, using Firefox on
> > Ubuntu, and have observations;
> >
> > 1. a significant increase in mail contact attempts by other projects
> > on GitHub; i.e. you'll get more spam, because people have coded things
> > to get to you through Gitter,
> >
> > 2. a daily mail message containing some of the notifications from
> > Gitter, but not all,
> >
> > 3. the display does not scroll with page down, page up, or arrow
> > keys, unless you first click in the message area,
> >
> > 4. it isn't clear how I can make a local log of the discussion,
> >
> > 5. the network demand is substantially greater than IRC; this is not
> > something we can expect to scale up into schools with poor networks,
> >
> > 6. the power and processing demand is higher.
> >
> >
> >
> > --
> > Sent from Postbox
> > <[23]https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&
> utm_campaign=reach>
> > _______________________________________________
> > Sugar-devel mailing list
> > [24]Sugar-devel at lists.sugarlabs.org
> > [25]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <[26]http://lists.sugarlabs.org/archive/sugar-devel/attachments/
> 20190121/ea4fe82b/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 21 Jan 2019 13:04:41 -0500
> From: Walter Bender <[27]walter.bender at gmail.com>
> To: Samson Goddy <[28]samsongoddy at sugarlabs.org>
> Cc: Rahul Bothra <[29]rrbothra at gmail.com>, Amaan Iqbal
> <[30]amaaniqbal2786 at gmail.com>, Sugar-dev Devel
> <[31]sugar-devel at lists.sugarlabs.org>
> Subject: Re: [Sugar-devel] Suggestions for GSoC 2019
> Message-ID:
> <CADf7C8sWeJZk77p+6OffTHyeCLpcFBvpxA_7SjonXVzxdOM=[32]
> PQ at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> My two cents re GSoC: from the very beginning of our involvement, I have
> thought of it as an opportunity for us to take some risks and explore new
> ideas. That being said, it is incumbent upon us to provide good mentoring
> and follow through.
>
> -walter
>
> On Mon, Jan 21, 2019 at 12:18 PM Samson Goddy <[33]
> samsongoddy at sugarlabs.org>
> wrote:
>
> > Just for some point of correction.
> >
> > Sugar Labs Social was never a GSoC project, I don't understand why you
> > keep bringing it up. Any "coding" project that is related to Sugar Lab's
> > goals or leads to improvement to the mission is eligible as a Gsoc
> project.
> >
> > Some project requires more than 3 months of coding to be called a
> > successful project. I just wonder how these decisions are made. Let
> utilize
> > the GSoC platform to improve every form of Sugar Labs as much as
> possible.
> > Everything is as important as the other.
> >
> > The current tools we are building how do we measure its success?
> >
> > Regards
> >
> > On Mon, Jan 21, 2019 at 5:47 PM Rahul Bothra <[34]rrbothra at gmail.com>
> wrote:
> >
> >> Hello,
> >>
> >> On Mon, Jan 21, 2019 at 7:44 PM Amaan Iqbal <[35]
> amaaniqbal2786 at gmail.com>
> >> wrote:
> >> > I see we only have 6 projects so far in our Ideas list in comparison
> to
> >> 11
> >> > which were selected in GSoC last year. Being a successful Open Source
> >> > organization, I sincerely hope we have the potential of having many
> more
> >> > projects in GSoC this year(most probably 15+ if we can come up with
> >> > such promising ideas).
> >>
> >> We had 12 projects last year, out of which 1 was failed officially. Many
> >> projects failed to deliver what was expected out of them, including my
> >> own.
> >> Some projects did not involve improving our tools, Sugar Desktop,
> >> Activities,
> >> MusicBlocks or Sugarizer, and did add any value to the organisation.
> >> This was primarily because we had more projects than we could handle,
> >> and that some projects were not effectively groomed and mentored.
> >>
> >> I don't know what a "successful Open Source organisation" means. But I
> >> don't think we should release more ideas than we can mentor. Having less
> >> projects does not imply our failure in any sense, lack of existing
> >> contributors
> >> might indicate that.
> >>
> >> > Here I would suggest an idea for the renovation of our Website, blog
> >> <[36]http://planet.sugarlabs.org/>, and
> >> > creation of a customized/integration of existing CMS to our website
> from
> >> > where admins can create articles directly.
> >>
> >> FWIW, our current website was also implemented as a GSoC Project. I
> >> don't think it will improve our tools, or if it will actually be
> >> completed. Past
> >> examples show that development of such tools (Sugar Social, ASLO v3)
> >> never got into deployment at the end.
> >>
> >> Even if we add a project for improving the website, 2 years down the
> line
> >> we might again face a similar email pointing out the drawbacks of the
> new
> >> model and another revamping of the website.
> >>
> >> Although I would be happy to see contributions made to improve the
> >> website, I am not in favor of adding this as a GSoC Project.
> >> FYI, there are plans of A/B testing of the website, though I don't know
> >> the
> >> current status.
> >>
> >> Thanks,
> >> Rahul
> >> _______________________________________________
> >> Sugar-devel mailing list
> >> [37]Sugar-devel at lists.sugarlabs.org
> >> [38]http://lists.sugarlabs.org/listinfo/sugar-devel
> >>
> >
> >
> > --
> > -------
> > Oversight Board Member at Sugar Labs
> > _______________________________________________
> > Sugar-devel mailing list
> > [39]Sugar-devel at lists.sugarlabs.org
> > [40]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
>
> --
> Walter Bender
> Sugar Labs
> [41]http://www.sugarlabs.org
> <[42]http://www.sugarlabs.org>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <[43]http://lists.sugarlabs.org/archive/sugar-devel/attachments/
> 20190121/c46097e3/attachment.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Sugar-devel mailing list
> [44]Sugar-devel at lists.sugarlabs.org
> [45]http://lists.sugarlabs.org/listinfo/sugar-devel
>
> ------------------------------
>
> End of Sugar-devel Digest, Vol 123, Issue 31
> ********************************************
>
> References:
>
> [1] mailto:sugar-devel-request at lists.sugarlabs.org
> [2] mailto:sugar-devel at lists.sugarlabs.org
> [3] http://lists.sugarlabs.org/listinfo/sugar-devel
> [4] mailto:sugar-devel-request at lists.sugarlabs.org
> [5] mailto:sugar-devel-owner at lists.sugarlabs.org
> [6] mailto:samsongoddy at sugarlabs.org
> [7] mailto:rrbothra at gmail.com
> [8] mailto:amaaniqbal2786 at gmail.com
> [9] mailto:sugar-devel at lists.sugarlabs.org
> [10] mailto:NpBjAnSnbZcTDUJvhM9uLeVRAeCqDNvuiHSTmuN%2BQ at mail.gmail.com
> [11] mailto:rrbothra at gmail.com
> [12] mailto:amaaniqbal2786 at gmail.com
> [13] http://planet.sugarlabs.org/
> [14] mailto:Sugar-devel at lists.sugarlabs.org
> [15] http://lists.sugarlabs.org/listinfo/sugar-devel
> [16] http://lists.sugarlabs.org/archive/sugar-devel/attachments/20190121/ed366573/attachment-0001.html
> [17] mailto:rrbothra at gmail.com
> [18] mailto:aperez at alexperez.com
> [19] mailto:sugar-devel at lists.sugarlabs.org
> [20] mailto:m60VRA3A at mail.gmail.com
> [21] https://gitter.com/Sugar-Labs
> [22] mailto:aperez at alexperez.com
> [23] https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach
> [24] mailto:Sugar-devel at lists.sugarlabs.org
> [25] http://lists.sugarlabs.org/listinfo/sugar-devel
> [26] http://lists.sugarlabs.org/archive/sugar-devel/attachments/20190121/ea4fe82b/attachment-0001.html
> [27] mailto:walter.bender at gmail.com
> [28] mailto:samsongoddy at sugarlabs.org
> [29] mailto:rrbothra at gmail.com
> [30] mailto:amaaniqbal2786 at gmail.com
> [31] mailto:sugar-devel at lists.sugarlabs.org
> [32] mailto:PQ at mail.gmail.com
> [33] mailto:samsongoddy at sugarlabs.org
> [34] mailto:rrbothra at gmail.com
> [35] mailto:amaaniqbal2786 at gmail.com
> [36] http://planet.sugarlabs.org/
> [37] mailto:Sugar-devel at lists.sugarlabs.org
> [38] http://lists.sugarlabs.org/listinfo/sugar-devel
> [39] mailto:Sugar-devel at lists.sugarlabs.org
> [40] http://lists.sugarlabs.org/listinfo/sugar-devel
> [41] http://www.sugarlabs.org/
> [42] http://www.sugarlabs.org/
> [43] http://lists.sugarlabs.org/archive/sugar-devel/attachments/20190121/c46097e3/attachment.html
> [44] mailto:Sugar-devel at lists.sugarlabs.org
> [45] http://lists.sugarlabs.org/listinfo/sugar-devel
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
--
James Cameron
http://quozl.netrek.org/
More information about the Sugar-devel
mailing list