Ahmed,
Thank you. Both for your question 1 below (we should use it), and
for question 2 (responsiveness – let’s make it more responsive and
actually show the failure, etc.) that would be great.
Thanks,
Chris
From: Ahmed Ifhaam <ahmedifha...@gmail.com>
Reply-To: "dev@drat.apache.org" <dev@drat.apache.org>
Date: Wednesday, March 21, 2018 at 4:02 AM
To: "dev@drat.apache.org" <dev@drat.apache.org>
Subject: Re: GSOC-Drat issue 115
hi Chris,
in terms of running, i meant, i have cloned the repo, build it and ran it
on one of my git repository.
I ran it in cli mode on my local and remote.
but in the gui i ran it only for remote git because it required a zip file
in local
Related to code base i'm reading on it. I like to start work on this, i
will prepare my proposal draft asap. Since i got your requirements ill try
to check on them too and once i get something ill ping you back and Thanks
for the reply.
Initially i have few questions
1. If we can select a folder in cli why we are not using it in GUI
2. When we are using GUI it is not very responsive, means when ever the app
crashes gui doesn't reflect that. For example if i forget to reset the drat
and run a new job my java is crashing but gui still shows indexing and some
percentage too. Is it built that way ? or its a bug ?
Thank you,
Regards
Ahmed Ifhaam
On Wed, Mar 21, 2018 at 3:05 AM, Chris Mattmann <mattm...@apache.org> wrote:
Hi Ahmed,
Sorry about the delay in replying. I would be happy to mentor you on this
project.
So, where did you get to in terms of installing DRAT and running it? Were
you
able to run DRAT against e.g., itself? For example are you able to run DRAT
against its own code base? Did you use Proteus to do so?
The next steps in Proteus are:
1) Unifying the architecture - right now it is an AngularJS mess with
Wicket and
REST web services provided by Apache CXF. It's decent, but the components
could
use cleaning up, and furthermore, some of them get overloaded.
2) the REST services simply wrap a process execution to the DRAT backend.
I think
we can actually do better than that and simply use OODT REST API services
since
most of the commands are simply using OODT services, aka Crawler and File
Manager
and workflow, etc. So I would like to clean this part up too.
3) I would like to add some new features to the code base for example the
downloading
and exporting of JSON reports for the license issues that DRAT found from
the UI.
4) I would like to carefully look at the non Proteus "viz" UI which runs
separate and uses
DRAT stats and then see if any of that should be part of Proteus, etc.
5) I would like to make it so that Proteus can support multiple instances
of a user and multiple
runs using the same OODT backend, just by tagging the results with
"project" labels so that
they could be looked up in the UI.
So that's the scope of the GSoC project. Are you game? How far did you
get? Have you started
working on a proposal yet?
Cheers,
Chris Mattmann
On 3/20/18, 1:42 PM, "Ahmed Ifhaam" <ahmedifha...@gmail.com> wrote:
hi,
I'm Ahmed Ifhaam. I am a Management and Information Technology
Undergraduate at University of Kelaniya. I'am willing to contribute
something to this community and i see Programming and problem solving
as my
strengths hence I would love to use this GSOC opportunity to do
something
which will make my self happy. And i found this issue interesting [1]
<https://github.com/apache/drat/issues/115> in git-hub. I did comment
on
the issue but i didn't get a reply thats why even though it was clearly
mentioned to comment there i'm dropping an email. I tried running the
project. I need to know what i should do next.
[1] https://github.com/apache/drat/issues/115
Thank you.
Regards
--
*Ahmed Ifhaam *
University of Kelaniya | MIT '19
Tel :- 0662244937 | Mob :- 0776699609
ahmedifha...@gmail.com <e-mail-ahmedifha...@gmail.com>
--
*Ahmed Ifhaam *
University of Kelaniya | MIT '19
Tel :- 0662244937 | Mob :- 0776699609
ahmedifha...@gmail.com <e-mail-ahmedifha...@gmail.com>
