On Sun, May 11, 2008 at 1:20 AM, Michael Tinsay <[EMAIL PROTECTED]> wrote: > Does one have to contribute code to be said to be a contributor to a FOSS > software?
This has always been a misconception on a participatory cultured community like FOSS. A set of FOSS code like an API is not useful without proper documentation; its not going to have mileage it doesn't have advocates marketing it; and most important, it won't be known in the world if its not online. These are low-barrier groups that people can jump in and not worry about contributing code. Its also possible that code patches do not get accepted in mainline for various reasons, so attacking the core might not be a good option for starting contributions (unless you really know what you are doing or you started the project on your own). I think globally, there is this thinking that its not cool to contribute to such subprojects and still would like to have that geek pride, bragging rights of sorts. That's quite fine to desire such, but I have seen a lot of "drive-by" contributors who just want to be part of the release notes or history and never come back. But I'm not complaining, a fix is still a fix no matter the intentions. -- Jerome Gotangco _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List http://lists.linux.org.ph/mailman/listinfo/plug Searchable Archives: http://archives.free.net.ph
