Am Dienstag, den 17.02.2009, 20:47 +0100 schrieb Søren Hauberg:
> tir, 17 02 2009 kl. 19:34 +0000, skrev [email protected]:
> > Is there a way to see more precisely what "maintaining" means?
>
> That is a very good question! Well, the minimal way to maintain a
> package is to
>
> 1) Apply patches to the package that users supply.
> 2) Release the package when enough changes has been made.
>
> Of course it is nice if the maintainer also actively develops the
> package, but I'm not expecting this. If the maintainer also attempts to
> answer questions related to the package, then this is helpful as well,
> but I believe this is (and should be) a community task, so I don't think
> this is required by the maintainer.
>
> So, in terms of hours per week, this is a fairly small task. I'm hoping
> that releasing a package will take less than an hour. The other tasks
> really depends on the popularity of the package.
>
> So, I think a minimal maintenance is very light on time requirements.
> But this is just my opinion. Perhaps other people fell differently?
Just a note as a distribution maintainer: an important asset is the
ability to say "NO". Especially feature requests tend to become an
ever-growing pile, so saying "stop" is really helpful. Otherwise, you'll
start fixing other people's problem.
Thomas
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Octave-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/octave-dev
