[Whonix-devel] Introduction - Rick
adrelanos at riseup.net
Thu Jan 29 10:07:46 CET 2015
secretsocket at nym.hush.com:
> Hello folks, I just want to introduce myself to the list as I intend
> to be lurking for a while and thought it would be fair of me to
> introduce myself quickly first.
> My name is Rick and am currently studying Computer engineering -
> security. I was in computer science for 3 semesters (programming)
> before switching to security.
> I am hoping to eventually be able to support this project by
> contributing my time. I think this is a fantastic project and am
> hoping to learn a lot but I do need to get more oriented. I noticed
> a lot of request for testers but very little on what and how would
> be most useful as well as the best way to format results. I hope to
> find some documentation on that.
There is no formal testing documentation yet. Best there is:
For now, testing means, "download, verify, try whatever you would do
anyhow, report if you find any issues". No formal report or so.
> As I mentioned I will be reading this discussion and documentation
> as well as testing out the product. I would like to submit my name
> to the developers on this board and pledge a few hours (maybe 3 to 6)
> a week to start while I do this to anyone here who would care to
> delegate some tasks to me. I see there is a need for testers and
> research. I can do research and/or testing for instance and submit
> semi formal results. Anyway, if anyone cares to take me up on this
> it would make me feel welcome and very happy. If not I am also
> happy to lurk and learn until I can find something useful to do.
Recently I posted this search ad:
automated test suite developer (Cucumber...)
Creating that test suite would be an independent Whonix sub project from
We also have a research tag:
We also have sometimes C tasks. They're not all on the tracker yet,
however the one that is there is a good one:
Mostly those tasks are C code that we need in projects that are not
Whonix, but that Whonix depends on. You'd need to jump through whatever
hoop upstream wants then.
There are also other C tasks which need lots of guess work, proposal
writing, cross project communication, politics before you the actual C
code can be written. Important and difficult one:
Otherwise look around in the tracker:
Plenty of stuff there. Perhaps you find something that sounds good to you?
> Thank-you for reading this intro and please advise if you have any
> tasks you think I can do taking in the range of 3 to 6 hours a week.
> These are not hard numbers but I want to be realistic.
Good to be realistic. That hours are okay. If you keep at it at a weekly
base, that still piles up over the year. :)
More information about the Whonix-devel