And where your code is? It does not matter it is incomplete, etc. That's the whole point - we are here to help you make it better. You should have had your own branches (if based on existing work) or or your own repositories, by now, and as much of the on-going work should be available in public, and discussed in public.
That's also not optional. And why did you not ask for sample SPDX files earlier, if you need them? You should have asked in the mailing list, as soon as you think you need them. And ask again, if you don't hear a reply... I think I counted only two posts from you to the mailing list, and both times because I asked. -------------------------------------------- On Sun, 8/6/14, ahi <[email protected]> wrote: Subject: Re: current status of the java binding, and GSoC To: [email protected] Cc: "[email protected]" <[email protected]>, "Philippe Ombredanne" <[email protected]>, "Nuno Brito" <[email protected]>, "Vlad Velici" <[email protected]> Date: Sunday, 8 June, 2014, 22:12 On Sun, Jun 8, 2014 at 11:46 PM, Hin-Tak Leung <[email protected]> wrote: > Ahmed: I think I already explained that you must write a few words every > 10 days or so during the GSoC period on progress. You can plan your own > work and how you want to spend your time on a day-to-day basis and the approach > you take; but GSoC is supposed to be equivalent to a 3-month summer job > and you should treat it as such. A few words every 10 days-ish is *not* optional. > I apologize for not sending updates, I will do my best to keep regular updates. I am currently working on the tag/value parser. I am using PLY https://pypi.python.org/pypi/ply/3.1 to implement the lexer and parser. The lexer is pretty much complete at this point, I am still testing it. Hopefully I will be testing the parser by this time tomorrow. I could really benefit from some sample SPDX files. I am currently using the ones from https://github.com/goneall/SPDX-Tools/tree/master/Examples and https://github.com/triplecheck/reporter/tree/master/run/reports -- Best Regards, Ahmed _______________________________________________ Spdx-tech mailing list [email protected] https://lists.spdx.org/mailman/listinfo/spdx-tech
