XSPF Todo list: Difference between revisions

From XiphWiki
Jump to navigation Jump to search
(I think that means using the Xiph page headers and stuff which is also the case already)
(loving no longer planned. see vorbis-dev archive of today.)
Line 9: Line 9:
## can either side back out later?
## can either side back out later?
## read the 501c and other legal documents
## read the 501c and other legal documents
# Move the mailing list?  How to do that without affect Musicbrainz.org?
# Move wiki
# Move wiki
## pointer on the old wiki to the new one
## pointer on the old wiki to the new one
## freeze the old wiki to be sure that people use this one?
## freeze the old wiki to be sure that people use this one?

Revision as of 17:39, 28 September 2007

  1. Due diligence on legal agreement. What exactly are the XSPF and Xiph.org people committing to?
    1. commitment to open/royalty-free
      DanBri suggests:
      "http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Requirements It would be re-assuring if Xiph would explicitly (re)confirm their commitment to open, royalty-free standards in this area. From a look at the Xiph site, I'd guess that shouldn't be a problem..."
      1. see theora notice for something similar in a xiph project.
    2. what was the arrangement between FLAC and Xiph when they did a similar thing in 2003?
    3. talk to Xiph lawyer?
    4. who owns XSPF copyrights and trademark?
      1. have each contributor sign something like http://copylaw.com/forms/copyassn.html
      2. add a copyright notice to each file
    5. can either side back out later?
    6. read the 501c and other legal documents
  2. Move wiki
    1. pointer on the old wiki to the new one
    2. freeze the old wiki to be sure that people use this one?