Changes

*WikiPort will help users port their wikis to GitHub with minimum user inputs, which  would ultimately benefit everyone involved and for many generations of developers to come who will use that documentation.

*WikiPort will help users port their wikis to GitHub with minimum user inputs, which  would ultimately benefit everyone involved and for many generations of developers to come who will use that documentation.

*As previously stated, documentation is an important part of any development process. Bad documentation impacts the entire community as. But if the documentation is

*As previously stated, documentation is an important part of any development process. Bad documentation impacts the entire community as. But if the documentation is

1. '''Accessible''' - GitHub is one of the best places to host it.  

1. '''Accessible''' - GitHub is one of the best places to host it. <br />

2. '''Relevant and easily traversable''' - The documentation about every activity will be housed with its GitHub Repository.

2. '''Relevant and easily traversable''' - The documentation about every activity will be housed with its GitHub Repository. <br />

Clearly written - Strict format to maintain overall uniformity.  

Clearly written - Strict format to maintain overall uniformity. <br />

3. '''Easily editable (+ VCS)''' - Wiki offers edit history of documents too, but the process to edit a document is cumbersome while GitHub makes it very easy for users to fix issues in it.  

3. '''Easily editable (+ VCS)''' - Wiki offers edit history of documents too, but the process to edit a document is cumbersome while GitHub makes it very easy for users to fix issues in it. <br />

4. '''More views, more stars''' - GitHub also increases views and popularity of the activity ultimately helping Sugar Labs to get noticed more.

4. '''More views, more stars''' - GitHub also increases views and popularity of the activity ultimately helping Sugar Labs to get noticed more. <br />

If our documentation has all these features, then everybody would be more inclined towards contributing to Sugar Labs and get to know more about it.   

If our documentation has all these features, then everybody would be more inclined towards contributing to Sugar Labs and get to know more about it.   

People would contribute more to bug fixing, indirectly helping the Sugar Labs community to grow and expand more. Helping students, developers, activity maintainers, members of the community.

People would contribute more to bug fixing, indirectly helping the Sugar Labs community to grow and expand more. Helping students, developers, activity maintainers, members of the community.

'''Answer 3:''' James Cameron - quozl@laptop.org <br />

'''Answer 3:''' James Cameron - quozl@laptop.org <br />

(His assessment of project impact from both Github and Email )

(His assessment of project impact from both Github and Email )<br />

* "Migration is needed because Wiki is not being used now that GitHub is being used. Maintaining the Wiki in addition to GitHub is not sustainable. So we want documentation to move from Wiki to GitHub. So that when an activity is updated in GitHub, the documentation can be updated in the same place at the same time."

* "Migration is needed because Wiki is not being used now that GitHub is being used. Maintaining the Wiki in addition to GitHub is not sustainable. So we want documentation to move from Wiki to GitHub. So that when an activity is updated in GitHub, the documentation can be updated in the same place at the same time."<br />

* “Originally documentation was separate because we had non-coding developers and tool chains that varied by type of developer.  Now we use GitHub the tool chains are combined. With the project as described, documentation will be concentrated in the source code repository for an activity, reducing ongoing maintenance.We have less active Wiki contributors than we ever did, and in the current threat environment a Wiki requires significant monitoring and administration; we recently lost some system administrators and gained new ones; using GitHub allows us to outsource system administration.”

* “Originally documentation was separate because we had non-coding developers and tool chains that varied by type of developer.  Now we use GitHub the tool chains are combined. With the project as described, documentation will be concentrated in the source code repository for an activity, reducing ongoing maintenance.We have less active Wiki contributors than we ever did, and in the current threat environment a Wiki requires significant monitoring and administration; we recently lost some system administrators and gained new ones; using GitHub allows us to outsource system administration.”<br />

'''Answer 4:''' Tony Anderson - quozl@laptop.org <br />

'''Answer 4:''' Tony Anderson - quozl@laptop.org <br />

(His comments clarifying the need of WikiPort and the problems it solves)

(His comments clarifying the need of WikiPort and the problems it solves)<br />

As always, the question is the impact on our users. The traditional source of information for users is [1] and [2] and, especially the wiki pages. So far the effect of gitHub has been to reduce the value of these two sources. In many cases the activities on ASLO have been superseded by ones on Github other git repository but are not available to our users. The documentation of activities on ASLO has never been adequate but now no effort will be made to improve it. This continues the trend toward Sugar being a playground for the technical elite. Complete conversation available here.

As always, the question is the impact on our users. The traditional source of information for users is [1] and [2] and, especially the wiki pages. So far the effect of gitHub has been to reduce the value of these two sources. In many cases the activities on ASLO have been superseded by ones on Github other git repository but are not available to our users. The documentation of activities on ASLO has never been adequate but now no effort will be made to improve it. This continues the trend toward Sugar being a playground for the technical elite. Complete conversation available here.<br />

[1] http://www.sugarlabs.org [2] http://www.laptop.org

[1] http://www.sugarlabs.org [2] http://www.laptop.org<br />

'''What will you do if you get stuck on your project and your mentor isn't around?'''<br />

'''What will you do if you get stuck on your project and your mentor isn't around?'''<br />

I strive to solve a problem using my own skill base by searching about the problem case and working it out into smaller bits.

I strive to solve a problem using my own skill base by searching about the problem case and working it out into smaller bits.

#sugar and #sugar-devel channels on IRC, the mailing lists where other community members discuss issues. I am familiar with mailing list etiquettes for open source communities and learn fairly fast.

#sugar and #sugar-devel channels on IRC, the mailing lists where other community members discuss issues. I am familiar with mailing list etiquettes for open source communities and learn fairly fast.<br />

Google and StackOverflow about the issues, later refer to the documentation of the tool I am using for reference.  

Google and StackOverflow about the issues, later refer to the documentation of the tool I am using for reference.  

'''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?''' <br />

'''How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?''' <br />

I would get regular, constructive feedback on the code I will write and the work I would do for the community by posting work samples from Github, on the mailing list and on IRC. [Check Timeline for the same]

I would get regular, constructive feedback on the code I will write and the work I would do for the community by posting work samples from Github, on the mailing list and on IRC. [Check Timeline for the same]<br />

Post constant updates on my blog and maintain an update tracker for each week on a public notepad (Etherpad, etc.)

Post constant updates on my blog and maintain an update tracker for each week on a public notepad (Etherpad, etc.)

Another Issue that I am currently working  is [https://github.com/sugarlabs/sugar-live-build/issues/6 sugar-live-build/issues/]  

Another Issue that I am currently working  is [https://github.com/sugarlabs/sugar-live-build/issues/6 sugar-live-build/issues/]  

'''Describe a great learning experience you had as a child.'''

'''Describe a great learning experience you had as a child.'''<br />

Here’s a short story titled “Let me Google that for you.” when I was 14.  

Here’s a short story titled “Let me Google that for you.” when I was 14. <br />

From my childhood, web technologies have always piqued my interest for the longest time as I can remember. I been writing HTML since I was 1. But I never liked to read from the old, dusty books. When I code, I had to take help from seniors, teachers, the experience I gained and other sources. Almost everybody was irritated by the constant barrage of long and complex questions, that Vipul Gupta had.

From my childhood, web technologies have always piqued my interest for the longest time as I can remember. I been writing HTML since I was 1. But I never liked to read from the old, dusty books. When I code, I had to take help from seniors, teachers, the experience I gained and other sources. Almost everybody was irritated by the constant barrage of long and complex questions, that Vipul Gupta had.

'''Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?'''<br />

'''Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?'''<br />

* I think I am well satisfied with the proposal that I have made for WikiPort, the project for Sugar Labs. The template given by Sugar Labs really covers all the corners of my  project, and actually helped me think more constructively about the project and the fine aspects of it.  

* I think I am well satisfied with the proposal that I have made for WikiPort, the project for Sugar Labs. The template given by Sugar Labs really covers all the corners of my  project, and actually helped me think more constructively about the project and the fine aspects of it. <br />

* I learned a lot through these few weeks, working on the proposal. MediaWIki API and new skills, contributing to an open-source organisation of this stature, how to interact with people. This has been a memorable experience. I am in awe, I really am.

* I learned a lot through these few weeks, working on the proposal. MediaWIki API and new skills, contributing to an open-source organisation of this stature, how to interact with people. This has been a memorable experience. I am in awe, I really am.<br />

* All open-source communities may not be same, but are run on the same principle that I also try to follow in life. Be humble, and helpful to everybody. The ‘ahaa-moment’ of a beginner is what I live for, when he truly get the point that I am trying to make.

* All open-source communities may not be same, but are run on the same principle that I also try to follow in life. Be humble, and helpful to everybody. The ‘ahaa-moment’ of a beginner is what I live for, when he truly get the point that I am trying to make.<br />

* Some Credits - Learned to not contest for issues, but focus on better PR’s, and many new things from James Cameron (@Quozl)’s blog. Jasikrat too for helping people on IRC emailsll mentors who review our proposal and go through all our mails. Thank you all for the opportunities and the help provided to me and my fellow contributors. I hope down the line, I could follow in your footsteps too.

* Some Credits - Learned to not contest for issues, but focus on better PR’s, and many new things from James Cameron (@Quozl)’s blog. Jasikrat too for helping people on IRC emailsll mentors who review our proposal and go through all our mails. Thank you all for the opportunities and the help provided to me and my fellow contributors. I hope down the line, I could follow in your footsteps too.<br />

__NOEDITSECTION__

__NOEDITSECTION__

__INDEX__

__INDEX__

[[Category:2018 GSoC applications]]

[[Category:2018 GSoC applications]]