/docs/CREDITS

https://github.com/JazzDeben/tiddlyweb-xmobile · #! · 64 lines · 50 code · 14 blank · 0 comment · 0 complexity · 36ef626747a6546f170a5b6b7fb8530e MD5 · raw file

  1. 1.0 to 1.2
  2. ----------
  3. Once a stable 1.0 release of TiddlyWeb was out in the wild, the number
  4. of people using the system, working the code and generally contributing
  5. to its well being took off. The improvement of the code since then is
  6. entirely the result of a diverse group of people from the TiddlyWeb
  7. google group, the TiddlyWiki community and the people who operate in and
  8. about Osmosoft.
  9. The Osmosoft project to create TiddlySpace has helped make TiddlyWeb far
  10. more robust, flexible and scalable.
  11. I (Chris Dent) am especially grateful to FND for his continued
  12. enthusiasm, limitless contributions, dogged attention to detail and
  13. invaluable service as a rubber duck.
  14. Thanks to BT for continuing to believe that supporting open source
  15. development has benefits in the short and long term. Without BT's
  16. support there would likely be no TiddlyWeb.
  17. Birth to 1.0
  18. ------------
  19. The architecture, attitude and action of TiddlyWeb is the result of
  20. ideas and interactions with many people, all of whom are impossible to
  21. list here, but a few highlights:
  22. * The original mo'ass (mother of all server sides) idea, including the
  23. concepts of recipes and bags, comes from Jeremy Ruston, the original
  24. inventor of TiddlyWiki.
  25. * TiddlyWeb is a Python application in large part because of the WSGI
  26. specification, PEP 333, authored by Phillip J. Eby and the stalwart
  27. enthusiasm of Zac Bir, a long time Python confederate.
  28. * Zac is also a conceptual parent of the architectural style that drives
  29. TiddlyWeb's extensibility in the stores and serializers and the
  30. challengers and extractors. All four are modeled, at a distance, on
  31. concepts in Zope and systems implemented or designed to varying
  32. degrees while at Socialtext.
  33. * The RESTful principles, or at least web friendly principles depending
  34. on how strict you care to think about such things, that drive the
  35. TiddlyWeb HTTP API, are all based on research and development creating
  36. the Socialtext REST API with Matt Liggett and Matthew O'Connor.
  37. * Frank McIngvale, the author of WikklyText which does the server-side
  38. wikitext to HTML transformation originally in TiddlyWeb and then extracted
  39. to a plugin (tiddlywebwiki), provided excellent input on many aspects
  40. of TiddlyWeb, and of course built the excellent WikklyText.
  41. * Frederik Dohr is the earliest adopter of TiddlyWeb, and responsible
  42. for most of the code that creates the TiddlyWebWiki vertical. He's
  43. been invaluable in providing input on features, excellent bug reports,
  44. and general support and comradeship throughout the development process.
  45. * Action requires communication to make go. Many thanks to Jon Lister,
  46. Martin Budden, Paul Downey, Phil Hawksworth, Phil Whitehouse, Simon
  47. McManus, Michael Mahemoff, Jon Robson and Ben Gillies from Osmosoft;
  48. Tony, Oveek, Reenen, Ben Tremblay and others from the TiddlyWikiDev
  49. and TiddlyWeb Google groups; and many others for comments, questions
  50. and conversations about TiddlyWeb.