O
OctavioOlguin
Guest
When I'm aproaching a concept, I have learned that the wiki has lots of good readings and stuff. In fact so much, that abrumates the newbie, like me. For instance, I'm reasearching all about the OERA, and found on development.wiki lots of documents, so much that is not easily handled, even more if you are start learning and don't have the big picture in your head, yet... Spent all day yesterday trying to organize documents, started by the good "Implementing The OERA, 1,2 ,3 and 9 by Mr Sadd... I think there should be 4-8 chapters, but didn't found them... well, after 6 or 7 pm, I found the second release of these same documents, so all work done so far was some kind of wasted effort. As I write this Idea, I find Mr. James Palmer has addressed same concerns in this post (https://community.progress.com/community_groups/products_enhancements/i/community/pool_of_knowledge.aspx). What I found be very handy and it drives our study in a well structured form is something, like ProductDocumentation did on https://community.progress.com/community_groups/openedge_general/w/openedgegeneral/1117.openedge-educational-videos.aspx. So what I propose is a new group named something like "Roadmap Group" where sumarizes some kind of structuration to the vast amount of docs, and helps new guys, like me to find it's way to the real knowledge, and perhaps the posts there are somekind of "sticky" ones, as on other forums, and it would not be open to posting by us, just to branch out to the related stuff. My $0.02. Thanks.
Continue reading...
Continue reading...