[Sharpknocking-devel] The next to do

[SharpKnocking project development list.]

Hello sharpknockers :p

Lately we have been very busy but it's time to spent some of out scarce free
time into this if we want to make some progress this year.

The first thing is the state of the current code base.

The old project layout is still there under the sharpknocking folder but
some things got broken by me this summer when i was refactorizing things.
Someone should revert it to its state after june of 2007 when we finished
the past contest.

There are some new folders there to comment on:
- iSharpKnocking: This is the new project main folder. Inside it are folders
named using the namespace of the components inside them where we should
begin to drop our old sharpknocking code and start giving some love to it.
- Extras: This is where all that stuff that we think that can be shared
goes. Inside it are:
  + IptablesSharp: This is the refactoring of the old iptablesNet library
with a lot of changes. In the process of refactoring i have left only the
targets and match extensions that we need as that part have been fully
rewritten and still needs some sanity to be applied.
  + DeveloperCommon: This is an assembly to put code that we think can be of
use for more projects but is too small to be usefull in a single assembly.
- Library: In monodevelop post-compile actions are supported so i added a
call to a script that copies each library built and puts it in this
directory. When compiling in debug mode they are put in a Debug directory
and the same with Release.
- Common: This is the same as before. Only contains the artwork directory.
- lib: Our old library directory for the external libraries that we might
use. Currently there is only the old SharpKnocking.Common.dll library that
is used in our old implementation.
- Tests: This is where all our tests should go. By now there is only a few
scripts with little use for good testing.

This is a high-level view of the sources.

This code still needs some work:
- IptablesSharp is functional but needs support for more match and target
extensions to be really usefull. We also need a class with the
responsability of executing commands over the real iptables as no library
exists to do this task.
- iSharpKnocking still needs its redesign, most of it should go to the
daemon and the logic that cares about the knocking sequences and that should
handle timeouts, commands, more variability, and all those fancy features in
our wiki.

This is all for now.

Cogments?
Thoughts?
Grammatical corrections?

Regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ilikecoffee.net/pipermail/sharpknocking-devel_ilikecoffee.net/attachments/20080111/bed55edb/attachment.html