about.html 3.8 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071
  1. {% extends "base.html" %}
  2. {% block content %}
  3. About GNU MediaGoblin
  4. <div id="page-8" class="page-asset asset">
  5. <div class="asset-header">
  6. <h1 id="page-title" class="asset-name">About</h1>
  7. </div>
  8. <div class="asset-content">
  9. <div class="asset-body">
  10. <p>The <b>"What"</b> of the project is described on our <a href="/">main page</a>. As for the rest...</p>
  11. <h2>Why?</h2>
  12. <p>Why do this? We believe it's necessary, for multiple reasons, but in a nutshell:</p>
  13. <p>Centralization and proprietization of media on the internet is a serious problem and makes the web go from a system of extreme resilience to a system of frightening fragility.</p>
  14. <p>Also, people should be able to free their data from proprietary control.</p>
  15. <p>If you're reading this, chances are you already agree though.</p>
  16. <h2>How?</h2>
  17. <p>Things are mostly <a href="http://python.org">python</a> based. Beyond that, see the <a href="http://docs.mediagoblin.org/codebase.html#software-stack">software stack</a> section of the docs as the <a href="http://docs.mediagoblin.org/designdecisions.html">design decisions</a> chapter.</p>
  18. <h2>Who?</h2>
  19. <p>We are goblins who live near the Earth's core. We number one and twenty and we like to eat french fry sandwiches, though we accurately refer to them as chip butties.</p>
  20. <p>A more useful list of the founders of GNU MediaGoblin follows:</p>
  21. <ul>
  22. <li>
  23. <b><a href="http://dustycloud.org/">Chris Webber</a></b> --
  24. Lead developer. Currently works for <a href="http://creativecommons.org">Creative Commons</a> as a software engineer, working on the website, metadata stuff, etc. Former <a href="http://getmiro.com">Miro</a> hacker, also worked on the <a href="http://miroguide.com">Miro Guide</a> and was the initial programmer for <a href="http://mirocommunity.org">Miro Community</a>.
  25. </li>
  26. <li>
  27. <b><a href="http://bluesock.org/~willg/">Will Kahn-Greene</a></b> --
  28. Developer and emperor of documentation. Also a <a href="http://getmiro.com">Miro</a> hacker, maintainer of <a href="http://pyblosxom.bluesock.org/">PyBlosxom</a> and <a href="http://python.mirocommunity.org/">Python Miro Community</a>. Overall charming fellow.
  29. </li>
  30. <li>
  31. <b><a href="http://matt.lee.name/">Matt Lee</a></b> --
  32. FooCorp (provider of our infrastructure) mastermind #1. <a href="http://fsf.org">FSF</a> campaigns manager. A time traveller stranded in this era.
  33. </li>
  34. <li>
  35. <b><a href="http://robmyers.org/">Rob Myers</a></b> --
  36. FooCorp mastermind #2. Free culture activist and enthusiast. Absolutely the most likely person to explain to you at length that <a href="http://creativecommons.org/characteristic/nc">NC</a> and <a href="http://creativecommons.org/characteristic/nc">ND</a> licenses are a bad idea.
  37. </li>
  38. <li>
  39. <b><a href="http://eximiousproductions.com/">Deb Nicholson</a></b> --
  40. Community outreach overlord. Founder of the <a href="http://libreplanet.org/wiki/Womenscaucus">Women's Caucus</a>. Secretly fights crime with the power of performing music loudly.
  41. </li>
  42. <li><b><a href="/pages/join.html">You???</a></b></li>
  43. </ul>
  44. <h2>When?</h2>
  45. <p>Right now the code that we have is moving from base infrastructure to basic functionality. We're hoping to have a better, more feature-ful version that is targeted for people other than us by around September/October 2011. It'll let you log in, log out, post pictures, etc... It'll be clear that we've accomplished something useful, but that there is still a lot of interesting things left to do. Success on this largely depends on both the hard work of the current developers but also whether we can get new contributors.</p>
  46. <p>On that note, <b>please <a href="/pages/join.html">join us as a contributor</a></b>... one way or another we could use your help!</p>
  47. </div>
  48. </div>
  49. </div>
  50. {% endblock content %}