[Sugar-devel] Response in Re: you needed Assistance
James Cameron
quozl at laptop.org
Fri May 18 16:52:07 EDT 2018
G'day Pratul,
What you propose would be suitable for an organisation with central
control of members.
However, Sugar Labs is a loose collective of developers who aim for
several common goals. Our developers do not always concur.
The software licenses we use allow forking. We cannot prevent this,
or patrol it. Nor do we want to.
Developers have very good personal reasons for maintaining their
repositories inside their accounts on GitHub; control of their work,
control of merging other people's work, and an honest expression of
their profile.
So we have to work within those limitations;
- not every repository will be in the http://github.com/sugarlabs
list,
- new repositories may be developed at any time.
You should provide a way for Sugar Labs members to propose, discuss,
and merge changes to the list of repositories used by your dashboard.
We also have some repositories that aren't on GitHub. Some are on a
Gitorious instance at http://git.sugarlabs.org, and some are shown by
a cgit instance at http://dev.laptop.org/git/
People have often said "we should migrate them all to GitHub", but as
far as I can see the only _sensible_ justification is where pull
requests are to be merged by multiple developers.
In summary, I do not support;
- everything should be in GitHub,
- everything should be in one GitHub organisation.
I know this makes your project more difficult, but my understanding is
that GSoC is for roughly three months of full-time coding; I'm sure
anybody with three months to work on this would figure out a solution
that does not involve trying to change a community practice against
the wishes of a community. ;-)
p.s. this is my opinion, not the opinion of the rest of the community!
On Fri, May 18, 2018 at 06:32:19PM +0530, Pratul Kumar wrote:
> *
> Hello James,
> Hope you are doing well.
>
> > No, not really. Members of Sugar Labs have never been _required_ to keep
> their contributions in one place. You would have to ask each member.
>
> I looked at your mail several times and analyzed that there is a threat that
> many of our valuable Sugarlabs projects are not part of Sugarlabs Github
> organization and
> They are forked from the developer's profile to the Sugarlabs organization
> like:
>
> 1>>>>>[1]https://github.com/sugarlabs/sugarizer
>
> 2>>>>>[2]https://github.com/llaske/sugarizer
>
> And there might be several other situations too and there might be some which
> don't be even forked.
>
> So the problem arises that In link_1 Issues are not listed and in link_2 issues
> are listed but it is not a part of Sugarlabs GitHub organization,
> Currently, my API call is such that in Github Sugarlabs organization, I am
> looking for all the open issues which are labeled with some specific labels.
>
> So What solution I seek to this problem is that if Sugarlabs community members
> can share links to those Github Repo which are not part of current
> Github organization, so that I can add search issues API call from those
> repositories too.
> For this method, I would share a google doc where the community members can
> share the link to there GitHub repository.
>
> Or another method is that if we add those repo to Github organization and
> further work is done in the GitHub organization repositories.
>
> If there is any other possible solution to it, then kindly let know regarding
> it.
>
> Thanks,
> Pratul Kumar
>
> On Mon, May 14, 2018 at 12:30 PM, James Cameron <[3]quozl at laptop.org> wrote:
>
> On Mon, May 14, 2018 at 12:03:51PM +0530, Pratul Kumar wrote:
> > *Hello James,
> > Hope you are doing well.
> >
> > This all information would be part of Developer Dashboard
> >
> > > Repositories must also include those that are not in the /sugarlabs/
> > organization, such as the Help Activity and many others.
> >
> > For this, if you can let me know regarding other potential repositories,
> then I
> > can have a add them to my script too.
>
> No, not really. Members of Sugar Labs have never been _required_ to
> keep their contributions in one place. You would have to ask each
> member.
>
> We have some of those repositories cloned to /sugarlabs/, but probably
> not all of them. Cloned repositories are not kept up to date.
>
> An example of an important repository that should be tracked is the
> repository from which /sugarlabs/sugarizer is cloned.
>
> > > I still don't think a developer dashboard will help Sugar Labs at
> a social
> > level, because we have so few developers.
> >
> > Each year new developer's are there around GCI who are looking for the
> > organization to contribute and be their part,
>
> We may not be successful in applying for GCI this year. Our care and
> diligence as a community should recognise that possibility and plan
> for it as well.
>
> > What I feel that want things to be ease contribute to the organization
> through
> > Github, but without having the knowledge to do so they step back.
> > Further, new developers need some social rewards for their work, if that
> can be
> > reflected in our Developer Dashboard.
> > Let us give a try to improve our developer count through this
> methodology,
> > although it won't give a drastic improvement.
>
> As I said, I don't mind if you try, it's just that your argument and
> others argument is unconvincing. Amazing claims need amazing
> evidence, and the evidence so far is not amazing. Tony's assessment
> of how badly Sugar runs on Ubuntu 18.04 is more real.
>
> > If required then that can be used to organize our own program like GCI
> for
> > about a months before GCI with a bit similar methodology, where our new
> mentors
> > can know what they need to do during GCI. This is to engage a greater
> number of
> > Developers to Sugarlabs.
> >
> > Regards,
> > Pratul Kumar
> >
> > On Mon, May 14, 2018 at 11:33 AM, Pratul Kumar <[1][4]
> pratulkumar1997 at gmail.com>
> > wrote:
> >
> > *Hello Vipul,
> > Hope you are doing well.
> >
> > Thanks, Vipul for your initiative for help, yesterday I figured out
> the
> > methodology for my problem.
> > I used GitHub API instead using any NPM module or library. I read
> your mail
> > after I had sorted out the problem.
> > Once again I would like to thank you for the same.
> >
> > Regards,
> > Pratul Kumar
> >
> > On Mon, May 14, 2018 at 2:27 AM, James Cameron <[2][5]
> quozl at laptop.org> wrote:
> >
> > All data from GitHub issues would be useful for a developer
> dashboard.
> >
> > It's not simple. Repositories must also include those that are
> not in
> > the /sugarlabs/ organisation, such as the Help Activity, and many
> > others.
> >
> > Pratul is writing a web application, and likely coding in
> JavaScript,
> > so the GitHub REST API [3][6]https://developer.github.com/v3/
> should have
> > what is needed. If Pratul has a problem with the API, ask GitHub
> Help
> > team or #github IRC channel. The GitHub API is not part of Sugar.
> >
> > I still don't think a developer dashboard will help Sugar Labs at
> a
> > social level, because we have so few developers, but I've no
> objection
> > to someone trying it.
> >
> > On Sun, May 13, 2018 at 10:44:59AM +0530, Vipul Gupta wrote:
> > > Hi,
> > > Over the problem, you were having - You need all issues of a
> every
> > Repository
> > > in Sugar Labs. I would need some clarification on the same.
> > >
> > > 1. How do you need all the issues (Issue description, just
> titles, on
> > respect
> > > to what, repo to repo or some other criteria?)
> > > 2. Why Javascript, I couldn't understand this part. Shouldn't
> you
> > need the
> > > output in a more accessible format like JSON for instance? You
> can
> > use the
> > > GitHub API for the same (I strongly recommend PyGitHub)
> > >
> > > Cordially,
> > > Vipul Gupta
> > > [1]Mixster | [2]Github
> > > Ps - I did read your messages, that day on IRC. I made the
> draft at
> > night but
> > > forgot to send it until now and yesterday I was busy with my
> > community meetup.
> > >
> > > References:
> > >
> > > [1] [4][7]https://mixstersite.wordpress.com/
> > > [2] [5][8]https://github.com/vipulgupta2048
> >
> > > _______________________________________________
> > > Sugar-devel mailing list
> > > [6][9]Sugar-devel at lists.sugarlabs.org
> > > [7][10]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> >
> > --
> > James Cameron
> > [8][11]http://quozl.netrek.org/
> >
> >
> > --
> >
> > Pratul Kumar | Sophomore LNMIIT | +91-8107525493
> >
> > GCI Mentor SugarLabs, Mentor & Beta Tester at Coursera, HKUST
> > University
> > Stanford Scholar Internship, Mozilla Club Captain LNMIIT, Head of
> > Developers Group HackerEarth
> > [s] [9]LinkedIn [s] [10]Github _ [s]
> >
> >
> > --
> >
> > Pratul Kumar | Sophomore LNMIIT | +91-8107525493
> >
> > GCI Mentor SugarLabs, Mentor & Beta Tester at Coursera, HKUST
> University
> > Stanford Scholar Internship, Mozilla Club Captain LNMIIT, Head of
> > Developers Group HackerEarth
> > [s] [11]LinkedIn _ [12]Github _ [s]
> >
> > References:
> >
> > [1] mailto:[12]pratulkumar1997 at gmail.com
> > [2] mailto:[13]quozl at laptop.org
> > [3] [14]https://developer.github.com/v3/
> > [4] [15]https://mixstersite.wordpress.com/
> > [5] [16]https://github.com/vipulgupta2048
> > [6] mailto:[17]Sugar-devel at lists.sugarlabs.org
> > [7] [18]http://lists.sugarlabs.org/listinfo/sugar-devel
> > [8] [19]http://quozl.netrek.org/
> > [9] [20]https://www.linkedin.com/in/pratul1997/
> > [10] [21]https://github.com/Pratul1997
> > [11] [22]https://www.linkedin.com/in/pratul1997/
> > [12] [23]https://github.com/Pratul1997
>
> --
> James Cameron
> [24]http://quozl.netrek.org/
>
> --
>
> Pratul Kumar | Sophomore LNMIIT | +91-8107525493
>
> GCI Mentor SugarLabs, Mentor & Beta Tester at Coursera, HKUST University
> Stanford Scholar Internship, Mozilla Club Captain LNMIIT, Head of
> Developers Group HackerEarth
> _ [25]LinkedIn [s] [26]Github [s] [s]
>
> References:
>
> [1] https://github.com/sugarlabs/sugarizer
> [2] https://github.com/llaske/sugarizer
> [3] mailto:quozl at laptop.org
> [4] mailto:pratulkumar1997 at gmail.com
> [5] mailto:quozl at laptop.org
> [6] https://developer.github.com/v3/
> [7] https://mixstersite.wordpress.com/
> [8] https://github.com/vipulgupta2048
> [9] mailto:Sugar-devel at lists.sugarlabs.org
> [10] http://lists.sugarlabs.org/listinfo/sugar-devel
> [11] http://quozl.netrek.org/
> [12] mailto:pratulkumar1997 at gmail.com
> [13] mailto:quozl at laptop.org
> [14] https://developer.github.com/v3/
> [15] https://mixstersite.wordpress.com/
> [16] https://github.com/vipulgupta2048
> [17] mailto:Sugar-devel at lists.sugarlabs.org
> [18] http://lists.sugarlabs.org/listinfo/sugar-devel
> [19] http://quozl.netrek.org/
> [20] https://www.linkedin.com/in/pratul1997/
> [21] https://github.com/Pratul1997
> [22] https://www.linkedin.com/in/pratul1997/
> [23] https://github.com/Pratul1997
> [24] http://quozl.netrek.org/
> [25] https://www.linkedin.com/in/pratul1997/
> [26] https://github.com/Pratul1997
--
James Cameron
http://quozl.netrek.org/
More information about the Sugar-devel
mailing list