On Sunday, August 17, 2014 01:24:41 PM unixninja92 wrote: > This means that all the other classes I've written for the API are > finished and ready for review/merging.
It is very much appreciated to have things in a merge-able state after GSoC :)
Thanks for your efforts! It's nice to see core security being improved by
crypto work, especially since the way we did crypto was said to be rather non-
standard and possibly insecure in the past.
Please make sure to nag people even after GSoC to merge it. Too much GSoC code
has been abandoned because nobody bothered to merge it. It probably often is
not an issue with the code but just a lack of someone continuously annoying
people to merge it, so please do it :)
> Unfortunately I don't have time to get JFKExchange classes working as
> part of GSoC, but I will hopefully have time to work on them in the
> future.
Is that a major missing component or minor stuff?
Can you fix it right after GSoC?
If not, can you properly document as a bugtracker entry what needs to be done
and how to do it? The code should also have JavaDoc to explain how it works,
but large TODOs should be in the bugtracker so they don't get lost.
Thanks again for your work! :)
xor
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
