On Thu, May 30, 2013 at 8:28 PM, Christopher Sean Morrison <[email protected]> wrote:
> I'm glad to hear that you are interested in feedback. I presume you'd like > the feedback in private since you didn't specifically state otherwise. If > you'd like it to be public, you are welcome to forward any response to the > brlcad-devel mailing list. On to your feedback... I forget to write "public" here. I will be glad if some one can learn from my mistakes. and it is open source community why I remain private here. > The technical detail in your proposal was good. Overall, it's clear that > you put a lot of time and effort into your proposal and it's an active area > of interest. Your proposal expanded on our idea well enough and you > certainly seem to have a fully capable background. You clearly have strong > coding skills and have the potential for being a fantastic open source Thanking you so much for your feedback. > developer that we'd love to work with. There was even a sponsoring > developer interested and they were willing to mentor you. Can I get a chance to work with developer now? because I want to continue my work on proposal. > So what went wrong? > > The biggest detriment to your application was your communication skills. > Open source participation is *predominantly* about communication and this is > an area that needed improvement. Some of the language mistakes were easily > attributed to English not being your proficiency and that by itself would > have been JUST FINE and understandable. However, the *style* of your > writing exceptionally lacked attention to detail. For example, you use > uppercase seemingly randomly throughout and punctuation was very > inconsistent. Basically, this made your proposal seem very "messy". I admit my mistakes. <snip> > This is not meant to be one-sided feedback. If you have questions or > comments of your own, please don't hesitate to engage me in discussion. > Myself and other developers are more than happy to help you become a better > developer. This is my first attempt to involve with an open source community. I want to learn more things and getting involved to such a good community. > For the near term, I urge you to learn to notice the inconsistencies in your > writing (code or otherwise). It sometimes takes time and practice if it's > just something you just don't yet "see". You might want to make yourself a > checklist of things to consider when you write a piece of code like asking > yourself whether the case and whitespace are consistent, making sure you > compile, making sure you check placement of curly braces, comments, > parentheses, commas, indentation, etc. A good first step might be to try I will take care of these things from now onwards. -- Navdeep Bagga Happy Bird [W] http://navdeepbagga.com [T] http://www.navdeepbagga.com/category/daily-diary-3/ ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
