> it may be easier to use grabCAD. It is a similar to git in the sense that
it is revision control, however it is geared towards CAD. One of the most
useful functions is; a user can checkout a file (or group) and it locks
that file from other users editing it.

Yeah, that may be a good solution. I'm a little wary of bringing in *even
more* tools, but it would be good to have something other than "let's agree
to only edit these parts".

> march for science

Agh, that's right. It's the same day and time here too...

-- Joe Shields <https://joedang.github.io/>

On Sun, Apr 16, 2017 at 9:25 AM, Jeremy Louke <jalo...@gmail.com> wrote:

> if there is a problem with conflicts because of a lot of people working on
> an assembly, it may be easier to use grabCAD. It is a similar to git in the
> sense that it is revision control, however it is geared towards CAD. One of
> the most useful functions is; a user can checkout a file (or group) and it
> locks that file from other users editing it. I set it up with a previous
> revision of the Oresat structure, but I never really utilized it because i
> was the only one doing the CAD back then. I was however thinking of having
> both PSAS and Oresat switch all CAD to grabCAD at one point because it is
> better suited to CAD than github.
>
> Maybe it's something we should revisit with so many people all working on
> one assembly.
>
> I unfortunately won't be able to join this weekend, as I am going to the
> march for science in LA.
>
>
> On Apr 16, 2017 7:46 AM, "Joseph Shields" <shiel...@pdx.edu> wrote:
>
>> It looks like the best time for the OreSat structure meeting would be
>> Saturday morning. So, let’s plan to meet at *10 am on Saturday* in the
>> rocket room and/or the hangout <http://psas.pdx.edu/hangout>.
>>
>> I added some later times to the poll and forgot to tell anyone. So, if
>> you really want the meeting to be at one of those later times, I guess you
>> can give a holla.
>>
>> I think the main stuff we want to do at this meeting is help each other
>> with any clarifications and *pick some parts to convert before the next
>> meeting*. (It might also be good to talk about what we plan to change,
>> so we don’t constantly create merge conflicts with the assemblies. We could
>> also just use branches for this.)
>> day time max yes maybe max non-no
>> Thu. 12-2 pm 4 1 4
>> Fri. 6-7 pm 4 0 4
>> *Sat.* *10 am-1 pm* 4 2 *5*
>> Sat. 4-7 pm 4 0 4
>> Sun. 5-7 pm 4 0 4
>>
>> The reason for choosing this time is to get all the people who are
>> working on converting the model to attend. (And also just to get the
>> maximum number of people to attend.)
>> ​
>>
>> -- Joe Shields <https://joedang.github.io/>
>>
>> On Mon, Apr 10, 2017 at 9:21 PM, Joseph Shields <shiel...@pdx.edu> wrote:
>>
>>> Hey airframe list,
>>> We need to pick a new time for the OreSat strucutre meeting
>>> <http://doodle.com/poll/5esq23qxci38zwvw>, since the old one doesn’t
>>> work any more didn’t work. As usual, this isn’t a poll for the
>>> *specific* days you’re free, but rather the *day’s of the week* you’re
>>> usually free.
>>>
>>> In the near future this is just a time to all sit down with SolidWorks
>>> and get each other unstuck or assign parts to migrate. In the less near
>>> future, this is about designing the antenna deployment.
>>> ​
>>> -- Joe Shields <https://joedang.github.io/>
>>>
>>
>>
>> _______________________________________________
>> psas-airframe mailing list
>> psas-airframe@lists.psas.pdx.edu
>> http://lists.psas.pdx.edu/mailman/listinfo/psas-airframe
>>
>>
_______________________________________________
psas-airframe mailing list
psas-airframe@lists.psas.pdx.edu
http://lists.psas.pdx.edu/mailman/listinfo/psas-airframe

Reply via email to