User:YLiu

Revision as of 02:26, 8 June 2016

Ying Liu

Dr. Ying Liu is an Assistant Professor in the Division of Computer Science, Mathematics and Science within the College of Professional Studies at St. John's University.

Dr. Ying Liu teaches graduate and undergraduate computer science courses, including programming, operating systems, database systems, networking, software design method and software engineering.

Dr. Liu’s scholarly interests span Data Mining, Text Mining, Big Data Analytics, and their applications.

In his spare time, Dr. Liu likes enjoy jogging and soccer.

Intro IRC Activity:

• How do people interact?

People interact through communication. Communication can be done through various forms, such as in-person, phone call, video call, text messaging and e-mails.

• What is the pattern of communication? Is it linear or branched? Formal or informal? One-to-many, one-to-one or a mix?

I think most of the communication is linear. We communicate with others and wait for responses from others. Communications can be one-to-one or one-to-many or a mix.

• Are there any terms that seem to have special meaning?

There are terms which have special meaning, e.g. #info, #action tags.

• Can you make any other observations?

Communication could be become very challenging when it is many-to-one or many-to-many.

Guided Tour

Sugar Labs Project

• Contributions:

I think my role will be mainly a Developer, who get the source code, test & break Sugar, design & build Sugar, file bugs, fix bugs, build packages, develop new features, test, design, develop & help maintain activities, toolchain, scripts.

• Tracker: On your wiki page describe the general process for submitting a bug and indicate the types/categories of tickets listed on this page as well as the information available for each ticket. A ticket should be prepared on the trac instance and then if braod attention to the issue is desired it should be announced with a link on the sugar-devel list serve. Tickets appear to be classified as either "defect" or "enhancement". Information is also available such as a summary of the issue, the status of the ticket (new/accepted/assigned/reopened/closed), who created the ticket (reporter), who owns (i.e. is responsible for) the ticket, the priority of the ticket and the milestone by which the ticket is targeted to be addressed. Significant additional information is available by clicking through to the ticket specific page. In particular, the full Description and the Change History would be valuable to a developer working on the issue. • Repository: Can you determine from the information provided here whether the project uses a web-based common repository or a local repo? The repo is hosted by Gitorious, which provides free hosting for git based open source projects. • Release Cycle: Include an entry on your wiki page that describes how the release cycle and roadmap update are related. The roadmap is updated by the development team at the start of each release cycle. The release cycle goes through development, beta, release candidate and final release versions. Sahana Eden Project • Community: are there any commonalities? Is there something distinct for each type of contributor? How is this structure different than the one you found on the Sugar Labs website? The "get started straight away" section is a nice addition and makes it easy to quickly find something to work on. It is nicely divided into code/documentation/outreach/QA/UI tasks. For students and use in a class the "Easy Bugs to Fix" section is a great feature. In general there seems to be extensive support for new developers including documents and video training. This should make it easier to get rolling with Sahana than many other projects. • Tracker: How is the information here different than the information found on the Sugar Labs tracker page? The information in the "Active Tickets" report is very similar to that in the Sugar Labs tracker. The most notable difference is that tickets are associated with particular components. This will allow developers to more quickly identify tickets to which their expertise may be best applied. Each ticket's creation date is also displayed in the report, making it easier to identify both new and old issues. The immediate availability of a variety of commonly useful reports (e.g. Active Tickets, Easy Bugs, Feature Requests, etc) may be useful as well. • Repository: Can you determine from the information provided here whether the project uses a web-based common repository or a local repo? To install Eden git is used with a repository location on ghithub.com. Thus, this project uses a web-based common repository for the trunk. Developers fork the repository, make changes to their local repository, contributing changes back when complete. • Release Cycle: Information about Sahana Eden's release cycle and roadmap can be found here. Include an entry on your wiki page that describes the information you find here. The first thing that jumps out is that the milestone 0.9.0 "Medway" is "4 years late", though not particularly surprising or concerning, given the nature of the project. Plans for several future milestones are laid out in bulleted lists of the key features and tickets are tracked with respect to which milestone to which they apply.