I've made the proposal public. It should be visible now. :) On Wed, Mar 19, 2014 at 12:20 PM, Marcel Raad wrote:

Nikhar Agrawal writes:

...

If there are any visibility issues, kindly let me know.

Only the GSoC mentors & admins can see your proposal.

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

On Wed, Mar 19, 2014 at 12:46 PM, TONGARI J wrote:

2014-03-19 15:03 GMT+08:00 Nikhar Agrawal :

...

I've made the proposal public. It should be visible now. :)

The same URL? I don't think so :/

Oh sorry for the confusion. I thought the link would be the same. The following link should work: http://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/nikhar/57... In case it still doesn't, the following google doc should work (this anyways has better formatting): https://docs.google.com/document/d/1Ylc_OJBpoN_lNgMrYh0l-O_qCb-EDJQy0JGoh5uM...

(Aside: please avoid top-posting)

Sorry for that. Gmail automatically puts the message at the bottom. Didn't pay attention to that. Sorry.

On Thu, Mar 20, 2014 at 6:22 AM, Michael Marcin wrote:

The proposal seems pretty good. There was a discussion of a fixed-point proposal for last year's GSOC that might be relevant.

http://thread.gmane.org/gmane.comp.lib.boost.devel/239971

Hi, Thanks a ton for the thread. I'll go through it and try to make appropriate changes. Though I'm not sure how much time I would have to make any amends to the proposal. Which is of course my fault given that I submitted the proposal a little late for feedback. It's just that I preferred to be more confident about the project before writing the proposal. So I probably spent a lot of time in researching. Is there anything in particular that you'd like me to add to the proposal? Thanks a lot for taking the time to go through it :). Nikhar

On 21 Mar 2014 at 3:37, Nikhar Agrawal wrote:

Wow... there's an incredible wealth of information in the Boost archives on fixed-point. A lot of these concern with a lot of design issues. These discussions should come in really handy. I wish I had come upon these earlier. But never too late I guess.

It's never too late. Far more importantly you asked for help here, got given help, and then made use of that help by doing your own research. That's exactly the kind of student we want for GSoC.

Since my current proposal as it stands seems quite good to you (apart from any particular quibbles you might have which I'm most interested in hearing :) ) and the fact that I don't have much time left to make amendments to the proposal based on reading of these archives, I'll add a time before the community bonding period to the schedule solely to reading of these archives and ponder upon the various design issues discussed. This period lies before selection of the project in GSoC and it doesn't bother me since fixed-point has me very very interested now after all the time spent on it. So, GSoC or not, I would like to implement this library anyways provided of course that no one has any objection to it and no one else is working on it. Having said that though, I would like to hope that my above interest in developing the library regardless of GSoC doesn't hurt my chances of selection in it.

Be aware that I plan to ask this community to rank the proposals this Sunday 23rd. Between submission deadline tomorrow 21st and Sunday I hope to get all the potential mentors to indicate which proposals they like on Melange as this may aid the community when ranking. Hence, any improvements you can make to your proposal before Sunday would be great. Niall --- Boost C++ Libraries Google Summer of Code 2014 admin https://svn.boost.org/trac/boost/wiki/SoC2014

On 21 Mar 2014 at 13:29, Stefan Seefeld wrote:

...

Be aware that I plan to ask this community to rank the proposals this Sunday 23rd. Between submission deadline tomorrow 21st and Sunday I hope to get all the potential mentors to indicate which proposals they like on Melange as this may aid the community when ranking.

I think the schedule you propose is too aggressive. There are quite a few proposals to be reviewed, so I don't think you can expect anyone to do this carefully within two days. Also, I expect this to be an iterative process, with changes applied incrementally following comments gathered from mentors as well as this list.

I only wish people were so thorough! What you'll find is that people only bother glancing over the top fifteen or so ranked applications and simply reinforce the existing rankings. Even already, with just the mentors voting, you can clearly see people simply don't bother voting for the lowest ranked proposals - just me and one other has voted on everything. This phenonomen is well known to the social sciences - basically, the first reviewers (i.e. the mentors) have an outsize effect on the eventual ranking, and it's a Zipf's Law power rule proportion. In other words, what I'm saying is that 80% of the ranking has already happened. You'll find any improvements in the proposals no longer have much effect. Hence I had considered there no point in waiting, especially as we have to figure out what to do about the mentors with four very strong proposals attached to them. Niall --- Boost C++ Libraries Google Summer of Code 2014 admin https://svn.boost.org/trac/boost/wiki/SoC2014