Difference between revisions of "Wishlist"

Q: How can I get X feature added to HylaFAX?

A: Great question! As with most open source software projects, there is no guarantee the work will be added to HylaFAX unless you a) do it yourself, and then b) convince the development team that the change is a "good thing"(tm). Who are the developers? They're those people who subscribe to the hylafax-devel mailing list, and who follow bugzilla and CVS commit logs, and who participate in discussions on some combination of these forums. Everyone's welcome, and people tend to come and go as the mood strikes them. There's some usual supects of course, but newcomers are always welcome. If you think you'd like to introduce a new feature to HylaFAX yourself then please by all means file a bug report and hang a patch at [bugs.hylafax.org] - you're sure to get feedback and if concensus is that the work represents a positive change, it will be committed to CVS.

If you don't fancy becoming a developer yourself, or are more of an idea, or "big picture" person, then file your idea below and perhaps some developer (or developer-to-be) will decide it looks like fun and run with it. If you want to increase the odds that someone will take interest in your feature, you should consider adding a bounty, which is the amount of money you'd be willing to offer a developer to do the work for you.

Things I'd like to see in HylaFAX

• Integrated web-based frontend GUI with the option to upload a standard coversheet and letterhead. Hylafax desperately needs an integrated frontend GUI accessible via any browser that is readily available when Hylafax is installed. This will eliminate the need for fax clients installed on user computers and issues with configuring clients to work with Hylafax, and users can readily access it to send and view received faxes. The uploaded coversheet and letterhead will already contain the user logo, slogan, contact info, etc as desired/designed and the recipient information/coversheet body entered by the sender will be printed on the coversheet, while other page body will print on the letterheaded pages before it actually sends the fax.
• Better documentation of Dialrules. More examples of string replacement, addition. How to accomplish conditional testing with the dialrule regex syntax (eg "if not current area code, and LD code not prepended, add LD code), etc.
• The JobFmt technique seems to be a bit outdated in relation to the sendq files, becaues one doesn't get all the information. As Client-developer i would like to use exactly the same tags available in the sendq files in the jobfmt-string, instead of (or additionally to) those letters.
• LDAP Support for Client/User Authentication: Paul 15:35, 16 December 2005 (EST)
• Mini Webserver for Hylafax Server Status, Job Management: Paul 15:35, 16 December 2005 (EST)
• Destination Routing between multiple Servers in different Countries: Alex 18:33, 30 January 2006 (CET)
• Fax Accept / Reject using both Caller ID and TSI. Possibly referencing CID variables in the tsi file?: User: Gguldens 22:37 22 May 2007(EDT USA)
• A way to accept faxes from known spammers, but make the process slow down, grinding to a near halt. The longer each spammer is on each individual's line, the fewer people they get to spam at the end of the day.
• Support for additional languages encoding for ASCII to postscript conversion in textfmt/TextFormat such as Hebrew and Arabic, so we could fax header pages (incl. automatic fields such as date, sender name, recipient name, company, etc) in those languages.
• direct support to SMTP protocol to use an external Mail server