Hylafax Developers Mailing List Archives
|
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[hylafax-devel] Re: Pep talk
On Thu, Aug 10, 2000 at 02:27:56AM -0400, Darren Nickerson wrote:
>
> Personally, I think your ideas are positive ones. At the end of the day, the
> most crushingly absent resource is people who are sufficiently experienced to
> hack on HylaFAX code. I agree, the website is an important public-facing aspect
> of the project which is by now pretty stale. I welcome suggestions on how to
> attrack the type of volunteer who might be able to make a difference in that
> regard.
Regarding developers, I understand. There are probably a lot of factors
affecting the lack of HylaFAX developers. I think we should do our best to
make HylaFAX easy to install and configure. This will grow the user base.
Out of the user base will come developers. It's also importatnt that the
public-facing communication channels (website and mail lists) remain active
and up-to-date. Having the appearance of a dead project will not grow the user
base.
As for what I've volunteered, a bug tracking database will give focus
to development efforts. It may even attract more developers to the group.
Perhaps there are some out there who don't know where to start or what to
work on. With a public list of bugs, they can see what needs to be
worked on and will hopefully pitch in. It may even cause me to do some
development. My problem is time. If I see a 'small' bug that I could fix
in the spare time I have, I may do so. Right now, I don't know what needs
work and HylaFAX is too big to just jump into the source without a reason.
-joe
____________________ HylaFAX(tm) Developers Mailing List ____________________
To unsub: mail -s unsubscribe hylafax-devel-request@hylafax.org < /dev/null