I thought the idea was to us SVN for those documents? If more is needed let's just use the wiki that is part of www.squeaksource.com/Cryptography
It's not a full wiki in that it doesn't appear to support file uploads but that what I thought the google source was for.
Can we map out what our requirements are and what our current resources are for meeting those requirements, then we can look at what more we need.
What I see is:
www.squeaksoruce.com/Cryptography = Code Repository and limited wiki
http://code.google.com/p/squeak-cc-validation/ = Validation documentation, plan and test results, bug tracking. This should not hold code.
cryptography@lists.squeakfoundation.org is our mailing list.
Ron
-----Original Message----- From: cryptography-bounces@lists.squeakfoundation.org [mailto:cryptography-bounces@lists.squeakfoundation.org] On Behalf Of Krishna Sankar Sent: Tuesday, October 17, 2006 11:11 AM To: 'Cryptography Team Development List' Subject: RE: [Cryptography Team] Common Criteria Documentation...
Kyle,
Can you see if you have the SVN write access ? All, Just as FYI, we need gmail address to become part of the Google project and it has no Wiki. Any thoughts on the Wiki for us to document the functionalities and the results of development/testing ?
Cheers
<k/>
-----Original Message----- From: cryptography-bounces@lists.squeakfoundation.org [mailto:cryptography-bounces@lists.squeakfoundation.org] On Behalf Of Kyle Hamilton Sent: Monday, October 16, 2006 8:33 PM To: Cryptography Team Development List Subject: [Cryptography Team] Common Criteria Documentation...
I found the Google Code project that Krishna started, and uploaded the Common Criteria documentation I found (in PDF form) to it as an issue. Unfortunately, I don't have SVN write access, and I don't know how to get it either.
After reading it, I realized that it /IS/ a good idea for anyone starting on CC validation to read it before they start. It's important to realize what it is, and what the goals must be. (As well, it also helps customers -- that'd include you, Ron -- understand what the various validation levels are, and compare them to regulatory requirement.)
--
-Kyle H I speak only for myself. I don't have the faintest clue about anyone else. _______________________________________________ Cryptography mailing list Cryptography@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/cry ptography
Cryptography mailing list Cryptography@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/cryptography
http://code.google.com/p/squeak-cc-validation/ = Validation documentation, plan and test results, bug tracking. This should not hold code.
<KS>
I would prefer to hold the validation documentation, plan and test results in a Wiki. That way we have built-in revision control as well as history tracking. In that sense the Google projects do not help us.
The bug tracking in Google projects is fine.
</KS>
-----Original Message----- From: cryptography-bounces@lists.squeakfoundation.org [mailto:cryptography-bounces@lists.squeakfoundation.org] On Behalf Of Ron Teitelbaum Sent: Tuesday, October 17, 2006 9:34 AM To: 'Cryptography Team Development List' Subject: RE: [Cryptography Team] Common Criteria Documentation...
I thought the idea was to us SVN for those documents? If more is needed let's just use the wiki that is part of www.squeaksource.com/Cryptography
It's not a full wiki in that it doesn't appear to support file uploads but that what I thought the google source was for.
Can we map out what our requirements are and what our current resources are for meeting those requirements, then we can look at what more we need.
What I see is:
www.squeaksoruce.com/Cryptography = Code Repository and limited wiki
http://code.google.com/p/squeak-cc-validation/ = Validation documentation, plan and test results, bug tracking. This should not hold code.
cryptography@lists.squeakfoundation.org is our mailing list.
Ron
-----Original Message----- From: cryptography-bounces@lists.squeakfoundation.org [mailto:cryptography-bounces@lists.squeakfoundation.org] On
Behalf Of
Krishna Sankar Sent: Tuesday, October 17, 2006 11:11 AM To: 'Cryptography Team Development List' Subject: RE: [Cryptography Team] Common Criteria Documentation...
Kyle,
Can you see if you have the SVN write access ? All, Just as FYI, we need gmail address to become part of the Google project and it has no Wiki. Any thoughts on the Wiki for us to document the functionalities and the results of
development/testing ?
Cheers
<k/>
-----Original Message----- From: cryptography-bounces@lists.squeakfoundation.org [mailto:cryptography-bounces@lists.squeakfoundation.org]
On Behalf
Of Kyle Hamilton Sent: Monday, October 16, 2006 8:33 PM To: Cryptography Team Development List Subject: [Cryptography Team] Common Criteria Documentation...
I found the Google Code project that Krishna started, and
uploaded
the Common Criteria documentation I found (in PDF form) to it as an issue. Unfortunately, I don't have SVN write access, and I
don't know how
to get it either.
After reading it, I realized that it /IS/ a good idea for anyone starting on CC validation to read it before they start. It's important to realize what it is, and what the goals must be. (As well, it also helps customers -- that'd include you, Ron -- understand what the various validation levels are, and
compare them
to regulatory requirement.)
--
-Kyle H I speak only for myself. I don't have the faintest clue about anyone else. _______________________________________________ Cryptography mailing list Cryptography@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/cry ptography
Cryptography mailing list Cryptography@lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/cryptograph
y
Cryptography mailing list Cryptography@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/cry
ptography
cryptography@lists.squeakfoundation.org
-
Krishna Sankar -
Ron Teitelbaum