[Sugar-devel] Response in Re: you needed Assistance
Pratul Kumar
pratulkumar1997 at gmail.com
Fri May 18 09:02:19 EDT 2018
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*>>>>>https://github.com/sugarlabs/sugarizer
*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 <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]
> 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]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]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]https://mixstersite.wordpress.com/
> > > [2] [5]https://github.com/vipulgupta2048
> >
> > > _______________________________________________
> > > Sugar-devel mailing list
> > > [6]Sugar-devel at lists.sugarlabs.org
> > > [7]http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> >
> > --
> > James Cameron
> > [8]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:pratulkumar1997 at gmail.com
> > [2] mailto:quozl at laptop.org
> > [3] https://developer.github.com/v3/
> > [4] https://mixstersite.wordpress.com/
> > [5] https://github.com/vipulgupta2048
> > [6] mailto:Sugar-devel at lists.sugarlabs.org
> > [7] http://lists.sugarlabs.org/listinfo/sugar-devel
> > [8] http://quozl.netrek.org/
> > [9] https://www.linkedin.com/in/pratul1997/
> > [10] https://github.com/Pratul1997
> > [11] https://www.linkedin.com/in/pratul1997/
> > [12] https://github.com/Pratul1997
>
> --
> James Cameron
> http://quozl.netrek.org/
>
--
*Pratul Kumar | S**ophomore 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*
[image: LinkedIn] <https://www.linkedin.com/in/pratul1997/> [image:
Github] <https://github.com/Pratul1997>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20180518/b4f1e1b2/attachment-0001.html>
More information about the Sugar-devel
mailing list