From 773c90513aaa58425dee2204aabf8be0bd23378c Mon Sep 17 00:00:00 2001 From: Yury Delendik Date: Sat, 3 Aug 2013 10:16:52 -0700 Subject: [PATCH] Updated Frequently Asked Questions (markdown) --- Frequently-Asked-Questions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Frequently-Asked-Questions.md b/Frequently-Asked-Questions.md index 148f796..49ac061 100644 --- a/Frequently-Asked-Questions.md +++ b/Frequently-Asked-Questions.md @@ -115,6 +115,6 @@ Yes. The PDF.js will attempt to recover usable PDF data (pages, content, or font ## I have a really great idea. Where is the best place to record it? -The best place is our dev-pdf-js@lists.mozilla.org mailing list. You can subscribe to it using [lists.mozilla.org](https://lists.mozilla.org/listinfo/dev-pdf-js) or [Google Groups](https://groups.google.com/group/mozilla.dev.pdf-js/topics). This way you will reach not only developers. +The best place is our dev-pdf-js@lists.mozilla.org mailing list. You can subscribe to it using [lists.mozilla.org](https://lists.mozilla.org/listinfo/dev-pdf-js) or [Google Groups](https://groups.google.com/group/mozilla.dev.pdf-js/topics). This way you will reach not only developers. As alternative, you can join our [weekly engineering meeting](https://github.com/mozilla/pdf.js/wiki/Weekly-Public-Meetings) to discuss new ideas for the project. The issue tracking system is designed to record a single technical problem. A bug report is something where a developer/contributor can work on. And [github issues](https://github.com/mozilla/pdf.js/issues?state=open) is not a good place for general, not well thought out, or unworkable ideas. Most likely a discussion-type issue will not be addressed for long time or closed as invalid. \ No newline at end of file