[General] sandboxes or branches for interns/SoC students

[Philippe Bossut]

Mike Taylor wrote:
> Not sure if I can offer any *specific* guidelines.
>
> The sandbox repository is where you can commit to so my understanding 
> was that you would checkout/export the trunk/chandler/ directory and 
> do an initial import into your sandbox as a starting point.
Bear is right: you put *whatever* you want in the sandbox, it's not part 
of the Tinderboxes, there's no test run against it. It's basically a 
facility so that you can have all the advantages of a source control 
system without any of the hassle. It also makes it easy to share stuff 
with others.

If you want to modify Chandler's code, you'll have to grab a version of 
it, put it in there and work from it. You should do that from a QA 
certified milestone (Xun used 6.1 but 0.7alpha2 is a better choice). 
Hack and do commits without being afraid of breaking the official build. 
For integration in the trunk, see with your mentor when you get there or 
engage people on the chandler-dev at .

Cheers,
- Philippe
>
>
> On Jun 1, 2006, at 5:05 PM, Ashkan Soltani wrote:
>
>> Hey Mike
>>
>> Can you give me a quick overview of how i should be working with the 
>> sandbox (or direct me to the particular url).
>>
>> I've already checked out a read-only copy of the chandler directory 
>> using the instructions outlined  on the 
>> GettingChandler/SubversionGuidelines page.  However, I'm not 
>> completely clear on how I integrate my sandbox into this workflow.
>>
>> Thanks again for setting this up.  Please let me know if you have 
>> more instruction.
>>
>> -a
>>
>>
>>
>>
>> On Jun 1, 2006, at 11:51 AM, Mike Taylor wrote:
>>
>>> I have created directories in the sandbox repositories for them and 
>>> have also given them access to the svn server.
>>>
>>> svn+ssh://svn.osafoundation.org/svn/sandbox/asoltani
>>>
>>> svn+ssh://svn.osafoundation.org/svn/sandbox/xluo
>>>
>>>
>>>
>>> On May 31, 2006, at 11:47 PM, Philippe Bossut wrote:
>>>
>>>> Mike Taylor wrote:
>>>>> I can work on this tomorrow.  All of the items are in place it's 
>>>>> just a matter of gathering the following information from each of 
>>>>> the people:
>>>>>
>>>>>     svn user id
>>>>>     ssh public key
>>>>>
>>>>> Once I have that information I can create user id's and make the 
>>>>> appropriate entries to the access config files.
>>>> Excellent!
>>>>
>>>> I saw that Ashkan already sent you those info. Xun, can you get 
>>>> that to Mike?
>>>>
>>>> Cheers,
>>>> - Philippe
>>>>
>>>>
>>> ---
>>> Bear
>>>
>>> Build and Release Engineer
>>> Open Source Applications Foundation (OSAF)
>>> bear at osafoundation.org
>>> http://www.osafoundation.org
>>>
>>> bear at code-bear.com
>>> http://code-bear.com
>>>
>>> PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29
>>>
>>>
>>>
>>
>>
> ---
> Bear
>
> Build and Release Engineer
> Open Source Applications Foundation (OSAF)
> bear at osafoundation.org
> http://www.osafoundation.org
>
> bear at code-bear.com
> http://code-bear.com
>
> PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29
>
>