mediagoblin-1.0-checklist.html 6.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206
  1. <html>
  2. <head>
  3. <title>What's coming in MediaGoblin 1.0?</title>
  4. <meta name="date" content="2012-11-06 10:00" />
  5. <meta name="author" content="Christopher Allan Webber" />
  6. </head>
  7. <body>
  8. <p class="centered">
  9. <a href="/pages/campaign.html"
  10. ><img src="/blog_images/feature_puzzle.png"
  11. alt="Building our way to 1.0!" /></a>
  12. </p>
  13. <p>So the <a href="/pages/campaign.html">MediaGoblin fundraiser</a> is
  14. in its last week, and we're coming near our goal of funding one year
  15. of dedicated MediaGoblin development. We're hoping over the next year
  16. to hit a point of MediaGoblin for the masses... AKA MediaGoblin 1.0!
  17. But wait... what exactly <i>is</i> MediaGoblin 1.0?</p>
  18. <p>To answer that, we need to go over two things: what we already
  19. have, and what we're going to have. Let's go over the first list
  20. first...</p>
  21. <h2>Features we have (and will continue to improve on before 1.0):</h2>
  22. <ul>
  23. <li>
  24. <p>
  25. <b>Image, video, and audio publishing</b>
  26. </p>
  27. <p>
  28. MediaGoblin provides image, video, and audio publishing out of the
  29. box, making it a self-hostable and free replacement for services
  30. like Flickr, YouTube, and SoundCloud.
  31. </p>
  32. </li>
  33. <li>
  34. <p><b>Flexible storage system</b></p>
  35. <p>MediaGoblin has a
  36. <a href="http://wiki.mediagoblin.org/Storage">flexible storage
  37. system</a> built in. It comes with a local file storage option
  38. as well as integration with OpenStack's "Swift" storage system,
  39. so you can offload hosting to something like Rackspace
  40. Cloudfiles or equivalent. You can even add entirely new storage
  41. mechanisms.</p>
  42. </li>
  43. <li>
  44. <p><b>Media types are extensible</b></p>
  45. <p>Images, video, and audio are just the beginning. MediaGoblin was
  46. <a href="http://wiki.mediagoblin.org/Processing">designed to be
  47. extensible for entirely new media types</a>. For fun, you can
  48. use the AsciiArt example media type, or you could even build
  49. something entirely new. Want to support presentations or
  50. e-books? Or maybe you want to have 3d model support?
  51. MediaGoblin was designed from day 1 to be extensible to fit the
  52. needs of whatever types of files you want.</p>
  53. </li>
  54. <li>
  55. <p><b>Commenting</b></p>
  56. <p>MediaGoblin supports basic, markdown-enabled commenting on media
  57. entries.</p>
  58. </li>
  59. <li>
  60. <p><b>GeoLocation / OpenStreetMap integration</b></p>
  61. <p>Does your camera have a GPS? MediaGoblin can put your photos on a
  62. map, so you can see where they're taken.</p>
  63. </li>
  64. <li>
  65. <p><b>Galleries and collections</b></p>
  66. <p>We show the usual galleries of a user's media, as well as special
  67. galleries for tagging, and we also support user-curated
  68. "collections" of media.</p>
  69. </li>
  70. <li>
  71. <p><b>"Attachments" (for media source files and etc)</b></p>
  72. <p>If you have files that you used to make the final piece of media
  73. you're sharing and you want to share those also, MediaGoblin has an
  74. option to allow for that.</p>
  75. </li>
  76. <li>
  77. <p><b>Beginnings of a plugin system</b></p>
  78. <p>We have the beginnings of a plugin system, with already a couple of
  79. useful plugins (flatpages, so people setting up terms of service or
  80. similar non-dynamic pages are easy to add).</p>
  81. </li>
  82. </ul>
  83. <h2>Features that aren't developed yet but should be for 1.0:</h2>
  84. <ul>
  85. <li>
  86. <p><b>API (for desktop/mobile app integration and so on)</b></p>
  87. <p>We have an API that is close to being completed, but isn't yet.
  88. This should allow external application authors to integrate
  89. directly with MediaGoblin instances in various ways. This will
  90. allow for mobile phone uploading of photos and videos, or
  91. direct-from-desktop uploading, or integration with other services.</p>
  92. </li>
  93. <li>
  94. <p><b>Federation</b></p>
  95. <p>One major feature is the need to hook together separate MediaGoblin
  96. instances and provide a social experience that feels as clean as if
  97. it users were on the same site (similar to how users on different
  98. email servers can communicate to each other from different servers
  99. but it feels that things are on the same thing).</p>
  100. <p>We intend to use the meta-standard OStatus to provide the following
  101. federated functionality:</p>
  102. <ul>
  103. <li>Ability to subscribe to other users across instances</li>
  104. <li>Favoriting across instances</li>
  105. <li>Cross-instance collections/galleries (think Flickr pool)</li>
  106. </ul>
  107. </li>
  108. <li>
  109. <p><b>Audio and video podcasting support</b></p>
  110. <p>With podcasting support, MediaGoblin will enter a new area of
  111. usefulness as people are able to use it to broadcast shows to
  112. subscribers.</p>
  113. </li>
  114. <li>
  115. <p><b>Admin tools</b></p>
  116. <p>MediaGoblin needs better tools for administrators to be stewards of
  117. their instances, both to promote things appropriately and clean out
  118. problematic content and administer users.</p>
  119. </li>
  120. <li>
  121. <p><b>More and improved plugins</b></p>
  122. <p>We have plugin support already, but more plugins need to be built.
  123. These include:</p>
  124. <ul>
  125. <li>Comment spam prevention</li>
  126. <li>Moving some extensions into plugins (OpenStreetMap, etc)</li>
  127. <li>Limiting storage and upload space for various users</li>
  128. </ul>
  129. </li>
  130. <li>
  131. <p><b>Easier installs and improved documentation</b></p>
  132. <p>MediaGoblin needs to be even easier to install and develop. We can
  133. improve this situation with better packaging and stronger
  134. documentation.</p>
  135. </li>
  136. <li>
  137. <p><b>New media types</b></p>
  138. <p>In addition to the media types we have, new ones are on the way: 3d
  139. model support is close to being polished, and there may be other
  140. types added soon.</p>
  141. </li>
  142. <li>
  143. <p><b>More general polish</b></p>
  144. <p>MediaGoblin is well working software, but there are a lot of rough
  145. edges that still need to be smoothed out to make the experience
  146. better for users, such as cleaner submission processes, various
  147. adjustments to theming, and so on. We will continue to add shine
  148. to MediaGoblin as we approach 1.0.</p>
  149. </li>
  150. </ul>
  151. <p>Wow. Tall order! But if you look at the first section and the
  152. second section both, you can see we've already accomplished a lot. We
  153. can do this... but we need your help to make it happen! MediaGoblin
  154. has a wonderful volunteer community, but it takes a lot to
  155. coordinate... the closer we can get to our full goal, the better we
  156. can do to get a full and uninterrupted year of MediaGoblin development
  157. and coordination. Help us make all our dreams come true...
  158. <a href="/pages/campaign.html">Support MediaGoblin!</a></p>
  159. <p class="centered">
  160. <a href="/pages/campaign.html">
  161. <img src="/blog_images/support_mediagoblin-blagpost.png"
  162. alt="Gavroche imploring you to support MediaGoblin!" />
  163. </a>
  164. </p>
  165. </body>
  166. </html>