From eaa2a96cfaecb2b64df0c2fd2f1bfeaf2fd9fd0c Mon Sep 17 00:00:00 2001 From: "Bradley M. Kuhn" Date: Tue, 17 Dec 2013 13:13:16 -0500 Subject: [PATCH] Remove a few additional files not needed to use this only for voting. --- ChangeLog | 47 --------------------------------------------- HACKING | 17 ---------------- foundation-web.doap | 20 ------------------- 3 files changed, 84 deletions(-) delete mode 100644 ChangeLog delete mode 100644 HACKING delete mode 100644 foundation-web.doap diff --git a/ChangeLog b/ChangeLog deleted file mode 100644 index f12a383..0000000 --- a/ChangeLog +++ /dev/null @@ -1,47 +0,0 @@ -=== ChangeLog discontinued === - - With the move to git, this module is switching from a ChangeLog file to - relying on commit messages to provide change history. Please write commit - messages in the format described at http://live.gnome.org/Git/CommitMessages - - Below is a copy of this format: - -=== begin example commit === -[tag] Short explanation of the commit - -Longer explanation explaining exactly what's changed, whether any -external or private interfaces changed, what bugs were fixed (with bug -tracker reference if applicable) and so forth. Be concise but not too brief. -=== end example commit === - - - The commit message is mainly for the other people, so they should be able - to understand it now and six months later. - - - Always add a brief description of the commit to the _first_ line of the - commit and terminate by two newlines (it will work without the second - newline, but that is not nice for the interfaces). - - - First line (the brief description) must only be one sentence and should - start with a capital letter unless it starts with a lowercase symbol or - identifier. Don't use a trailing period either. Don't exceed 72 characters. - - - You can prefix the first line with one tag, to make it easier to know to - which part of the module the commit applies. For example, a commit with - "[fish] Make it work with newer fortune" in the gnome-panel module clearly - applies to the fish applet. - - - The main description (the body) is normal prose and should use normal - punctuation and capital letters where appropriate. Normally, for patches - sent to a mailing list it's copied from there. This main description can be - empty if the change is self-explanatory (eg: "Add DOAP file"). - - - When committing code on behalf of others use the --author option, e.g. git - commit -a --author "Joe Coder ". - - - When referring to a bug, you can use this form: bgo#12345. Use bgo for - bugzilla.gnome.org, but you can also reference bugs in other bug trackers: - rh means bugzilla.redhat.com, bnc means bugzilla.novell.com, lp means - launchpad.net, etc. - - - When a commit closes a bug, the commit message should contain a line like: - Closes: http://bugzilla.gnome.org/show_bug.cgi?id=12345 diff --git a/HACKING b/HACKING deleted file mode 100644 index 9a59622..0000000 --- a/HACKING +++ /dev/null @@ -1,17 +0,0 @@ -Other than fixes to obvious typos, please do not commit to this module -without first approving changes with the GNOME Foundation Board or -the Membership Committee: - - board-list@gnome.org - membership-committee@gnome.org - -Note that many of these files were originally created with various HTML -authoring tools and have a lot of evil cruft in them. It is very unlikely -that any of these files are valid HTML. Over time we should gradually clean -them up whenever we edit them until some day all the old cruft is gone and -we have valid HTML. :) - -Please edit these files by hand and consider using indentation. ;) - -[ See README in the gnomeweb-wml module for a primer about GNOME website -development. ] diff --git a/foundation-web.doap b/foundation-web.doap deleted file mode 100644 index 2c082cb..0000000 --- a/foundation-web.doap +++ /dev/null @@ -1,20 +0,0 @@ - - - Website foundation.gnome.org - Website foundation.gnome.org - - - - - - - Vincent Untz - - vuntz - - -