| User | Post |
|
1:08 am
December 27, 2009
|
Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
As discussed earlier, I have created a Google code project for CSTART, with a Mercurical repository. The project is set up so that, by default, computer code in the repository is GPL3 licensed and anything else in their is CC-BY-SA-3.0 licensed, which means that all our Social Contract obligations should be taken care of. You can browse the repository here. So far the only actual code is a prototype of USOFS – but I've laid out a directory structure for CLLARE and OHKLA specific stuff.
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
5:04 am
December 27, 2009
|
rpulkrabek
| | |
| Member | posts 349 | |
|
|
I might need some instructions on how to use this. Who has the rights to upload or modify? Do we include any Matlab work (actually, should we convert to Octave?)? What about CAD files or FEA/CFD? What about pictures or screenshots we take? I noticed quickly you had a read me file, is that something we should strive to include for every file/program we upload?
|
|
|
5:30 am
December 27, 2009
|
Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
Yes, I was a little light on details about how to use this.
I might write a page in the Wiki tomorrow explaining how to use it properly. I'll post a link to it in this thread when I do so you can catch up quickly.
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
1:16 am
December 28, 2009
|
Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
Haven't gotten around to this yet, sorry. Just quickly:
Right now only I can actually commit to the repository but I can add anybody else with a google account to the list of project admins and then they will be able to do so as well – any of the regulars on this forum can let me know if they want an admin invite and I'll send it out.
However, the beauty of Mercurial is that anybody can create a local clone of the repository and work on it themselves (or with others), even doing their own local commits and rollbacks, etc. and then an admin can later merge this repository with the official one. The whole thing is very decentralised.
I think it makes sense to include CAD files and computer code in any language in the repository, and also official written documents (like familiarization manuals, etc.).
The README files are only there because Mercurial won't let you commit empty directories, so the only way I could esablish the basic directory structure of the repository (which I thought it important to get done quickly) was to put something in each directory. README files seemed like the least useless thing for this task.
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
2:44 am
December 30, 2009
|
Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
Post edited 8:49 am – December 30, 2009 by Luke Maurits
Detailed information on how to use the Google code facilities is gradually materialising at this Wiki page. I am still somewhat learning this stuff myself so if something doesn't work for reason please let me know.
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
9:18 am
December 30, 2009
|
Rocket-To-The-Moon
| | Altus, Oklahoma, USA | |
| Member | posts 685 | |
|
|
I don't really know much about this subject area, but it looks like a nice and organized way to do things. Basically it is a place to store all software that is written for CSTART to include the actual mission software that our ground control and spacecraft will run, correct? This allows programmers from all over the world to contribute to the software and make improvements.
|
Main Workgroups: Propulsion & Spacecraft Engineering
|
|
|
10:09 am
December 30, 2009
|
Luke Maurits
| | Adelaide, Australia | |
| Admin
| posts 1483 | |
|
|
Yes, the idea is that all our code goes in here – that includes mission planning stuff, mission control software, onboard software, the works. Even non-software stuff like CAD diagrams can be stored in the repository, with all the same benefits (access to previous versions, etc.). This will end up being a fairly authoritative source of data.
|
Main CLLARE workgroups: Mission Planning, Navigation and Guidance. I do maths, physics, C, Python and Java.
|
|
|
10:36 am
December 30, 2009
|
Rocket-To-The-Moon
| | Altus, Oklahoma, USA | |
| Member | posts 685 | |
|
|
That sounds great. Software is definitely a workgroup that has no real need to ever physically meet.
|
Main Workgroups: Propulsion & Spacecraft Engineering
|
|
|
11:41 am
January 20, 2010
|
rpulkrabek
| | |
| Member | posts 349 | |
|
|
I have now pushed my changes from my cloned repository to the official repository. There was no need for me to do any merge commands, which I originally thought. Here is what I did:
$ cd rapulkrabek-cstart-clone
$ hg push https://cstart.googlecode.com/hg/
Then entered user name and then entered password, which is a generated string found on the project page. I was also a bit surprised that I didn't need to commit any changes either. Well, I am slowly but surely learning.
If there are then changes to the repository, all I need to do is (I think):
$ cd rapulkrabek-cstart-clone
$ hg pull https://cstart.googlecode.com/hg/
Then enter name and password.
|
|
Login 
Register 
Search 
Home
Topic RSS 
