[L2Ork-dev] New developer interested in doing a GSOC18 project

[pranay gupta]

Hello Jonathan,

Well I think there is a some kind of a mixup here. I don't know.

Anyways thanks for the suggestion Jonathan. I have already divided my
project into 3 different parts according to your suggestion.
I chose to include these libs since it was important to come up with an
initial plan for the project, and I thought that the libraries that the
lib_loader loads up by default might be a good choice for starters.
Although I had mentioned that I will extend this list after the selection
of the project in GSoC.

Sincerely,
Pranay Gupta.


On Mon, Mar 26, 2018 at 9:45 PM, Rishabh Jain <
f20140069 at goa.bits-pilani.ac.in> wrote:

> Agreed. If go by this approach, the final outcome will be fool proof. I'll
> starting reading up about each now, but I'm not sure about finishing this
> by tomorrow morning (by the deadline). Though, it's already been 7 hours
> straight now and I'm still not done with my proposal.
> Have you looked at it once?Please let me know about it.
> Though, I've been told by my friend that I can change my proposal after
> submitting the first draft at google platform. I'm not sure about this.
>
> Best,
> Rishabh
>
> On Mon, Mar 26, 2018 at 9:30 PM, Jonathan Wilkes <jon.w.wilkes at gmail.com>
> wrote:
>
>> >> Below is the list of externals that get loaded, in order.
>> >>
>> >> cyclone
>> >> zexy
>> >> creb
>> >> cxc
>> >> iemlib
>> >> mapping
>> >> markex
>> >> maxlib
>> >> memento
>> >> mjlib
>> >> motex
>> >> oscx
>> >> pddp
>> >> pdogg
>> >> pixeltango
>> >> rradical
>> >> sigpack
>> >> smlib
>> >> unauthorized
>> >> pan
>> >> hcs
>> >> jmmmp
>> >> ext13
>> >> ggee
>> >> ekext
>> >> disis
>> >> lyonpotpourri
>> >> pdlua
>>
>> Also-- I would strongly suggest to break the default libraries up into
>> two categories for your proposal: perhaps three "critical" libraries,
>> and "other."
>>
>> The critical ones would be the most popular libraries that users would
>> want ported. You don't have to choose
>> them now, but have it as a category. "Other" would be the remaining
>> default libraries.
>>
>> Then the project divides up into at least three broad sections: core,
>> critical libs, and other default libs.
>>
>> That way if you run into unforeseen problems as you begin working on
>> the external libraries, you'll
>> still have a clear goal on the horizon to finish the critical libs.
>> Whereas if you just lump them all
>> together, the same set of problems will seem an order of magnitude
>> more difficult to solve.
>>
>> -Jonathan
>> _______________________________________________
>> L2Ork-dev mailing list
>> L2Ork-dev at disis.music.vt.edu
>> https://disis.music.vt.edu/listinfo/l2ork-dev
>
>
>
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20180326/1abf36b7/attachment-0001.html>