Note: Currently new registrations are closed, if you want an account Contact us

Challenges

From FSCI Wiki
Revision as of 22:40, 10 December 2006 by Pravs (talk | contribs) (→‎Links to mailing list topics: foss-in and glug-bom added)

Patching FOSS in India

Solving the fundamental structural problem of the free software movement in India

A multilog of developers, evangelists and students

The discussion was started in the panel discussion on '10 years of linux in India' on day 2 of FOSS.IN 2006 and continued on day 3 with a BoF on 'Patching FOSS in India'.

BoF details

Day 3 (26 Nov 2006) 2:00 pm

Moderators: Thaths/Fred

Complacency

Big IT boom in India gives people jobs easily; and when you do a cosy job, you lose half of the motivation. It is a case of innovation being killed due to complacency.

Social Setup

As a society, there is a lot of pressure on people to be successful immediately; and success here means making money. This means that if one were to tread the road not taken, one has to withstand the pressure from friends, family, relatives blah blah blah. What adds to this is the lack of knowledge about FOSS and such things among the common folks (read one's parents, relatives etc).

The whole atmosphere around is counterproductive to innovation and risk taking. Those who fail are not looked upon well by the Indian society. What matters to the society in India is success; the means does not matter.

We also are not trained to think in a creative manner. Succumbing to authority comes more natural to Indians rather than being free and think freely. Of course there are exceptions, but in general as a rule.

Bandwidth

Only available in metros? Lack of introuctory materials in an easily accessible (printed) form.

Consumer Mentality

We should encourage people develop a producer culture.

Develop a "Good User" culture.

(a) A good user reacts to all glitches by filing a "Good Bug Report" --- (need a link here on how to write good bug reports).

(b) A good user reacts to inactivity on her bug by the maintainer by providing a fix :-)

(c) A good user does not hesitate. If you fear that you will make a mistake and do not speak that will be a mistake.

Perfectionist attitude

People wait for perfection before release.

No patches and many forks

Hesitation to submit patches upstream.

Lack of awareness about bounties

Google Summer of Code, Redhat scholarship, Novell internship, NRCFOSS projects ...


Even with all these challenges we have some contributors which we can be proud of.

Links to mailing list topics