Hello.
Le ven. 22 mars 2019 à 14:48, Abhishek Dhadwal <dhadwal1...@gmail.com> a écrit :
>
> Dear Sir,
> >I don't understand what you mean be "screening tests". Sorry.
> Certain organisations had held certain micro tasks to be performed by
> students in order to increase their chances of selection for the project. I
> was asking about those tasks in reference to our current project.
Well then, I guess that we consider the micro-tasks which I evoked in
my previous message: Clone the repository and build the code.
This is explained in more details here:
http://commons.apache.org/proper/commons-rng/developers.html
Please try it, and then let us know how it went.
> >Overall, the task consists in providing a Java implementation of the
> generator(s).
> Sir, may I attain more information on this topic?
If we are going to advance in the discussion, you'll have to spell out
what you don't understand in the task description here:
https://issues.apache.org/jira/browse/RNG-32
> I read the student guidebook, and, as the deadline for the application
> submission periods are approaching, I may need to write the synopsis,
> timeline, deliverables and participation details of the project along with
> the application itself, and would greatly appreciate help with obtaining
> data/guidance with the above information.
Here is a document which you should read if not done already:
http://community.apache.org/gsoc.html#students-read-this
Please note that there are several "roles" in the GSoC program; on this
ML, you'll only get technical help with specific programming tasks. But
it seems (?) that you need more general help from the administrative side.
Also, you should have a look at other tasks which you help with in the
"Commons" project (of which "Commons RNG" is a tiny part).
Some of these other tasks may look less daunting to you. And nothing
will prevent you from contributing to "Commons RNG" too when you'll
feel more comfortable with the expectations.
> > But, in order to compile the library and perform automatically the necessary
> sanity checks on the code you write, you'll need "maven"[1].
> I’ve downloaded and installed Maven, and shall begin pursuing a Udemy course
> in Maven in the near future.
OK. But that is certainly not a requirement; usage is pretty
straightforward in the context of this project, and most of the
"magic" is handled by the configuration file(s) shipped with the
project's code. At this point, you should be fine with running
this command (from within the directory where you "clone"d the
"git" repository):
$ mvn package
Gilles
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
