userops.html 5.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105
  1. <html>
  2. <head>
  3. <title>
  4. Userops: Deployment for the People
  5. </title>
  6. <meta name="date" contents="2015-03-16 14:12" />
  7. <meta name="author" contents="Christopher Allan Webber" />
  8. <meta name="tags" contents="userops, deployment, fosdem" />
  9. </head>
  10. <body>
  11. <p>
  12. Deb Nicholson and I both recently gave a talk at FOSDEM 2015
  13. called "Can Distros Make the Link?" (A recording is
  14. <a href="http://video.fosdem.org/2015/devroom-distributions/can_distros_make_the_link%3f_lets_package_the_customizable,_free_software_web_of_the_future!_.mp4">here</a>,
  15. and my slides are
  16. <a href="http://dustycloud.org/misc/talks/deployment/fosdem_2015/deploying_libreweb.html">here</a>,
  17. hit "s" for speaker notes or read the
  18. <a href="http://dustycloud.org/misc/talks/deployment/fosdem_2015/deploying_libreweb.org">org-mode source</a> if
  19. you prefer.) The main purpose of the talk was that packaging
  20. libre network services/applications for distros is important, but
  21. distros in their present forms aren't really enough to solve the
  22. deployability problems and pains that anyone trying to run their
  23. own libre servers knows. I had a bit of a worry that this thesis
  24. would upset part of the audience (it was in the distros room,
  25. after all) but it turns out that everyone seemed to agree and be
  26. on board.
  27. </p>
  28. <p>
  29. Many audience members even encouraged us that this conversation
  30. needed to continue beyond FOSDEM, and there was discussion of
  31. hosting a mailing list to continue the conversation. As usual,
  32. everyone had various ideas of where to host it, but the audience
  33. seemed to feel that MediaGoblin's servers were fairly neutral
  34. ground, so we announced that we would put up a mailing list and
  35. announce it here when we got the chance.
  36. </p>
  37. <p>
  38. It's a bit delayed, but I'm happy to announce the launch of the
  39. <a href="http://lists.mediagoblin.org/listinfo/userops">userops
  40. mailing list</a>! If you're interested in talking about making
  41. deployment easier for every-day users, please consider joining
  42. the conversation there. (Oh, and we also have an IRC channel:
  43. join #userops on irc.freenode.net, if you're the IRC type!)
  44. </p>
  45. <p>
  46. Why the name "userops"? As you may have guessed, this is a pun on
  47. the term "devops"; the idea is that we also care about
  48. configuration management and deployability, but we aim for a
  49. different audience. Devops, as the name implies, focuses on
  50. liberating developers in the world of deployment, particularly
  51. developers who have to deploy a large number of machines for
  52. $LARGE_CORPORATION at their job. Userops, on the other hand, aims
  53. at liberating users in the world of deployment. You shouldn't
  54. have to be a developer to take advantage of network freedoms and
  55. run network-oriented free software. After all, the free software
  56. world generally agrees that it makes sense that users of desktop
  57. software should not have to be developers, and that "user freedom"
  58. takes priority over "developer freedom"... the freedom of
  59. $LARGE_CORPORATION, while not something we object to, is not
  60. really our primary concern. (Though of course, if we build
  61. solutions that are good enough for end-users, corporations will
  62. probably adopt them, and that is fine! It just isn't our focus.)
  63. </p>
  64. <p>
  65. (Oh, and in case you stumble upon it, "userops" was originally a
  66. name I had for one of my personal projects experimenting with
  67. deployability, but a
  68. <a href="http://asheesh.org/">friend of mine</a>
  69. convinced me that the term was too useful to be constrained to one
  70. particular piece of software, so I've renamed that project!
  71. Everyone is now free to use the term "userops" to refer to the
  72. vision described above.)
  73. </p>
  74. <p>
  75. We believe that "userops" is now more important than ever. These
  76. days, it is not just enough to use free software network services,
  77. one must have the ability to deploy and make use of that software.
  78. (For many of this, the timeliness and urgency of this is seen with
  79. the turmoil for many free software developers figuring out where
  80. to go now that the
  81. <a href="https://about.gitlab.com/2015/03/03/gitlab-acquires-gitorious/">hosted
  82. version of Gitorious is being shut down</a>.) And as you may
  83. have guessed, we're well aware of how true this is not of just
  84. "all that other libre network services"; MediaGoblin requires
  85. quite a bit of technical skills and resources to run. We'd like
  86. to improve that, but we think there are some real challenges that
  87. are beyond what MediaGoblin can do as MediaGoblin itself: things
  88. need to happen on another layer (or layers) too. Hence "userops"!
  89. </p>
  90. <p>
  91. If this is something you likewise care about, and especially if it's
  92. something you're working on or thinking about (or would like to),
  93. consider
  94. <a href="http://lists.mediagoblin.org/listinfo/userops">joining
  95. the conversation</a>!
  96. </p>
  97. </body>
  98. </html>