From: Matias Capeletto (matias.capeletto_at_[hidden])
Date: 2006-05-01 00:59:27
I am finishing my application to the (M)ulti (I)ndex (S)pecialized
(C)ontainers (from now on MISC, do you like it?) for the SoC.
I am constructing a quickbook with a formal proposal, interface
design, project plan and personal information. I want to share it with
the list. I will really appreciate some feedback before sending the
application, specially from Joaquin. Can i post it here when it is
The past two days i learned how to use the tools that boost is using
to compile and generate docs (build v2 and quickbook+doxygen). I first
want to thanks to the developers of this tools, they are pretty
amazing. I do not know if this is the place to say something about the
docs of how to install this two tools, correct me if it is not so the
next time i post it in the right place.
I lost a lot of time trying to make build v2 work because i download
it separately and my user-config.jam was not being read because bjam
was parsing a user-config.jam in the /boost/tools/build/v2/ folder.
Maybe this is in the docs and i do not find it.
The boostbook documentation have a very nice list of things to do in
order to get doxygen and other stuff working with build v2. I endless
look for something like this in the quickbook documentation and was
not able to find it.
Now that i know how to do it, all the process seems straight forward,
it will be possible to add this two things to the documentation?
On 4/29/06, JOAQUIN LOPEZ MU?Z <joaquin_at_[hidden]> wrote:
> ----- Mensaje original -----
> De: Matias Capeletto <matias.capeletto_at_[hidden]>
> Fecha: Sábado, Abril 29, 2006 4:54 am
> Asunto: Re: [boost] [SoC] Specialized containers with Boost.MultiIndex
> > Hi, all, especially Joaquin...
> > I am planning to submit an application to SoC. I will love to make
> > realthe specialized containers you mention and try to include some
> > useful others.
> > Is the list the place to talk this about of?
> Hello Matías, good to know a Spanish-speaking fellow,
> we're only a handful round here.
> The way SoC is organized, I think the procedure involves
> your sending an application thru SoC online tool starting
> May 1st. Yours, along with all other applications related
> to Boost, will then be routed by Google to Boost mentors,
> which will do then the selection and P2P discussion
> with applicants.
> In your case, since you're interested in the B.MI proposal,
> I understand it's gonna be I who will be evaluating
> your application. I don't really know what the application
> format and required information are (that depends on the
> SoC online tool, I guess) but I can tell you what I'd like
> to see in those submissions under my evaluation
> * As much CV data as possible, academic performance,
> programming-related courses, etc.
> * Programming experience: University assignments,
> open source projects, freelance activities, whatever.
> If you can point to some code of yours, so much the
> * As per the concrete proposal, expand on the idea
> described on the Boost wiki along the following
> * A detailed description of your activity, specially
> if you plan to add some extra bonuses to the
> original idea (some other specialized container,
> for instance). Do not make a wishlist, but rather
> provide a realistic statement of goals you feel
> confident to achieve within the time schedule
> imposed by SoC.
> * Environmental details: IDEs you'll be using,
> how you'll do the docs, etc.
> * A roadmap of the project, or some approximation
> to it.
> In general, take into account there can be other
> applicants for the same project, so not only must you
> be convincing the mentors you're fit for the project,
> you must make it it clear you're the fittest :)
> Good luck with your application, I'll be seeing you
> around during these weeks, come back here if you have
> tecnhical doubts while designing your application.
> Joaquín M López Muñoz
> Telefónica, Investigación y Desarrollo
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk