[Nexus 7 Q&A, Help & Troubleshooting] chrisftw92:
Really?

"Module CPU4000 Core Skills

OSS Assignment

Interacting with an Open Source Software Development Community

Marks from this assignment will contribute 50% of the overall mark for the module.

Aims

•	to develop awareness of the process of open source software (OSS) development.

•	to develop confidence and initiative in interacting with an OSS development community.

•	to display skills in verbal communications.

Task 1 Start and maintain a diary or blog

Start a diary or set up a blog for the assignment and continue to post entries throughout. Keep a record of everything you do towards the assignment and every response from the community.

Task 2. Find a suitable Open Source Software Development Project

Find an active open source software application in an area that interests you.

A few examples of areas where one or more sites have already proved suitable are given below, but you should not feel restricted to these areas alone.

personal finance package	currency converter

music editor / mixer	music instrument tutor e.g. guitar

music synthesis	media player

image manipulation and tagging	video editor / standards converter

text editor	web development / web browser

game (various)	game development environment

flight simulator	desktop publishing

integrated office package	social networking

language translation	blog

code development environment	architectural design package

mobile device app development	operating system

virus checker	screen grabber / recorder

voice over IP system	project management

database management system	email package

Some examples of where to look for OSS development projects are:

Sourceforge

Apache Software Foundation

Mozilla Foundation

Google code

Eclipse Foundation	(also via Google code)

Ohloh

Search engine (any)	search for <open source> followed by keywords

describing an applications that interests you.

To determine whether the development community is active, locate the forum or reporting part of the site and check the dates of recent postings and responses. Also check the analysis and metrics for the project at

If the application is clearly inactive, make a note of what you have found, but then STOP and look for something else. It is quite normal to find that your first choice of site is inactive, so don't leave it too long before you reach that conclusion and move on. If you post a question and nobody has replied after a few days, it’s time to move on.

Task 3. Do something to interact with the community

Here are a few examples:

•	Work through a tutorial or some other documentation. Find something that is unclear, confusing, or is out of date, and write an amendment. Submit your improved version.

•	Become familiar with the application. Then pick a question that has been posted on a forum, investigate the issue raised and post a comment either answering the query satisfactorily, or contributing in some way that will help others work towards a solution.

•	Investigate an existing bug report and try to duplicate the circumstances that gave rise to the problem. Then make a change to something and see if the bug is repeatable. Try to narrow down the circumstances when the bug will / will not appear. Report your findings to the development community.

(This is known as 'reducing' a bug. For an explanation and an example of a list of known bugs in a project, see: )

•	Download some software or some small element (e.g. a library function) and get it working properly. Devise some tests and write up the results. If the software doesn't perform exactly as described in the documentation, take action as appropriate: if you are unsure, post a question on a forum, but check for previous reports first. If you are quite sure, submit a bug report describing the circumstances, or amend the documentation and submit the revised version to the community. Follow up the response.

•	Specify improvements or suggest one or more new features that you would like added to the software.

There are many possibilities and so you should not be limited by these suggestions. What is important is that you interact in a constructive manner with an OSS development community.

Task 4. Make a presentation

Make a short presentation to the class, describing what you have done and the nature of the interaction that took place. The presentation should last about 5 minutes, after which you should invite questions.

Describe what you have done and the nature of the interaction that took place. Include evidence of your contribution, either by linking to the website where your work is apparent, or by screen shots.

Explain the choice of package and the evidence that convinced you the community is active. If you started to investigate a project that subsequently proved to be unsuitable, briefly mention the details and the reason why you abandoned it.

Date of Presentations: Week commencing Monday 3rd December

The presentation may be recorded to show the External Examiner.

Marking Scheme

Nature and depth of the interaction	50%

Presentation	50%

Grade A:	Substantial and serious interaction described in an exemplary presentation

Grade B:	As above, but less of an interaction, or with some deficiencies in presentation

Grade C:	As grade A, but the interaction was minor or there were some serious deficiencies in the presentation.

Grade D:	Trivial interaction and/or serious deficiencies in the presentation.

Grade E or F: No interaction and/or very poor presentation.

Any Questions?

If in doubt, don’t struggle. Come and see me in room C2-7a. Roy Attwood

File: Core-Skills-OSS-assignment-Sept12.doc

Updated 16 Oct 2012 RA

"

For a blog ey?