2016/program/formatted-sessions.html

   1 <article class="program-day" id="day-1-program">
   2  <header class="program-day-header">
   3   <hgroup>
   4    <h2>
   5     Saturday, March 19th
   6     <a aria-controls="day-1-timeslots" aria-expanded="false" class="btn btn-default btn-xs" data-toggle="collapse" href="#day-1-timeslots" role="button">
   7      ↓
   8     </a>
   9    </h2>
  10   </hgroup>
  11  </header>
  12  <div class="collapse in" id="day-1-timeslots">
  13   <article class="program-timeslot" id="day-1-timeslot-1">
  14    <header class="program-timeslot-header">
  15     <hgroup>
  16      <h2>
  17       10:40 - 11:25: Session Block 1B
  18       <a aria-controls="day-1-timeslot-1-sessions" aria-expanded="false" class="btn btn-default btn-xs" data-toggle="collapse" href="#day-1-timeslot-1-sessions" role="button">
  19        ↓
  20       </a>
  21      </h2>
  22     </hgroup>
  23    </header>
  24    <div class="collapse in" id="day-1-timeslot-1-sessions">
  25     <section class="program-session" id="day-1-timeslot-1-session-1">
  26      <header class="program-session-header">
  27       <hgroup>
  28        <h2>
  29         Fork and ignore: fighting a GPL violation by coding instead
  30        </h2>
  31       </hgroup>
  32      </header>
  33      <span class="program-session-speaker">
  34       <a href="https://libreplanet.org/YEAR/path/to/speakers.html#kuhn">
  35        Bradley Kuhn
  36       </a>
  37       ,
  38       <a href="https://libreplanet.org/YEAR/path/to/speakers.html#sandler">
  39        Karen Sandler
  40       </a>
  41      </span>
  42      <button aria-controls="day-1-timeslot-1-session-1-collapse" aria-expanded="false" class="btn btn-default btn-xs" data-target="#day-1-timeslot-1-session-1-collapse" data-toggle="collapse">
  43       Details
  44      </button>
  45      <div class="collapse in" id="day-1-timeslot-1-session-1-collapse">
  46       <p>
  47        <span class="label label-default">
  48         Room 32-155
  49        </span>
  50       </p>
  51       <p>
  52        Typically, GPL enforcement activity involves copyright infringement
  53 actions which compel license violators to correct errors in their
  54 GPL compliance, defending the policy goals of the GPL: the rights of
  55 developers and users to copy, share, modify and redistribute.
  56       </p>
  57       <p>
  58        While traditional enforcement is often undeniably necessary for
  59 embedded electronics products, novel approaches to GPL violations
  60 are often possible and even superior for more traditional software
  61 distributions.
  62       </p>
  63       <p>
  64        Recently,
  65        <a href="https://sfconservancy.org/">
  66         Software Freedom Conservancy
  67        </a>
  68        engaged in an
  69 enforcement action whereby, rather than fight the violator in court,
  70 we instead provided resources and assistance to a vetted
  71 GPL-compliant fork of a violating codebase.
  72       </p>
  73       <p>
  74        This talk discusses which scenarios make this remedy optimal and the
  75 lessons learned. The talk includes some licensing and technical
  76 content about vetting the licensing information of codebases.
  77       </p>
  78      </div>
  79      <!-- day-1-timeslot-1-session-1-collapse end -->
  80     </section>
  81     <!-- day-1-timeslot-1-session-1 end -->
  82     <section class="program-session" id="day-1-timeslot-1-session-2">
  83      <header class="program-session-header">
  84       <hgroup>
  85        <h2>
  86         A serious session
  87        </h2>
  88       </hgroup>
  89      </header>
  90      <span class="program-session-speaker">
  91       <a href="https://libreplanet.org/YEAR/path/to/speakers.html#sandler">
  92        Ms Inline
  93       </a>
  94      </span>
  95      <button aria-controls="day-1-timeslot-1-session-2-collapse" aria-expanded="false" class="btn btn-default btn-xs" data-target="#day-1-timeslot-1-session-2-collapse" data-toggle="collapse">
  96       Details
  97      </button>
  98      <div class="collapse in" id="day-1-timeslot-1-session-2-collapse">
  99       <p>
 100        <span class="label label-default">
 101         Room 32-420
 102        </span>
 103       </p>
 104       <p>
 105        Typically, GPL enforcement activity involves copyright infringement
 106 actions which compel license violators to correct errors in their
 107 GPL compliance, defending the policy goals of the GPL: the rights of
 108 developers and users to copy, share, modify and redistribute.
 109       </p>
 110       <p>
 111        While traditional enforcement is often undeniably necessary for
 112 embedded electronics products, novel approaches to GPL violations
 113 are often possible and even superior for more traditional software
 114 distributions.
 115       </p>
 116       <p>
 117        Recently, Mister Mime engaged in an
 118 enforcement action whereby, rather than fight the violator in court,
 119 we instead provided resources and assistance to a vetted
 120 GPL-compliant fork of a violating codebase.
 121       </p>
 122       <p>
 123        This talk discusses which scenarios make this remedy optimal and the
 124 lessons learned. The talk includes some licensing and technical
 125 content about vetting the licensing information of codebases.
 126       </p>
 127      </div>
 128      <!-- day-1-timeslot-1-session-2-collapse end -->
 129     </section>
 130     <!-- day-1-timeslot-1-session-2 end -->
 131     <section class="program-session" id="day-1-timeslot-1-session-3">
 132      <header class="program-session-header">
 133       <hgroup>
 134        <h2>
 135         A silly session
 136        </h2>
 137       </hgroup>
 138      </header>
 139      <span class="program-session-speaker">
 140       Zak Rogoff who doesn't have a bio yet
 141      </span>
 142      <button aria-controls="day-1-timeslot-1-session-3-collapse" aria-expanded="false" class="btn btn-default btn-xs" data-target="#day-1-timeslot-1-session-3-collapse" data-toggle="collapse">
 143       Details
 144      </button>
 145      <div class="collapse in" id="day-1-timeslot-1-session-3-collapse">
 146       <p>
 147        <span class="label label-default">
 148         Room 32-555
 149        </span>
 150       </p>
 151       <p>
 152        Typically, GPL enforcement activity involves copyright infringement
 153 actions which compel license violators to correct errors in their
 154 GPL compliance, defending the policy goals of the GPL: the rights of
 155 developers and users to copy, share, modify and redistribute.
 156       </p>
 157       <p>
 158        While traditional enforcement is often undeniably necessary for
 159 embedded electronics products, novel approaches to GPL violations
 160 are often possible and even superior for more traditional software
 161 distributions.
 162       </p>
 163       <p>
 164        Recently, uncle pepper engaged in an
 165 enforcement action whereby, rather than fight the violator in court,
 166 we instead provided resources and assistance to a vetted
 167 GPL-compliant fork of a violating codebase.
 168       </p>
 169       <p>
 170        This talk discusses which scenarios make this remedy optimal and the
 171 lessons learned. The talk includes some licensing and technical
 172 content about vetting the licensing information of codebases.
 173       </p>
 174      </div>
 175      <!-- day-1-timeslot-1-session-3-collapse end -->
 176     </section>
 177     <!-- day-1-timeslot-1-session-3 end -->
 178    </div>
 179    <!-- day-1-timeslot-1-sessions end -->
 180   </article>
 181   <!-- day-1-timeslot-1 end -->
 182   <article class="program-timeslot" id="day-1-timeslot-2">
 183    <header class="program-timeslot-header">
 184     <hgroup>
 185      <h2>
 186       12:00 - 01:25: Session Block 4F
 187       <a aria-controls="day-1-timeslot-2-sessions" aria-expanded="false" class="btn btn-default btn-xs" data-toggle="collapse" href="#day-1-timeslot-2-sessions" role="button">
 188        ↓
 189       </a>
 190      </h2>
 191     </hgroup>
 192    </header>
 193    <div class="collapse in" id="day-1-timeslot-2-sessions">
 194     <section class="program-session" id="day-1-timeslot-2-session-1">
 195      <header class="program-session-header">
 196       <hgroup>
 197        <h2>
 198         Afternoon session
 199        </h2>
 200       </hgroup>
 201      </header>
 202      <span class="program-session-speaker">
 203       <a href="https://www.fsf.org">
 204        Steve Jobs
 205       </a>
 206      </span>
 207      <button aria-controls="day-1-timeslot-2-session-1-collapse" aria-expanded="false" class="btn btn-default btn-xs" data-target="#day-1-timeslot-2-session-1-collapse" data-toggle="collapse">
 208       Details
 209      </button>
 210      <div class="collapse in" id="day-1-timeslot-2-session-1-collapse">
 211       <p>
 212        <span class="label label-default">
 213         Room 01-420
 214        </span>
 215       </p>
 216       <p>
 217        Typically, GPL enforcement activity involves copyright infringement
 218 actions which compel license violators to correct errors in their
 219 GPL compliance, defending the policy goals of the GPL: the rights of
 220 developers and users to copy, share, modify and redistribute.
 221       </p>
 222       <p>
 223        While traditional enforcement is often undeniably necessary for
 224 embedded electronics products, novel approaches to GPL violations
 225 are often possible and even superior for more traditional software
 226 distributions.
 227       </p>
 228       <p>
 229        Recently,  engaged in an
 230 enforcement action whereby, rather than fight the violator in court,
 231 we instead provided resources and assistance to a vetted
 232 GPL-compliant fork of a violating codebase.
 233       </p>
 234       <p>
 235        This talk discusses which scenarios make this remedy optimal and the
 236 lessons learned. The talk includes some licensing and technical
 237 content about vetting the licensing information of codebases.
 238       </p>
 239      </div>
 240      <!-- day-1-timeslot-2-session-1-collapse end -->
 241     </section>
 242     <!-- day-1-timeslot-2-session-1 end -->
 243    </div>
 244    <!-- day-1-timeslot-2-sessions end -->
 245   </article>
 246   <!-- day-1-timeslot-2 end -->
 247  </div>
 248  <!-- day-1-timeslots end -->
 249 </article>
 250 <!-- day-1 end -->
 251 <article class="program-day" id="day-2-program">
 252  <header class="program-day-header">
 253   <hgroup>
 254    <h2>
 255     Sunday, March 20th
 256     <a aria-controls="day-2-timeslots" aria-expanded="false" class="btn btn-default btn-xs" data-toggle="collapse" href="#day-2-timeslots" role="button">
 257      ↓
 258     </a>
 259    </h2>
 260   </hgroup>
 261  </header>
 262  <div class="collapse in" id="day-2-timeslots">
 263   <article class="program-timeslot" id="day-2-timeslot-1">
 264    <header class="program-timeslot-header">
 265     <hgroup>
 266      <h2>
 267       10:40 - 11:25: Session Block 1B
 268       <a aria-controls="day-2-timeslot-1-sessions" aria-expanded="false" class="btn btn-default btn-xs" data-toggle="collapse" href="#day-2-timeslot-1-sessions" role="button">
 269        ↓
 270       </a>
 271      </h2>
 272     </hgroup>
 273    </header>
 274    <div class="collapse in" id="day-2-timeslot-1-sessions">
 275     <section class="program-session" id="day-2-timeslot-1-session-1">
 276      <header class="program-session-header">
 277       <hgroup>
 278        <h2>
 279         Fork and ignore: fighting a GPL violation by coding instead
 280        </h2>
 281       </hgroup>
 282      </header>
 283      <span class="program-session-speaker">
 284       <a href="https://libreplanet.org/YEAR/path/to/speakers.html#kuhn">
 285        Bradley Kuhn
 286       </a>
 287       ,
 288       <a href="https://libreplanet.org/YEAR/path/to/speakers.html#sandler">
 289        Karen Sandler
 290       </a>
 291      </span>
 292      <button aria-controls="day-2-timeslot-1-session-1-collapse" aria-expanded="false" class="btn btn-default btn-xs" data-target="#day-2-timeslot-1-session-1-collapse" data-toggle="collapse">
 293       Details
 294      </button>
 295      <div class="collapse in" id="day-2-timeslot-1-session-1-collapse">
 296       <p>
 297        <span class="label label-default">
 298         Room 32-155
 299        </span>
 300       </p>
 301       <p>
 302        Typically, GPL enforcement activity involves copyright infringement
 303 actions which compel license violators to correct errors in their
 304 GPL compliance, defending the policy goals of the GPL: the rights of
 305 developers and users to copy, share, modify and redistribute.
 306       </p>
 307       <p>
 308        While traditional enforcement is often undeniably necessary for
 309 embedded electronics products, novel approaches to GPL violations
 310 are often possible and even superior for more traditional software
 311 distributions.
 312       </p>
 313       <p>
 314        Recently,
 315        <a href="https://sfconservancy.org/">
 316         Software Freedom Conservancy
 317        </a>
 318        engaged in an
 319 enforcement action whereby, rather than fight the violator in court,
 320 we instead provided resources and assistance to a vetted
 321 GPL-compliant fork of a violating codebase.
 322       </p>
 323       <p>
 324        This talk discusses which scenarios make this remedy optimal and the
 325 lessons learned. The talk includes some licensing and technical
 326 content about vetting the licensing information of codebases.
 327       </p>
 328      </div>
 329      <!-- day-2-timeslot-1-session-1-collapse end -->
 330     </section>
 331     <!-- day-2-timeslot-1-session-1 end -->
 332     <section class="program-session" id="day-2-timeslot-1-session-2">
 333      <header class="program-session-header">
 334       <hgroup>
 335        <h2>
 336         A serious session
 337        </h2>
 338       </hgroup>
 339      </header>
 340      <span class="program-session-speaker">
 341       <a href="https://libreplanet.org/YEAR/path/to/speakers.html#sandler">
 342        Ms Inline
 343       </a>
 344      </span>
 345      <button aria-controls="day-2-timeslot-1-session-2-collapse" aria-expanded="false" class="btn btn-default btn-xs" data-target="#day-2-timeslot-1-session-2-collapse" data-toggle="collapse">
 346       Details
 347      </button>
 348      <div class="collapse in" id="day-2-timeslot-1-session-2-collapse">
 349       <p>
 350        <span class="label label-default">
 351         Room 32-420
 352        </span>
 353       </p>
 354       <p>
 355        Typically, GPL enforcement activity involves copyright infringement
 356 actions which compel license violators to correct errors in their
 357 GPL compliance, defending the policy goals of the GPL: the rights of
 358 developers and users to copy, share, modify and redistribute.
 359       </p>
 360       <p>
 361        While traditional enforcement is often undeniably necessary for
 362 embedded electronics products, novel approaches to GPL violations
 363 are often possible and even superior for more traditional software
 364 distributions.
 365       </p>
 366       <p>
 367        Recently, Mister Mime engaged in an
 368 enforcement action whereby, rather than fight the violator in court,
 369 we instead provided resources and assistance to a vetted
 370 GPL-compliant fork of a violating codebase.
 371       </p>
 372       <p>
 373        This talk discusses which scenarios make this remedy optimal and the
 374 lessons learned. The talk includes some licensing and technical
 375 content about vetting the licensing information of codebases.
 376       </p>
 377      </div>
 378      <!-- day-2-timeslot-1-session-2-collapse end -->
 379     </section>
 380     <!-- day-2-timeslot-1-session-2 end -->
 381     <section class="program-session" id="day-2-timeslot-1-session-3">
 382      <header class="program-session-header">
 383       <hgroup>
 384        <h2>
 385         A silly session
 386        </h2>
 387       </hgroup>
 388      </header>
 389      <span class="program-session-speaker">
 390       Zak Rogoff who doesn't have a bio yet
 391      </span>
 392      <button aria-controls="day-2-timeslot-1-session-3-collapse" aria-expanded="false" class="btn btn-default btn-xs" data-target="#day-2-timeslot-1-session-3-collapse" data-toggle="collapse">
 393       Details
 394      </button>
 395      <div class="collapse in" id="day-2-timeslot-1-session-3-collapse">
 396       <p>
 397        <span class="label label-default">
 398         Room 32-555
 399        </span>
 400       </p>
 401       <p>
 402        Typically, GPL enforcement activity involves copyright infringement
 403 actions which compel license violators to correct errors in their
 404 GPL compliance, defending the policy goals of the GPL: the rights of
 405 developers and users to copy, share, modify and redistribute.
 406       </p>
 407       <p>
 408        While traditional enforcement is often undeniably necessary for
 409 embedded electronics products, novel approaches to GPL violations
 410 are often possible and even superior for more traditional software
 411 distributions.
 412       </p>
 413       <p>
 414        Recently, uncle pepper engaged in an
 415 enforcement action whereby, rather than fight the violator in court,
 416 we instead provided resources and assistance to a vetted
 417 GPL-compliant fork of a violating codebase.
 418       </p>
 419       <p>
 420        This talk discusses which scenarios make this remedy optimal and the
 421 lessons learned. The talk includes some licensing and technical
 422 content about vetting the licensing information of codebases.
 423       </p>
 424      </div>
 425      <!-- day-2-timeslot-1-session-3-collapse end -->
 426     </section>
 427     <!-- day-2-timeslot-1-session-3 end -->
 428    </div>
 429    <!-- day-2-timeslot-1-sessions end -->
 430   </article>
 431   <!-- day-2-timeslot-1 end -->
 432   <article class="program-timeslot" id="day-2-timeslot-2">
 433    <header class="program-timeslot-header">
 434     <hgroup>
 435      <h2>
 436       12:00 - 01:25: Session Block 4F
 437       <a aria-controls="day-2-timeslot-2-sessions" aria-expanded="false" class="btn btn-default btn-xs" data-toggle="collapse" href="#day-2-timeslot-2-sessions" role="button">
 438        ↓
 439       </a>
 440      </h2>
 441     </hgroup>
 442    </header>
 443    <div class="collapse in" id="day-2-timeslot-2-sessions">
 444     <section class="program-session" id="day-2-timeslot-2-session-1">
 445      <header class="program-session-header">
 446       <hgroup>
 447        <h2>
 448         Afternoon session
 449        </h2>
 450       </hgroup>
 451      </header>
 452      <span class="program-session-speaker">
 453       <a href="https://www.fsf.org">
 454        Steve Jobs
 455       </a>
 456      </span>
 457      <button aria-controls="day-2-timeslot-2-session-1-collapse" aria-expanded="false" class="btn btn-default btn-xs" data-target="#day-2-timeslot-2-session-1-collapse" data-toggle="collapse">
 458       Details
 459      </button>
 460      <div class="collapse in" id="day-2-timeslot-2-session-1-collapse">
 461       <p>
 462        <span class="label label-default">
 463         Room 01-420
 464        </span>
 465       </p>
 466       <p>
 467        Typically, GPL enforcement activity involves copyright infringement
 468 actions which compel license violators to correct errors in their
 469 GPL compliance, defending the policy goals of the GPL: the rights of
 470 developers and users to copy, share, modify and redistribute.
 471       </p>
 472       <p>
 473        While traditional enforcement is often undeniably necessary for
 474 embedded electronics products, novel approaches to GPL violations
 475 are often possible and even superior for more traditional software
 476 distributions.
 477       </p>
 478       <p>
 479        Recently,  engaged in an
 480 enforcement action whereby, rather than fight the violator in court,
 481 we instead provided resources and assistance to a vetted
 482 GPL-compliant fork of a violating codebase.
 483       </p>
 484       <p>
 485        This talk discusses which scenarios make this remedy optimal and the
 486 lessons learned. The talk includes some licensing and technical
 487 content about vetting the licensing information of codebases.
 488       </p>
 489      </div>
 490      <!-- day-2-timeslot-2-session-1-collapse end -->
 491     </section>
 492     <!-- day-2-timeslot-2-session-1 end -->
 493    </div>
 494    <!-- day-2-timeslot-2-sessions end -->
 495   </article>
 496   <!-- day-2-timeslot-2 end -->
 497  </div>
 498  <!-- day-2-timeslots end -->
 499 </article>
 500 <!-- day-2 end -->
 501