Success-Abandonment-Classification

Created: 2008-02-06 14:35:41 Last updated: 2008-07-02 17:15:25

Download Workflow

This is a draft of an analysis workflow to replicate the Free/Libre Open Source Software project classification analysis from English & Schweik. The workflow is not yet functional. The original research uses a selection of FLOSS project metrics to classify projects as successes or abandonments in their initial or growth phases. Translation of the original classification as described in the paper to a workflow analysis requires some modification of the way criteria are applied to achieve exhaustiveness. In addition, this version of the analysis parameterizes all of the classification criteria to enable exploration of different threshold values.

The main aspects of the workflow that are currently incomplete are data selection and code for the classifier component. Unincorporated progress on workflow development includes some SQL queries for data selection and a reformulated classification criteria set. Assumptions include using a month unit for all time-based criteria, and restriction of classification to the six classes from the original paper.

Desired output will be a CSV that will include all derived metrics used for classification as well as an indicator of the specific combination of metrics that results in the final classification, as there are multiple combinations of metrics that can result in any given classification. Extended development of the workflow will incorporate additional RServe components to provide in-depth analysis of the classified data.

English, R. and Schweik, C.M. 2007. "Identifying Success and Tragedy of Free/Libre and Open Source (FLOSS) Commons: A Preliminary Classification of Sourceforge.net projects." Paper accepted for the First International Workshop on Emerging Trends in FLOSS Research and Development that is part of the 29th Int. Conference on Software Engineering. May 21st, 2007.

http://people.umass.edu/cschweik/pdfs/English_Schweik_FLOSS_Classification.pdf

Preview

Download as scalable diagram (SVG)

Run

Run this Workflow in the Taverna Workbench...

Option 1:

Copy and paste this link into File > 'Open workflow location...'
http://www.myexperiment.org/workflows/140/download?version=1
[ More Info Expand ]

Workflow Components

Inputs (1)

Name	Description
Project_Names

Processors (9)

Name	Type	Description
initiation_age_threshold	stringconstant
mortality_threshold	stringconstant
download_threshold	stringconstant
release_recency_threshold	stringconstant
release_lag_threshold	stringconstant
Fetch_Data	abstractprocessor
Assemble_Data	abstractprocessor
Classification	rshell
Compute_Project_Stats	rshell

Beanshells (0)

Outputs (1)

Name	Description
Classification_Output

Links (16)

Source	Sink
Project_Names	Fetch_Data:projects
Assemble_Data:data_for_classification	Classification:data_for_classification
Compute_Project_Stats:number_releases	Assemble_Data:number_releases
Compute_Project_Stats:time_between_releases	Assemble_Data:time_between_releases
Compute_Project_Stats:time_since_last_release	Assemble_Data:time_since_last_release
Compute_Project_Stats:time_since_reg	Assemble_Data:time_since_reg
Fetch_Data:data_collxn_date	Compute_Project_Stats:data_collxn_date
Fetch_Data:downloads	Assemble_Data:downloads
Fetch_Data:registration date	Compute_Project_Stats:registration_date
Fetch_Data:release_dates	Compute_Project_Stats:release_dates
download_threshold:value	Classification:download_threshold
initiation_age_threshold:value	Classification:intiation_age_threshold
mortality_threshold:value	Classification:mortality_threshold
release_lag_threshold:value	Classification:release_lag_threshold
release_recency_threshold:value	Classification:release_recency_threshold
Classification:classified_data	Classification_Output

Coordinations (0)

Information Workflow Type

Taverna 1

Information Uploader

Andrea Wiggins

Information License

All versions of this Workflow are licensed under:

Information Version 1 (earliest) (of 3)

Information Credits (2)

(People/Groups)

Information Attributions (0)

(Workflows/Files)

None

Information Tags (7)

Uploader tags

Log in to add Tags

Information Shared with Groups (1)

Free/Libre Open Source Software

Information Featured In Packs (1)

FLOSS Research Analyses

Log in to add to one of your Packs

Information Attributed By (0)

(Workflows/Files)

None

Information Favourited By (3)

Information Statistics

9926 viewings

11681 downloads

[ see breakdown ]

Citations (0)

None

Version History

In chronological order:

FLOSS Success-Abandonment Classification

Created by Andrea Wiggins on Wednesday 06 February 2008 14:35:41 (UTC)

Last edited by Andrea Wiggins on Monday 11 February 2008 16:50:39 (UTC)
Success-Abandonment-Classification

Created by Andrea Wiggins on Wednesday 06 February 2008 14:35:41 (UTC)

Last edited by Andrea Wiggins on Thursday 19 June 2008 02:14:31 (UTC)

Revision comment:

This version of the classifier is fully functional, drawing on data from FLOSSmole and the Notre Dame SourceForge repositories. The thresholds for classification decisions are set as string constants, which you can change as you like.

In addition, this workflow offers three versions of the recent release rate classification: the original version (first_last) based on the time between first and last releases; an averaged version (average_rate) which uses the average time between releases, and a version suggested by English & Schweik as future work (recent_density), which uses the time between the last X releases where X is the threshold number of releases to be considered successful.
Success-Abandonment-Classification

Created by Andrea Wiggins on Wednesday 06 February 2008 14:35:41 (UTC)

Last edited by Andrea Wiggins on Wednesday 02 July 2008 17:15:25 (UTC)

Revision comment:

This revision replaces the large RShell classifier component with a series of Beanshell components that execute the pre-classification criterion comparisons, do the project classification, and assemble a nice CSV output for ad-hoc analysis.

Reviews (0)

No reviews yet

Be the first to review!

Comments (1)

View Timeline

Log in to make a comment

Khalid Belhajjame

I quite the way this workflow is designed. The author used nested-workflows to favor modularity, and the data links seems to be carefully designed. On the downside, I couldnt execute teh workflow, which may be due to the fact that some constituent services are no longer available. Would be good if the author (or someone knowledgeable) to repair and create a new version of this workflow :-)

khalid

Other workflows that use similar services (0)

There are no workflows in myExperiment that use similar services to this Workflow.