[Freeswitch-dev] The Beginners Hurdle
FreeSwitch is an incredible project and I wish I had the knowledge that the developers have in communications. But coming from the position of someone without such a background I find the lack of simple progression of working examples a deterrent to applying FreeSwitch. 500+ pages of documentation, though very useful due to the dynamics of improving code, becomes obsolete, and pages produced by highly knowledgeable persons, even though accurate, often use abbreviations and terms obvious to them providing no description or reference to any glossary. Again a large hurdle to beginners. Now perhaps I misunderstand the difficulty in developing and maintaining a progressive set of examples, as this seems to be a common problem in open-source projects. But beginners are often intimidated and loose heart as it appears that accomplished users consider this necessary technological Darwinism. Note: I find the developers helpful but have not wished to bother them with questions that may be mundane but I have not found assistance from the users group. I would be willing to attempt to develop and "maintain" a series of "working" examples (and educational explanations) with a logical progression from simple to more complex. Initially Windows would be my preferred platform but Linux requirements would next need to be addressed. If there were a single set of progressive examples that those who are willing to help perfect could focus on all users would be advantaged and questions could become more focused and less redundant. Initially I would suggest developing: 1) A list of common FreeSwitch functionality. 2) Determine the most functional implementation (Lua, Postgre SQL, etc.) 2) Develop "working" examples beginning with simple functionality incrementally adding functionality. Any patient takers?
Robert, If you like you can join #freeswitch and we can help you with anything you need. This way we help you... and you improve documentation and it helps everyone in the project moving forward. I honestly do not consider it mundane to help someone thats new to FreeSWITCH. btw Welcome to the party! ;) /b PS: thats irc.freenode.net On Aug 15, 2008, at 9:19 AM, Robert Clayton wrote:
FreeSwitch is an incredible project and I wish I had the knowledge that the developers have in communications. But coming from the position of someone without such a background I find the lack of simple progression of working examples a deterrent to applying FreeSwitch.
500+ pages of documentation, though very useful due to the dynamics of improving code, becomes obsolete, and pages produced by highly knowledgeable persons, even though accurate, often use abbreviations and terms obvious to them providing no description or reference to any glossary. Again a large hurdle to beginners.
Now perhaps I misunderstand the difficulty in developing and maintaining a progressive set of examples, as this seems to be a common problem in open-source projects. But beginners are often intimidated and loose heart as it appears that accomplished users consider this necessary technological Darwinism.
Note: I find the developers helpful but have not wished to bother them with questions that may be mundane but I have not found assistance from the users group.
I would be willing to attempt to develop and "maintain" a series of "working" examples (and educational explanations) with a logical progression from simple to more complex. Initially Windows would be my preferred platform but Linux requirements would next need to be addressed.
If there were a single set of progressive examples that those who are willing to help perfect could focus on all users would be advantaged and questions could become more focused and less redundant.
Initially I would suggest developing: 1) A list of common FreeSwitch functionality. 2) Determine the most functional implementation (Lua, Postgre SQL, etc.) 2) Develop "working" examples beginning with simple functionality incrementally adding functionality.
Any patient takers?
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
Brian West sip:brian@freeswitch.org
Brian, Thank You. In monitoring communications over the past months you willingness to assist is quite obvious. Yet I have the fear that if developers are very open to questions they have less time to develop. I was just wondering if there could be a system that would reduce redundant question to you. For example maybe a format where questions and answers were attached to examples would allow individuals to see if their question was asked/answered before and what points they may be overlooking. Also it becomes obvious when the answers cease that this particular piece documentation has been abandoned. On Fri, Aug 15, 2008 at 10:33 AM, Brian West <brian@freeswitch.org> wrote:
Robert, If you like you can join #freeswitch and we can help you with anything you need. This way we help you... and you improve documentation and it helps everyone in the project moving forward. I honestly do not consider it mundane to help someone thats new to FreeSWITCH. btw Welcome to the party! ;)
/b PS: thats irc.freenode.net
On Aug 15, 2008, at 9:19 AM, Robert Clayton wrote:
FreeSwitch is an incredible project and I wish I had the knowledge that the developers have in communications. But coming from the position of someone without such a background I find the lack of simple progression of working examples a deterrent to applying FreeSwitch.
500+ pages of documentation, though very useful due to the dynamics of improving code, becomes obsolete, and pages produced by highly knowledgeable persons, even though accurate, often use abbreviations and terms obvious to them providing no description or reference to any glossary. Again a large hurdle to beginners.
Now perhaps I misunderstand the difficulty in developing and maintaining a progressive set of examples, as this seems to be a common problem in open-source projects. But beginners are often intimidated and loose heart as it appears that accomplished users consider this necessary technological Darwinism.
Note: I find the developers helpful but have not wished to bother them with questions that may be mundane but I have not found assistance from the users group.
I would be willing to attempt to develop and "maintain" a series of "working" examples (and educational explanations) with a logical progression from simple to more complex. Initially Windows would be my preferred platform but Linux requirements would next need to be addressed.
If there were a single set of progressive examples that those who are willing to help perfect could focus on all users would be advantaged and questions could become more focused and less redundant.
Initially I would suggest developing: 1) A list of common FreeSwitch functionality. 2) Determine the most functional implementation (Lua, Postgre SQL, etc.) 2) Develop "working" examples beginning with simple functionality incrementally adding functionality.
Any patient takers?
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
Brian West sip:brian@freeswitch.org
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
On Aug 15, 2008, at 9:53 AM, Robert Clayton wrote:
Brian, Thank You.
In monitoring communications over the past months you willingness to assist is quite obvious. Yet I have the fear that if developers are very open to questions they have less time to develop.
Well my job on the project is to do just this. I answer and filter out questions before they make it to the devs. Many others including Ray and Myself do this most of the day. So it's no problem. See if you ask it.. and it gets documented then we don't get asked again usually. Which in the long run the pay off is much better. ;)
I was just wondering if there could be a system that would reduce redundant question to you.
The FAQ and Wiki?
For example maybe a format where questions and answers were attached to examples would allow individuals to see if their question was asked/answered before and what points they may be overlooking. Also it becomes obvious when the answers cease that this particular piece documentation has been abandoned.
Just ask is the best way to get involved. The weekly conference calls are for this also. Bring up things that need to be documented.. fixed.. changed.. updated.. Brian West sip:brian@freeswitch.org
We are all in "amazed" of the rich features and true innovations within FreeSwitch. Kudos to the FS project and its developers. Count me in, as one to assist . -E
participants (3)
-
Brian West
-
EdPimentl
-
Robert Clayton