Geeklog.net Redesign - Revision history

Tom: /* Forum */

2013-04-12T22:23:49Z

‎Forum

2013-04-12T21:34:42Z

‎Forum

2013-04-05T15:19:51Z

‎Forum

2013-01-10T14:06:31Z

2013-01-09T17:03:03Z

re-save to fix character issue.

2012-09-04T21:35:10Z

‎Topics

2012-02-22T20:18:41Z

‎Topics

2012-02-22T01:46:25Z

‎Topics

2012-02-22T01:30:58Z

2012-02-22T01:26:08Z

‎Bounties

@@ Line 122: / Line 122: @@
 * Geeklog - General discussion for developers on Geeklog. (Combining GL 1.x and GL 2)
 * Plugins - General discussion for developers on Geeklog Core Plugins.
-* Themes - General discussion for developers on Themes bundled with Geeklog
+* Themes - General discussion for developers on Themes bundled with Geeklog.
 * GSOC - Google Summer of Code discussions.

@@ Line 110: / Line 110: @@
 * General Support - Geeklog and install support. (Combining General Help and Installation)
 * Plugin Support - Help and support with any Geeklog plugin. (Previously Plugin Help)
-* Theming Support (previously Themes)
+* Theming Support - Help and support with any Geeklog theme. (previously Themes)
 * Documentation, Tips & Tricks - Post instructions, tips and tricks for beginners. (non wiki related, or maybe a sticky topic pointing to the wiki for beginners)

@@ Line 120: / Line 120: @@
 Development & Coding - Information on developing Geeklog and it's core components
-* GL 1.x - General discussion for developers on Geeklog.
+* Geeklog - General discussion for developers on Geeklog. (Combining GL 1.x and GL 2)
 * Plugins - General discussion for developers on Geeklog Core Plugins.
 * Themes - General discussion for developers on Themes bundled with Geeklog

← Older revision		Revision as of 14:06, 10 January 2013
Line 19:		Line 19:

	= Components =		= Components =
		+
		+	== Database ==
		+
		+	* Convert database and tables from collation latin1_swedish_ci to UTF-8
		+	** http://www.geeklog.net/article.php?story=200410120657418
		+	** http://geeklog.fr/wiki/iso-8859-to-utf8

	== Pages ==		== Pages ==

@@ Line 77: / Line 77: @@
 ** A Geeklog team member(s) (which we will list somewhere) needs to green light the project and accept responsibility for adding it to Core if they approve the code submission. This probably should be done in the notes of the feature request so it is public and is easy to find.
 ** If a final patch is submitted then in the notes of the feature request the developer should state the bounty has been finished and he/she now wish to receive the bounty.
-** In a reasonable amount of time the Geeklog team member should reply stating if it was accepted or rejected and the reasons
+** In a reasonable amount of time the Geeklog team member should reply stating if it was accepted or rejected and the reasons why�
 ** Geeklog is only responsible for paying bounties they specifically sponsor.  If all or part of the money for a bounty is sponsored by other parties it is the developers responsibility to collect the money once the submission for the bounty has been accepted by the Geeklog Team.

@@ Line 51: / Line 51: @@
 ** News
 *** Announcements
 *** Summer of Code
 ** Archive (Private)
 *** AptitudeCMS (Private)

@@ Line 43: / Line 43: @@
 * Since Geeklog 1.9.0 will support child topics should we add, delete or move the topics around? (Tom)
 * Home
-** Geeklog
+** Development
-** AptitudeCMS
+*** Geeklog
-** Announcements
+*** Plugins
-** Summer of Code
+*** Themes
-** Security
+** News
-** Plugins
+*** Announcements
-** Server
+*** Summer of Code
-** Bugs (Private)
+*** Security
-** Spam
+*** Geeklog.net (formerly Server)
-** Developers Only (Private)
+** Archive (Private)
 === Team Members ===

@@ Line 39: / Line 39: @@
 ** Feel free to copy from other open source projects' web sites (with their permission...)
 ** Mixed feelings about whether and how prominently case studies and example sites should be featured. Definitely recommended not to commit to a timeline (such as "site of the week") for fear of being unable to keep such an update schedule.
 === Team Members ===

@@ Line 53: / Line 53: @@
 === Bounties ===
+* As discussed on the mailing list it looks like we may not offer Bounties since they really have not worked out. (Tom)
 * Add these points (reworded) to the "For Developers" section to help avoid any issues when developers work on a bounty. (Tom)
 ** A Geeklog team member(s) (which we will list somewhere) needs to green light the project and accept responsibility for adding it to Core if they approve the code submission. This probably should be done in the notes of the feature request so it is public and is easy to find.