History of Contribute Code

Differences from version 2 to 4



@@ -1,20 +1,31 @@

 {maketoc}
 As you know, bitweaver consists of a set of core packages and a number of optional packages. New devs who join the bitweaver coding team, have immediate access to non core packages and may commit to these. When there is demand, we will grant access to the core packages. Commits to these need to be treated with more respect since they affect all packages.
 
-! ToDo List
-# Subscribe to the [http://sourceforge.net/mail/?group_id=141358|bitweaver-core] mailing list. This is a low volume mailing list where important announcements are made.
-# {code title="Check out CVSROOT"}cd bitweaver/
+! How can i contribute?
+We recommend that you subscribe to the [http://sourceforge.net/mail/?group_id=141358|bitweaver-core] mailing list. This is a low volume mailing list where important announcements are made.
+Frequently it's useful to discuss changes in real time and we recommend that you ((ConnectingToIRC|join us on IRC)).
+
+!! Commit using CVS (recommended)
+# You will need an account on [http://www.sourceforge.net|Sourceforge]
+# Ask one of the developers to add you to the bitweaver developers (best done on IRC)
+# ((GetCode|Get bitweaver using CVS)) with your sourceforge username
+# Get a list of all cvs modules {code title="Check out CVSROOT" source=Bash}cd bitweaver/
 cvs co CVSROOT
 vim CVSROOT/modules
 {/code}
-# test
+# Check out all packages you're interested in using commands such as:{code title="Get additional packages"}cvs co _bit_gmap{/code}
+# Start contributing (thank you!)
+
+!! Submit Patches to Sourceforge
+Alternatively, you may submit patches to sourceforge. This might not always get picked up right away, since we are not very good at checking the patches section...
 
 ! Discuss Commits
-Certain types of commits should always be discussed:
-* All schema related files:
+Certain types of commits should always be discussed via the bitweaver-core mailing list or on IRC:
+* All changes to schema related files:
 ** ''package''/admin/schema_inc.php
 ** ''package''/admin/upgrade_inc.php
 ** ''package''/admin/upgrades/*
+* Any change to any core package that isn't simply cosmetic
 * Major changes to the behaviour of a package
 * Any change that is not backwards compatible
 

@@ -23,12 +34,12 @@

 # Discuss them with the creator / maintainer of the package or one of the lead developers
 # Commit schema change to ''package''/admin/schema_inc.php
 # Enter the change in ((SchemaChangelog))
-# Create an appropriate upgrade file in ''package''/admin/upgrades/<version>.php
+# Create an appropriate upgrade file in ''package''/admin/upgrades/''version''.php. Please see existing upgrade files on how to deal with upgrades.
 # announce the schema change on the [http://sourceforge.net/mail/?group_id=141358|bitweaver-core] mailing list
 
 !! Version Numbers
 Any package can use version numbers as they see fit. __Core packages__ stick to the following rules:
-||~ Rev | Rev | Rev | Desription
+||~ Major | Minor | Fix | Desription
 ::__X__:: | | | This is the __major__ release version of bitweaver and indicates what version of bitweaver the core package belongs to.
  | ::__Y__:: | | This is the __minor__ release which is increased when there is a schema change to that package.
  | | ::__Z__:: | This is a __bug fix__ release that simply fixes issues with existing code.
Page History
Date/CommentUserIPVersion
10 Nov 2008 (23:52 UTC)
xing88.117.24.1364
Current • Source
xing88.117.24.1363
View • Compare • Difference • Source
xing88.117.24.1362
View • Compare • Difference • Source
xing88.117.24.1361
View • Compare • Difference • Source