Editing Seismic Library (section)

==== So, how? ====

Specifications in our sort of environments develop during actual software development. What you can do, is make one
or a couple of documents scanning the problem domain, identifying what kinds of problems are the likely ones that need to be grappled with. Things like: what sort of data and procedures are common in acquisition,
processing and interpretation? How does this differ from research to hard-core production work? Or this one: what computer language(s) is/are the target(s)?

Therefore, we'd need input from many sides, from people who are willing to put aside their economic, emotional and historical stakes - but rather approach the problem from the more philosophical side. The result is an inventory of
knowledge, tensions, existing techniques, resources, visions, ... and take it from there.

Then, start cracking. The Open Source way is to specify by implementing. A function that works is worth a thousand words of specification. Read about the [http://www.martinfowler.com/articles/newMethodology.html Agile] way, and pick up the good bits. Keep communicating, and improving. Prepare for change; in particular, make sure the data versioning system is brilliant. Contribution is great but keep the evil forces away.