Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Linux bay



This is just an idea I am putting forward.  Since it cannot be
implemented or maintained by one person I thought of puting this idea in
the public domain.

Thank you for looking into it.

Subba Rao
subba9 at cablespeed.com

===========================================================
www.linuxbay.org

Based on E-Bay success model

Goal -	To reward young contributers to the open source code.
	To develop and reward discipline for open source
		 program development.
	To provide longevity to open source (and possibly shared
		 source) applications.



Step 1
User registration (Last Name & CPU ID are the key)  =  Voting members
	First Name
	Last Name
	Email Address
	Linux CPU ID (unique)
	Screen ID
	Password



Step 2
Developer registration (Group Name & CPU ID are the key)
	First Name
	Last Name
	Programming Group/Company/Association Name
	Mailing Address (Street, State, ZIP code, Country)
	Email Address
	Linux CPU ID (unique)
	Screen ID
	Password

Code Standards
	Should have the funtional items listed in Project file.
	Code should compile cleanly without warnings or errors
		 (i.e no > /dev/null 2>&1 for errors in the Makefiles)
	Code should be documented
	Code should compile and run on the latest released versions
		 of the following major distributions:
	(Slackware, SuSe, Redhat, Mandrake, Turbo Linux, Pacific Linux).
	Code should list the system requirements (package dependencies
		 and such)

Projects (These items are examples only)
	Dia
	OpenOffice
	Snort plugins
	GIMP plugins
	Cluster Management software
	.
	.
	.



Step 3
Project Ratings - Projects are rated by the following contributions
	Functionality added
	Functionality fixed
	Documented functionality
	Test platforms
	Test results



Step 4
Process of project competition
	Developer will register for the project. (Group Name and
		 CPU ID will be the key)
	Developer will work on the project and put the source code
		 back to the archive.
	Registered users will download the new source and test it out.
	If there are any errors
		Registered users/public testers will communicate with the
				 developer the errors discovered.
	else
		Registered users will rate the functionality/code/documentation
				 of the developer
	The highest rated programs will be awarded the Project Prize
		 amount via PayPal

Public contribution to the prize amount
	Public will contribute via PayPal ($1 (local currency) or more)
	(Are there any other online escrow accounts?)

Contestent qualifications
	Coded and contributed the source back to the source tree.
	Must have contributed code atleast twice to the project goal.
	**Contestents cannot contribute for the first time on the final day
		 of the project deadline.




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org