91 lines
4.2 KiB
Plaintext
91 lines
4.2 KiB
Plaintext
/*
|
|
Copyright 1996-2004 by Hans Reiser, licensing governed by
|
|
reiserfsprogs/README.
|
|
*/
|
|
|
|
Hans Reiser was the project initiator, source of all funding for the first 5.5
|
|
years. He is the architect and official maintainer.
|
|
|
|
Vladimir Saveliev started as the most junior programmer on the team, and became
|
|
the lead programmer. He is now an experienced highly productive programmer. He
|
|
wrote the extent handling code for Reiser4, plus parts of the balancing code
|
|
and file write and file read.
|
|
|
|
Alexander Zarochentcev (zam) wrote the high low priority locking code, online
|
|
resizer for V3 and V4, online repacker for V4, block allocation code, and major
|
|
parts of the flush code, and maintains the transaction manager code. We give
|
|
him the stuff that we know will be hard to debug, or needs to be very cleanly
|
|
structured.
|
|
|
|
Nikita Danilov wrote most of the core balancing code, plugin infrastructure,
|
|
and directory code. He steadily worked long hours, and is the reason so much of
|
|
the Reiser4 plugin infrastructure is well abstracted in its details. The carry
|
|
function, and the use of non-recursive balancing, are his idea.
|
|
|
|
Vladimir Demidov wrote the parser for sys_reiser4(), the V3 alpha port, part of
|
|
the V3 journal relocation code, and helped Hans keep the business side of
|
|
things running.
|
|
|
|
Chris Mason wrote the journaling code for V3, which was enormously more useful
|
|
to users than just waiting until we could create a wandering log filesystem as
|
|
Hans would have unwisely done without him.
|
|
Jeff Mahoney optimized the bitmap scanning code for V3, and performed the big
|
|
endian cleanups.
|
|
|
|
Elena Gryaznova performed testing and benchmarking.
|
|
|
|
Oleg Drokin was the debugger for V3 during most of the time that V4 was under
|
|
development, and was quite skilled and fast at it. He wrote the large write
|
|
optimization of V3.
|
|
|
|
Edward Shushkin wrote the encryption and compression file plugins, and the V3
|
|
journal relocation code.
|
|
|
|
Alexander Lyamin keeps our hardware running, and was very generous to our
|
|
project in many little ways.
|
|
|
|
Vitaly Fertman wrote fsck for V3 and maintains the reiserfsprogs package now.
|
|
He wrote librepair, userspace plugins repair code, fsck for V4, and worked on
|
|
developing libreiser4 and userspace plugins with Umka.
|
|
|
|
Yury Umanets (aka Umka) developed libreiser4, userspace plugins, and all
|
|
userspace tools (reiser4progs) except of fsck.
|
|
|
|
Joshua Macdonald wrote the first draft of the transaction manager. Yuri Rupasov
|
|
did testing and benchmarking, plus he invented the r5 hash (also used by the
|
|
dcache code). Yura Rupasov, Anatoly Pinchuk, Igor Krasheninnikov, Grigory
|
|
Zaigralin, Mikhail Gilula, Igor Zagorovsky, Roman Pozlevich, Konstantin
|
|
Shvachko, and Joshua MacDonald are former contributors to the project.
|
|
|
|
Jeremy Fitzhardinge wrote the teahash.c code for V3. Colin Plumb also
|
|
contributed to that.
|
|
|
|
The Defense Advanced Research Projects Agency (DARPA, www.darpa.mil) is the
|
|
primary sponsor of Reiser4. DARPA does not endorse this project; it merely
|
|
sponsors it.
|
|
|
|
Continuing core development of ReiserFS is mostly paid for by Hans Reiser from
|
|
money made selling licenses in addition to the GPL to companies who don't want
|
|
it known that they use ReiserFS as a foundation for their proprietary product.
|
|
And my lawyer asked 'People pay you money for this?'. Yup. Life is good. If you
|
|
buy ReiserFS, you can focus on your value add rather than reinventing an entire
|
|
FS.
|
|
|
|
BigStorage (www.bigstorage.com) contributes to our general fund every month,
|
|
and has done so for quite a long time.
|
|
|
|
SuSE (www.suse.com) pays for continuing work on journaling for version 3, paid
|
|
for much of the previous version 3 work, and is paying for Chris and Jeff to do
|
|
V3 maintenance. Reiserfs integration in their distro is consistently solid, and
|
|
they were key to our becoming widely used.
|
|
|
|
Lycos Europe (www.lycos-europe.com) had a support contract with us that
|
|
consistently came in just when we would otherwise have missed payroll, and that
|
|
they kept doubling every year. Much thanks to them.
|
|
|
|
Many persons came to www.namesys.com/support.html, and got a question answered
|
|
for $25, or just gave us a small donation there.
|
|
|
|
Thanks to all of those sponsors, including the secret ones. Without you, we
|
|
would each still have that day job.
|