Re: Probably definitive version of "what can I do?"

[Darin Lang <darin@flashcom.net>]

on 6/12/01 7:50 PM, Jean Francois Martinez at jfm2@club-internet.fr wrote:

> Here is a revised version of the "What can I do for Indy?"


> 
> I hope it is definitive
> 
> JFM
Here is a revised revised version. It reads better in English.

Darin

Darin Lang  mailto:darin@chandeliershop.com
My Web Sites: http://ChandelierShop.com
http://KodiakLodge.com
and Coming Soon----> http://YahooFarm.com

Many people think only programmers can participate in Indy.  Nothing
could be further from the truth.


Of course we really need programmers and if you are interested please contact
me <MYEMAIL> but here is a list of what non programmers can do:

-RPM building (slightly difficult) and maintenance (trivial most of time).

-Technological watch: look at www.freshmeat.net, www.linuxapps.com and
www.appwatch.com and filter the applications which match Indy's
applications guidelines.   

-Investigate applications: one of Indy's basic postulates is that we
 would like to ship only one application for a given task: the best
 one.   Also in some cases there are complementary docs or software which
 greatly improve an application, it would help considerably if after
 investigating you could give us a list of files to be included

-Activism and announcing it in LUGS.  Also improving Indy texts not
 only for syntax but for their impact.  Indy needs people remember?

-Look for resources like tutorials and additional docs

-Write documentation

-Translations

-Organizational work.

-If you are running another distribution than Indy or its parent
 distribution (presently RedHat) write a report about it.

-Testing and critics: it will help us to improve

-Security: Watch for announcements of security holes and, if software is
 Indy specific insert the fix in Indy-updates otherwise contact RPM
 maintainer.