Jim.Gettys at hp.com
Thu Mar 18 07:16:17 PST 2004
I also checked my notes from talking with Scott Peterson.
When they are an attribution
of where the file came from, they are perfectly fine and can
be left alone; but as we change files, we should replace them.
The point of trademark law is to avoid confusion with the trademark
owner; so in this case, when the file is unchanged, it is an
attribution; but when we change the file, we should change the
CVS tag, so that it is clear it is something we've changed.
The first priority
On Thu, 2004-03-18 at 10:25, Egbert Eich wrote:
> I've worked a little bit more on this issue.
> I guess more people should get moving on this.
> A few questions:
> \$XFree86: CVS tags in installed files 629 Leave alone or delete CVS tags Yes
> \$XFree86\$ Broken CVS tags 182 Leave alone or delete CVS tags Yes
> Are we sure we need to change CVS tags? They only suggest that these files
> where at one time in the XFree86 CVS.
> include/freetype2/freetype XFree86 Freetype headers 6 Eliminate XFree86-specific FreeType Delete
> Are you referring to ftxf86.h? Yes, I think the freetype project
> come up with a more generic name. The function already has a generic
> lib/X11/config All of the config files 227 I don't know. Yes
> These contain a lot of vendor specific names as they are used to build
> the DDX of that specific vendor. I don't see why the XFree86 rules
> should be removed from there. If they aren't used they aren't used.
> We also need to think what to do about the version number.
> This isn't as trivial as it sounds as some files have version
> specific build paths. This needs to be investigated and is
> error prone!
> Also I would like to invite those who advocate this to step
> forward and get going on this. Since we are quite late in the
> release cycle I would like to see people reviewing the code
> changes that go in. For every change we therefore should have
> at least two people: one who does the change and one who looks
> over the code. Sorry, this is not mistrust, we just need to
> make sure we don't introduce additional problems.
> OK, here is what I've done:
> XFree86 Font Renderer XFree86 driver identifiers 42 Can we change this and retain ABI? Accept either, use new
> XFree86 Video [Dd]river XFree86 driver identifiers 56 Can we change this and retain ABI? Accept either, use new
> XFree86 XInput [Dd]river XFree86 driver identifiers 52 Can we change this and retain ABI? Accept either, use new
> \\.[ao]: The XFree86 Project XFree86 drivers include this 102 Change? Yes
> XFree86 ANSI C Emulation XFree86 libraries have this 20 Can we change this and retain ABI? Accept either; use new
> usr/X11R6/bin/XFree86 Strings in the X server itself 16 Investigate Yes
> XFree86 Server Extension XFree86 driver identifiers 10 Can we change this and retain ABI? Accept either; use new
> drivers/sis_drv.o References product 3 Change Yes
> drivers/tseng_drv.o References product 3 Change Yes
> bin/xdpyinfo Gets custom XFree86 version 2 Should at least add new X.org version detection Add X.org version parsing
> etc/fonts/fonts.conf Fontconfig config 2 Replace with upstream Yes
> I'll have a look at these:
> XawVendor Xaw vendor string 1 Change Yes
> input/kbd_drv.o default keysym 1 I think we need to change this Yes
> bin/rman custom SGML manual extractor 2 Should we install this at all? Yes
> bin/cleanlinks fix shadow tree 1 Should we install this at all? No
> bin/mkhtmlindex Build html index 3 Should we install this at all? Fix TITLE/H1
> bin/pswrap How is this XFree86 specific? 1 Should we use DPS upstream? Yes
> bin/fonttosfnt New font utility. Not ready 6 We shouldn't install this Yes
> bin/mkfontscale Don't know how used 2 Fix? Yes
> bin/xfs Vendor string (I think) 1 Change Yes
> bin/xinit Product reference 1 Change Yes
> bin/setxkbmap Default keymap 1 Change? Yes
> bin/xterm Release version 1 Change Yes
> bin/Xnest Default keymap (I think) 1 Change Yes
> bin/xf86cfg Lots of stuff 13 Investigate Yes
> bin/xf86config Lots of stuff 13 Investigate Yes
> bin/scanpci Vendor 1 Change? Yes
> bin/gtf Names format for video mode 1 Leave alone, perhaps ammend with new project name yes
> bin/getconfig Used by xf86AutoConfig 19 Delete Delete
> etc/X11/app-defaults/Xvidtune Warranty 1 Change? Add our project name
> etc/X11/app-defaults/XF86Cfg Distributor of program 1 Change Yes
> etc/X11/xdm XFree86 logo 6 Replace with Freedesktop logo Yes
> etc/X11/xkb Keymapping stuff 173 Fix Yes
> release-wranglers mailing list
> release-wranglers at freedesktop.org
Jim Gettys <Jim.Gettys at hp.com>
HP Labs, Cambridge Research Laboratory
More information about the release-wranglers