User talk:Keshav - Revision history

Keshav: /* '''Building in Eclipse''' */

2006-01-31T01:50:44Z

‎'''Building in Eclipse'''

Keshav: /* '''Building in Eclipse''' */

2006-01-31T01:50:24Z

‎'''Building in Eclipse'''

Floratos: /* Open Source Component */

2006-01-24T04:49:28Z

‎Open Source Component

Floratos: /* Closed Source Component */

2006-01-24T04:48:56Z

‎Closed Source Component

Floratos: /* Unix File Permissions */

2006-01-24T04:47:58Z

‎Unix File Permissions

Floratos: /* CVS Paths */

2006-01-24T04:46:24Z

‎CVS Paths

Keshav: /* Open Source Component */

2006-01-23T22:14:04Z

‎Open Source Component

Keshav: /* Open Source Component */

2006-01-23T22:11:15Z

‎Open Source Component

Keshav: /* '''Use Cases''' */

2006-01-23T19:19:33Z

‎'''Use Cases'''

Keshav: /* Closed Source Component */

2006-01-23T19:17:50Z

‎Closed Source Component

@@ Line 6: / Line 6: @@
 Checkout geworkbench from adcvs.cu-genome.org/cvs/acallab.  In exclipse this looks like :extssh:keshav@adcvs.cu-genome.org:/cvs/acallab
 Add the following to the build path:
 == Folders ==

@@ Line 6: / Line 6: @@
 Checkout geworkbench from adcvs.cu-genome.org/cvs/acallab.  In exclipse this looks like :extssh:keshav@adcvs.cu-genome.org:/cvs/acallab
 Add the following to the build path:
 == Folders ==

@@ Line 132: / Line 132: @@
 The component directory would have the following unix permissions:
-    drwxrwsr--    2 cvsadmin gewcompCGrp     /cvs/magnet/component/componentC
+    drwxrwsr--    2 cvsadmin gewcompCGrp     /cvs/magnet/geWorkbenchComponents/componentC
 === CVS Paths ===

@@ Line 97: / Line 97: @@
 The core directory would have the following unix permissions:
-    drwxrws---    2 cvsadmin gewcompAGrp     /cvs/magnet/component/componentA
+    drwxrws---    2 cvsadmin gewcompAGrp     /cvs/magnet/geWorkbenchComponents/componentA
 - all other users would not have read access to this source code (this difference from open source component development).  If those developing componentA would like to give access to a developer working on componentB, the componentB developer would be added to gewcompBGrp.  For instance, before adding a developer from gewcompBGrp to gewcompAGrp, we would have:

@@ Line 78: / Line 78: @@
 The core directory would have the following unix permissions:
-    drwxrws---    2 cvsadmin gewcoreGrp     /cvs/magnet/core
+    drwxrws---    2 cvsadmin gewcoreGrp     /cvs/magnet/geWorkbenchCore
 == Components ==

@@ Line 137: / Line 137: @@
 Use the following repository paths to connect to the geWorkbench projects (this is how it is now ... it could change):
-    /cvs/geworkbench - The geWorkbench project (geWorkbench core project)
+    /cvs/magnet/geWorkbenchCore - The geWorkbench project (geWorkbench core project)
-    /cvs/components - The Component project (multiple component projects developed by third party developers).
+    /cvs/magnet/geWorkbenchComponents - The Component project (multiple component projects developed by third party developers).
 We will have to give users committer access to their specific project.
 For example, the cvs root could be something like:
-/cvs/components/foobar
+/cvs/magnet/geWorkbenchComponents/foobar
 === Bug Tracking/Issue Tracking ===

← Older revision		Revision as of 22:14, 23 January 2006
Line 133:		Line 133:

	drwxrwsr-- 2 cvsadmin gewcompCGrp /cvs/magnet/component/componentC		drwxrwsr-- 2 cvsadmin gewcompCGrp /cvs/magnet/component/componentC
−
−	~~[[Image:Magnet_CVS_Structure.jpg]]~~

	=== CVS Paths ===		=== CVS Paths ===

← Older revision		Revision as of 22:11, 23 January 2006
Line 133:		Line 133:

	drwxrwsr-- 2 cvsadmin gewcompCGrp /cvs/magnet/component/componentC		drwxrwsr-- 2 cvsadmin gewcompCGrp /cvs/magnet/component/componentC
		+
		+	[[Image:Magnet_CVS_Structure.jpg]]

	=== CVS Paths ===		=== CVS Paths ===

@@ Line 40: / Line 40: @@
 == '''Use Cases''' ==
-=== '''Core''' ===
+== Core ==
 '''Anonymous Access (eg. a component developer)'''

@@ Line 109: / Line 109: @@
     ''' gewcompAGrp::135:watkin,keshav '''
-User keshav would now have rw privileges to componentA.  Note that we cannot just give 'r privileges' to keshav because the permissions set on componentA is g+rws.  Setting componentA  '''g+r''' is not an option using standard unix file permissions because you can only attach one access group to a file/directory.  An alternative is to use '''AFS Access Control Lists (ACLs)''' which would allow us to give read permissions to individuals outside the component grp, but not allow them to write to the component directory ... while this is an option, I think it is safe to assume that if developers from grpA would like to disclose their source code to someone from grpB and the project is closed source, the reason is due to extenuating circumstances and they probably need the user from grpB to make a hack of some sort.  Thus, more often than not you will need to give the grpB developer write access as well.
+User keshav would now have rw privileges to componentA.  Note that we cannot just give '''r''' privileges to keshav because the permissions set on componentA is '''g+rws'''.  Setting componentA  '''g+r''' is not an option using standard unix file permissions because you can only attach one access group to a file/directory.  An alternative is to use '''AFS Access Control Lists (ACLs)''' which would allow us to give read permissions to individuals outside the component grp, but not allow them to write to the component directory ... while this is an option, I think it is safe to assume that if developers from grpA would like to disclose their source code to someone from grpB and the project is closed source, the reason is due to extenuating circumstances and they probably need the user from grpB to make a hack of some sort.  Thus, more often than not you will need to give the grpB developer write access as well.
 === Open Source Component ===