Re: [Sugar-devel] GSoC Project Contribution

[Pratul Kumar]

 Hello Walter,

I went through this link https://publiclab.github.io/community-toolbox/
 and thanks for sharing it
with me.

It looks like its functioning is mainly governed by a bot name plotsbot
.

Another organization which we have kept in the look from beginning Coala
also use such bot corobo .
This bot mainly functions on their Gitter channel, I have seen its working
in past few days.
These days I am looking forward how it is made, seems that it is itself
going to be a decent project.

I am looking how to make it in the easier way and if feasible I will try to
work on it.

Regards,
Pratul Kumar

On Fri, Feb 16, 2018 at 6:48 PM, Walter Bender 
wrote:

> https://publiclab.github.io/community-toolbox/ is an example of a
> direction we might want to consider. Especially in light of the fact that
> we have issues spread across so many different repositories.
>
> On Fri, Feb 16, 2018 at 12:24 AM, Pratul Kumar 
> wrote:
>
>> Hello,
>> Hope you all are doing well.
>>
>> As we have already discussed my interest in the project - "Making a
>> Beginner Guide" since this project can be highly valuable to our community
>> for future aspects.
>>
>> After reading the conversation regarding the coding and programming touch
>> for GSoC projects, I went through Beginner Guides of few other
>> organizations, observed them.
>>
>>  and I have few suggestions which we can add to the current draft of this
>> project idea(Making a beginner guide).
>>
>> We can add login and dashboard feature to our website where we are going
>> to write beginner guide like the one Mozilla has written (link
>> ).
>>  The
>> purpose of making dashboard is to make a newcomer feel more close to the
>> community. The dashboard will have certain features of adding Profile
>> Photo, About us section.Also, privacy can be maintained by the users.
>>
>> The dashboard can be logged in through single click integrated with
>> Google Gmail ID or Github like KDE
>> .
>>
>> Some of the benefits of adding this property to the current plans are
>> given.
>> 1. The user can add shortcuts to their dashboard just by single click if
>> they want to add some pages of the beginner guide for their future
>> reference, It will make things better and easy to use.
>>
>> 2. Badges: We can add the feature of badges like you get some badge when
>> you complete the certain portion of the guide, And more badges get added
>> when you completed other parts of the guide. It will be a motivation factor
>> for the students.
>>
>> The option of login will not be the compulsory part, the documentation
>> can be viewed without even logging.
>> These features will be the add-on to the current idea of Beginner Guide.
>>
>> It will bring good coding touch to the project and also this dashboard
>> feature can be explored in the much better way in future like Season of KDE
>> dashboard and certain other competitions like BOSS - Bountiful Open
>> Source Summer .
>>
>> Currently, I have skills required to implement this project and I am very
>> much enthusiastic and eager to do more on this project.
>>
>> Prerequisite:HTML,CSS,JavaScript,Bootstrap,Jquery,NodeJs,Angular,MongoDB.
>>
>> Regards,
>> Pratul Kumar
>>
>> On Wed, Feb 14, 2018 at 9:22 PM, Pratul Kumar 
>> wrote:
>>
>>> Hi James,
>>>
>>> .>  - use your other students _during_ the project rather than _after_,
>>> so that the content can be reviewed and refined by beginners,
>>>
>>> I also think getting feedback from newcomer from starting will be more
>>> beneficial.
>>>
>>>
>>>
>>> >  So it will be helpful to Sugar Labs if your content can be maintained by
>>> others.
>>>
>>> So for it, I think we can utilize Github pages and Cname them to our
>>> link.
>>> So other collaborators can also use and change them from Github
>>> according to their requirements and needs.
>>> Therefore others can also maintain it.
>>>
>>>
>>>
>>> Yes, I will try to use only those Tools and Frameworks which are Open
>>> Source and are extremely easy to deploy.
>>>
>>> Regards,
>>> Pratul Kumar
>>>
>>> On Wed, Feb 14, 2018 at 11:14 AM, James Cameron 
>>> wrote:
>>>
 G'day Pratul,

 Thanks for your answer.  The controls you propose for risks seem well
 thought out, though I'd propose one small change;

 - use your other students _during_ the project rather than _after_, so
   that the content can be reviewed and refined by beginners,

 I'll try to answer your other questions;

 Content hosted by Sugar Labs is maintained by many collaborators,
 using different editing or deployment tools.

 Your project is to make some more content.

Re: [Sugar-devel] GSoC Project Contribution

[Walter Bender]

https://publiclab.github.io/community-toolbox/ is an example of a direction
we might want to consider. Especially in light of the fact that we have
issues spread across so many different repositories.

On Fri, Feb 16, 2018 at 12:24 AM, Pratul Kumar 
wrote:

> Hello,
> Hope you all are doing well.
>
> As we have already discussed my interest in the project - "Making a
> Beginner Guide" since this project can be highly valuable to our community
> for future aspects.
>
> After reading the conversation regarding the coding and programming touch
> for GSoC projects, I went through Beginner Guides of few other
> organizations, observed them.
>
>  and I have few suggestions which we can add to the current draft of this
> project idea(Making a beginner guide).
>
> We can add login and dashboard feature to our website where we are going
> to write beginner guide like the one Mozilla has written (link
> ).
>  The
> purpose of making dashboard is to make a newcomer feel more close to the
> community. The dashboard will have certain features of adding Profile
> Photo, About us section.Also, privacy can be maintained by the users.
>
> The dashboard can be logged in through single click integrated with Google
> Gmail ID or Github like KDE
> .
>
> Some of the benefits of adding this property to the current plans are
> given.
> 1. The user can add shortcuts to their dashboard just by single click if
> they want to add some pages of the beginner guide for their future
> reference, It will make things better and easy to use.
>
> 2. Badges: We can add the feature of badges like you get some badge when
> you complete the certain portion of the guide, And more badges get added
> when you completed other parts of the guide. It will be a motivation factor
> for the students.
>
> The option of login will not be the compulsory part, the documentation can
> be viewed without even logging.
> These features will be the add-on to the current idea of Beginner Guide.
>
> It will bring good coding touch to the project and also this dashboard
> feature can be explored in the much better way in future like Season of KDE
> dashboard and certain other competitions like BOSS - Bountiful Open
> Source Summer .
>
> Currently, I have skills required to implement this project and I am very
> much enthusiastic and eager to do more on this project.
>
> Prerequisite:HTML,CSS,JavaScript,Bootstrap,Jquery,NodeJs,Angular,MongoDB.
>
> Regards,
> Pratul Kumar
>
> On Wed, Feb 14, 2018 at 9:22 PM, Pratul Kumar 
> wrote:
>
>> Hi James,
>>
>> .>  - use your other students _during_ the project rather than _after_,
>> so that the content can be reviewed and refined by beginners,
>>
>> I also think getting feedback from newcomer from starting will be more
>> beneficial.
>>
>>
>>
>> >  So it will be helpful to Sugar Labs if your content can be maintained by
>> others.
>>
>> So for it, I think we can utilize Github pages and Cname them to our link.
>> So other collaborators can also use and change them from Github according
>> to their requirements and needs.
>> Therefore others can also maintain it.
>>
>>
>>
>> Yes, I will try to use only those Tools and Frameworks which are Open
>> Source and are extremely easy to deploy.
>>
>> Regards,
>> Pratul Kumar
>>
>> On Wed, Feb 14, 2018 at 11:14 AM, James Cameron  wrote:
>>
>>> G'day Pratul,
>>>
>>> Thanks for your answer.  The controls you propose for risks seem well
>>> thought out, though I'd propose one small change;
>>>
>>> - use your other students _during_ the project rather than _after_, so
>>>   that the content can be reviewed and refined by beginners,
>>>
>>> I'll try to answer your other questions;
>>>
>>> Content hosted by Sugar Labs is maintained by many collaborators,
>>> using different editing or deployment tools.
>>>
>>> Your project is to make some more content.
>>>
>>> So it will be helpful to Sugar Labs if your content can be maintained
>>> by others.
>>>
>>> Measuring maintainability of content, by measuring the involvement by
>>> others, is my proposed control for the risk #3 of content being
>>> abandoned.
>>>
>>> Using certain front-end frameworks means nothing to me without first
>>> knowing the work flow for maintenance; what form will the content be
>>> maintained in, and what tools will be required by any maintainer?  Are
>>> the tools and frameworks open source and easily deployed?
>>>
>>> Recently, we have begun to favour GitHub Markdown; it has a low
>>> barrier of entry, and is reasonably easy to understand.
>>>
>>> --
>>> James Cameron
>>> http://quozl.netrek.org/
>>>
>>
>>
>>
>> --
>> *​Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493
>> <+91%2081075%2025493>*
>>
>> *GCI Mentor* SugarLabs*, Mentor* & Beta Tester at *Coursera*,
>> * HKUST 

Re: [Sugar-devel] GSoC Project Contribution

[Pratul Kumar]

 Hello,
Hope you all are doing well.

As we have already discussed my interest in the project - "Making a
Beginner Guide" since this project can be highly valuable to our community
for future aspects.

After reading the conversation regarding the coding and programming touch
for GSoC projects, I went through Beginner Guides of few other
organizations, observed them.

 and I have few suggestions which we can add to the current draft of this
project idea(Making a beginner guide).

We can add login and dashboard feature to our website where we are going to
write beginner guide like the one Mozilla has written (link
).
The
purpose of making dashboard is to make a newcomer feel more close to the
community. The dashboard will have certain features of adding Profile
Photo, About us section.Also, privacy can be maintained by the users.

The dashboard can be logged in through single click integrated with Google
Gmail ID or Github like KDE .

Some of the benefits of adding this property to the current plans are given.
1. The user can add shortcuts to their dashboard just by single click if
they want to add some pages of the beginner guide for their future
reference, It will make things better and easy to use.

2. Badges: We can add the feature of badges like you get some badge when
you complete the certain portion of the guide, And more badges get added
when you completed other parts of the guide. It will be a motivation factor
for the students.

The option of login will not be the compulsory part, the documentation can
be viewed without even logging.
These features will be the add-on to the current idea of Beginner Guide.

It will bring good coding touch to the project and also this dashboard
feature can be explored in the much better way in future like Season of KDE
dashboard and certain other competitions like BOSS - Bountiful Open Source
Summer .

Currently, I have skills required to implement this project and I am very
much enthusiastic and eager to do more on this project.

Prerequisite:HTML,CSS,JavaScript,Bootstrap,Jquery,NodeJs,Angular,MongoDB.

Regards,
Pratul Kumar

On Wed, Feb 14, 2018 at 9:22 PM, Pratul Kumar 
wrote:

> Hi James,
>
> .>  - use your other students _during_ the project rather than _after_, so 
> that
> the content can be reviewed and refined by beginners,
>
> I also think getting feedback from newcomer from starting will be more
> beneficial.
>
>
>
> >  So it will be helpful to Sugar Labs if your content can be maintained by
> others.
>
> So for it, I think we can utilize Github pages and Cname them to our link.
> So other collaborators can also use and change them from Github according
> to their requirements and needs.
> Therefore others can also maintain it.
>
>
>
> Yes, I will try to use only those Tools and Frameworks which are Open
> Source and are extremely easy to deploy.
>
> Regards,
> Pratul Kumar
>
> On Wed, Feb 14, 2018 at 11:14 AM, James Cameron  wrote:
>
>> G'day Pratul,
>>
>> Thanks for your answer.  The controls you propose for risks seem well
>> thought out, though I'd propose one small change;
>>
>> - use your other students _during_ the project rather than _after_, so
>>   that the content can be reviewed and refined by beginners,
>>
>> I'll try to answer your other questions;
>>
>> Content hosted by Sugar Labs is maintained by many collaborators,
>> using different editing or deployment tools.
>>
>> Your project is to make some more content.
>>
>> So it will be helpful to Sugar Labs if your content can be maintained
>> by others.
>>
>> Measuring maintainability of content, by measuring the involvement by
>> others, is my proposed control for the risk #3 of content being
>> abandoned.
>>
>> Using certain front-end frameworks means nothing to me without first
>> knowing the work flow for maintenance; what form will the content be
>> maintained in, and what tools will be required by any maintainer?  Are
>> the tools and frameworks open source and easily deployed?
>>
>> Recently, we have begun to favour GitHub Markdown; it has a low
>> barrier of entry, and is reasonably easy to understand.
>>
>> --
>> 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*
> *C.A*.@*GeeksforGeeks*, Interntheory, *Sub-Coordinator* Innovation, and
> Incubation Center, Finance@*IEEE* LNMIIT
> 
>   
> 
>
> 
>
>


-- 
*​Pratul Kumar | S**ophomore LNMIIT** | +91-8107525493*

*GCI Mentor* SugarLabs*, 

Re: [Sugar-devel] GSoC Project Contribution

[Pratul Kumar]

Hi James,

.>  - use your other students _during_ the project rather than _after_, so that
the content can be reviewed and refined by beginners,

I also think getting feedback from newcomer from starting will be more
beneficial.



>  So it will be helpful to Sugar Labs if your content can be maintained by
others.

So for it, I think we can utilize Github pages and Cname them to our link.
So other collaborators can also use and change them from Github according
to their requirements and needs.
Therefore others can also maintain it.



Yes, I will try to use only those Tools and Frameworks which are Open
Source and are extremely easy to deploy.

Regards,
Pratul Kumar

On Wed, Feb 14, 2018 at 11:14 AM, James Cameron  wrote:

> G'day Pratul,
>
> Thanks for your answer.  The controls you propose for risks seem well
> thought out, though I'd propose one small change;
>
> - use your other students _during_ the project rather than _after_, so
>   that the content can be reviewed and refined by beginners,
>
> I'll try to answer your other questions;
>
> Content hosted by Sugar Labs is maintained by many collaborators,
> using different editing or deployment tools.
>
> Your project is to make some more content.
>
> So it will be helpful to Sugar Labs if your content can be maintained
> by others.
>
> Measuring maintainability of content, by measuring the involvement by
> others, is my proposed control for the risk #3 of content being
> abandoned.
>
> Using certain front-end frameworks means nothing to me without first
> knowing the work flow for maintenance; what form will the content be
> maintained in, and what tools will be required by any maintainer?  Are
> the tools and frameworks open source and easily deployed?
>
> Recently, we have begun to favour GitHub Markdown; it has a low
> barrier of entry, and is reasonably easy to understand.
>
> --
> 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*
*C.A*.@*GeeksforGeeks*, Interntheory, *Sub-Coordinator* Innovation, and
Incubation Center, Finance@*IEEE* LNMIIT

  



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

Re: [Sugar-devel] GSoC Project Contribution

[James Cameron]

G'day Pratul,

Thanks for your answer.  The controls you propose for risks seem well
thought out, though I'd propose one small change;

- use your other students _during_ the project rather than _after_, so
  that the content can be reviewed and refined by beginners,

I'll try to answer your other questions;

Content hosted by Sugar Labs is maintained by many collaborators,
using different editing or deployment tools.

Your project is to make some more content.

So it will be helpful to Sugar Labs if your content can be maintained
by others.

Measuring maintainability of content, by measuring the involvement by
others, is my proposed control for the risk #3 of content being
abandoned.

Using certain front-end frameworks means nothing to me without first
knowing the work flow for maintenance; what form will the content be
maintained in, and what tools will be required by any maintainer?  Are
the tools and frameworks open source and easily deployed?

Recently, we have begun to favour GitHub Markdown; it has a low
barrier of entry, and is reasonably easy to understand.

-- 
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] GSoC Project Contribution

[Pratul Kumar]

Hi James,
Thanks for such well explained response.

Risk #1; your beginner guide does not help a beginner.
Regarding it, I had thought that bringing all the resources at a single
place with proper linking within, it might help to properly navigate.
So, instead of having multiple newcomer guides resources, we can add all
the resource in one place.

I have large student community in my college, so after the project
completes, I had a thought to organize a Sugarlabs online seminar, where we
can guide them about Open Source contribution, and direct them to these
newcomer guide website.
So, it will provide me raw feedback from them and I can improve that guide
further.




Risk #2; your beginner guide conflicts with other information.
I had thought to add current beginner guide information to the new
project's website(beginner guide website), and then remove information from
the current existing guide and put the link to new guide at those places.
So, it will be easy to maintain and update them at one place.





Risk #3; your beginner guide is abandoned soon after publishing.

Sugarlabs is my first organization where I got to know what and how Open
Source work and Walter has been great support all this time.
I would like to keep modifying and maintaining them according to community
guideline and projects, even after GSoC overs.
So the work and guide will always be nearly updated according to the
current standards of the community.


Few Parts I was unable to understand, Kindly explain them:

>  So in working on this "making a beginner guide" project, please;
>  - measure or assess the edits by others, (which will depend on the tools
or sources you choose to use),
>  - promote edits by others,
>  - provide some form of social reward.

I wanted to know while making the website can I use certain front-end
frameworks like Bootstrap, Material or any other.

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

Re: [Sugar-devel] GSoC Project Contribution

[James Cameron]

Three recent "beginner guides" also include;

1.  https://github.com/sugarlabs/sugar-docs/blob/master/src/how-can-i-help.md
by GitHub users pipix51, and quozl.

2.  https://github.com/sugarlabs/sugar-docs/blob/master/src/desktop-activity.md
by GitHub users Pro-Panda, and quozl.

3.  https://wiki.sugarlabs.org/go/Google_Code_In_2017/background by Wiki
users Llaske, Pikurasa, Walter, and Quozl.

Please make sure you include these in your work, and also deprecate
them where appropriate.

On Tue, Feb 13, 2018 at 07:27:36PM +0530, Pratul Kumar wrote:
> *
> Hello all,
> I am Pratul Kumar, I am second year undergraduate from LNM Institute of
> Information Technology, India.
> 
> I have been part of Sugarlabs community and was one of the mentor for GCI this
> year.
> During my initial time it was bit difficult for me to set up projects because
> of the lack of beginner guide.
> I would like to make a beginner guide and work on the project " Making a
> Beginner Guide ".
> I have started observing Coala and other organisation New comer guide.
> 
> I would like to take the opportunity to work and develop this project and
> contribute to Sugarlabs via this project.
> 
> I wanted to start working on it, so I need guidance on how to draft the work
> for this project.
> 
> Regards,
> Pratul kumar 
> 

> ___
> 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] GSoC Project Contribution

[James Cameron]

Thanks for your offer.  Here are my thoughts.

Risk #1; your beginner guide does not help a beginner.

Risk #2; your beginner guide conflicts with other information.

Risk #3; your beginner guide is abandoned soon after publishing.

--

Risk #1; your beginner guide does not help a beginner.

We have several beginner guides now.  A book.  A Wiki.  And
sugar-docs.  These do not help some beginners; witness the questions
we keep getting.

Previous beginner guides have had limited testing.  Perhaps testing
will help.

So in working on this "making a beginner guide" project, please
include tests of the guide against beginners; not yourself, and not
the experts.

--

Risk #2; your beginner guide conflicts with other information.

We have a development community fragmentation problem; multiple
sources of conflicting information.  As we migrate from one tool to
another, we fail to take down the old tool.  You can see this in the
way we have a book, a Wiki, and sugar-docs.  You can see a more
detailed example in https://github.com/sugarlabs/sugar-docs/issues/114

So in working on this "making a beginner guide" project, please;

- choose formats that are generally acceptable, such as markdown,

- choose one of the existing sources of information and add to it
  rather than make a new source; such as sugar-docs [1],

- add tools to convert that source to PDF, if PDF is really needed,
  (work flow such as markdown to HTML, then wkhtmltopdf),

- help to ensure old beginner guides are removed or updated,

--

Risk #3; your beginner guide is abandoned soon after publishing.

History of previous beginner guides show that one person writes them,
one person publishes them, some other people edit, and then
maintenance ceases as people leave the community.  Rarely do new
people begin to edit.

Root cause is that people vary in their comfort level with specific
tools or sources.  For example, we still have a valuable contributor
who will not use GitHub no matter how hard we try to help them.

So in working on this "making a beginner guide" project, please;

- measure or assess the edits by others, (which will depend on the
  tools or sources you choose to use),

- promote edits by others,

- provide some form of social reward.

--

References;

1.

https://github.com/sugarlabs/sugar-docs/blob/master/how-can-i-help.md
which was formerly
https://developer.sugarlabs.org/how-can-i-help.md.html

On Tue, Feb 13, 2018 at 07:27:36PM +0530, Pratul Kumar wrote:
> *
> Hello all,
> I am Pratul Kumar, I am second year undergraduate from LNM Institute of
> Information Technology, India.
> 
> I have been part of Sugarlabs community and was one of the mentor for GCI this
> year.
> During my initial time it was bit difficult for me to set up projects because
> of the lack of beginner guide.
> I would like to make a beginner guide and work on the project " Making a
> Beginner Guide ".
> I have started observing Coala and other organisation New comer guide.
> 
> I would like to take the opportunity to work and develop this project and
> contribute to Sugarlabs via this project.
> 
> I wanted to start working on it, so I need guidance on how to draft the work
> for this project.
> 
> Regards,
> Pratul kumar 
> 

> ___
> 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