Finally---the software repo is now non-private
I have managed (thanks to some help from a friend) to remove all the old history from the repository I was working on (which included all the Golf code if you looked correctly), so I have now created a repository on gitHub AMSAT-NA/PacSatx which is open to viewing by all.
As requested, I included a Documentation directory and put Chris' doc in it.
A couple things:
1) I wanted to have everyone get a chance to look and approve what I did with the repo structure, but the next step will be to delete the AMSAT-NA/pacsat repo (which has the identical documenation) and rename PacSatx to PacSat (or whatever we decide). I did not want to delete it for now.
2) I'd have preferred to have two directory trees, code and documentation instead of having docs branching off the code tree. However, I could not get TI CCS (Code Composer Studio) to be happy with that. I'm sure it is possible but it would have taken a lot of work.
3) Feel free to clone this repository to take a look. I think the syntax on your local machine would be git clone https://github.com/AMSAT-NA/PacSatx.git
4) This code does not build successfully. It mostly compiles but there are lots of undefined references, which I will fix. I just wanted to make it available ASAP.
73,
Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*
Done and thanks.
Gonna need more coffee!
Jim McCullers
WA4CWI
I have managed (thanks to some help from a friend) to remove all the old history from the repository I was working on (which included all the Golf code if you looked correctly), so I have now created a repository on gitHub AMSAT-NA/PacSatx which is open to viewing by all.
As requested, I included a Documentation directory and put Chris' doc in it.
A couple things:
1) I wanted to have everyone get a chance to look and approve what I did with the repo structure, but the next step will be to delete the AMSAT-NA/pacsat repo (which has the identical documenation) and rename PacSatx to PacSat (or whatever we decide). I did not want to delete it for now.
2) I'd have preferred to have two directory trees, code and documentation instead of having docs branching off the code tree. However, I could not get TI CCS (Code Composer Studio) to be happy with that. I'm sure it is possible but it would have taken a lot of work.
3) Feel free to clone this repository to take a look. I think the syntax on your local machine would be git clone https://github.com/AMSAT-NA/PacSatx.git
4) This code does not build successfully. It mostly compiles but there are lots of undefined references, which I will fix. I just wanted to make it available ASAP.
73,
Burns Fisher, WB1FJ
AMSAT(R) Engineering -- Flight Software
Ok. I'm not 100% sure I have everything there to make it work even when I get it to build. I just wanted quickly to get it have nothing that one could consider ITAR/EAR from Golf (and I'm not really sure there is ANYTHING like that anyway) and make it visible/open.
Feel free to ask anything. My next step is to get it to run on the Launchpad with sort of minimal functionality. Boot and talk to a terminal. From then we can play some more.
73,
Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*
On Wed, Nov 9, 2022 at 5:12 PM Jim McCullers [email protected] wrote:
Done and thanks.
Gonna need more coffee!
Jim McCullers
WA4CWI
I have managed (thanks to some help from a friend) to remove all the old history from the repository I was working on (which included all the Golf code if you looked correctly), so I have now created a repository on gitHub AMSAT-NA/PacSatx which is open to viewing by all.
As requested, I included a Documentation directory and put Chris' doc in it.
A couple things:
- I wanted to have everyone get a chance to look and approve what I did
with the repo structure, but the next step will be to delete the AMSAT-NA/pacsat repo (which has the identical documenation) and rename PacSatx to PacSat (or whatever we decide). I did not want to delete it for now.
- I'd have preferred to have two directory trees, code and documentation
instead of having docs branching off the code tree. However, I could not get TI CCS (Code Composer Studio) to be happy with that. I'm sure it is possible but it would have taken a lot of work.
- Feel free to clone this repository to take a look. I think the syntax
on your local machine would be git clone https://github.com/AMSAT-NA/PacSatx.git
- This code does not build successfully. It mostly compiles but there
are lots of undefined references, which I will fix. I just wanted to make it available ASAP.
73,
Burns Fisher, WB1FJ
*AMSAT**(R) **Engineering -- Flight Software*
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
Looks good to me. And I see no reason to rename the repo btw. PacsatX sounds like a fine name for a new generation of Pacsats.
73 Chris
On Wed, Nov 9, 2022 at 6:04 PM Burns Fisher (AMSAT) [email protected] wrote:
Ok. I'm not 100% sure I have everything there to make it work even when I get it to build. I just wanted quickly to get it have nothing that one could consider ITAR/EAR from Golf (and I'm not really sure there is ANYTHING like that anyway) and make it visible/open.
Feel free to ask anything. My next step is to get it to run on the Launchpad with sort of minimal functionality. Boot and talk to a terminal. From then we can play some more.
73,
Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software*
On Wed, Nov 9, 2022 at 5:12 PM Jim McCullers [email protected] wrote:
Done and thanks.
Gonna need more coffee!
Jim McCullers
WA4CWI
I have managed (thanks to some help from a friend) to remove all the old history from the repository I was working on (which included all the Golf code if you looked correctly), so I have now created a repository on gitHub AMSAT-NA/PacSatx which is open to viewing by all.
As requested, I included a Documentation directory and put Chris' doc in it.
A couple things:
- I wanted to have everyone get a chance to look and approve what I did
with the repo structure, but the next step will be to delete the AMSAT-NA/pacsat repo (which has the identical documenation) and rename PacSatx to PacSat (or whatever we decide). I did not want to delete it for now.
- I'd have preferred to have two directory trees, code and documentation
instead of having docs branching off the code tree. However, I could not get TI CCS (Code Composer Studio) to be happy with that. I'm sure it is possible but it would have taken a lot of work.
- Feel free to clone this repository to take a look. I think the syntax
on your local machine would be git clone https://github.com/AMSAT-NA/PacSatx.git
- This code does not build successfully. It mostly compiles but there
are lots of undefined references, which I will fix. I just wanted to make it available ASAP.
73,
Burns Fisher, WB1FJ
*AMSAT**(R) **Engineering -- Flight Software*
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
pacsat-dev mailing list -- [email protected] View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected] To unsubscribe send an email to [email protected] Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org
participants (3)
-
Burns Fisher (AMSAT) -
Chris Thompson -
Jim McCullers