Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open? #1

Open
gregmacfarlane opened this issue Jul 11, 2016 · 2 comments
Open

Open? #1

gregmacfarlane opened this issue Jul 11, 2016 · 2 comments

Comments

@gregmacfarlane
Copy link

Is there a compelling reason to keep this closed with the proprietary warning? I'd rather show off what we can do than keep our jewels like a troll.
@4Step
Copy link

4Step commented Jul 11, 2016

I prefer is to keep project related stuff open (to show off) but keep the tools and development work under close door.

@PeterKucirek
Copy link
Collaborator

PeterKucirek commented Jul 11, 2016 •
edited
Loading

I'd like to, once I've figured out what to call Bill's FORTRAN binary format.Referring to it that way is a more than just a tad obfuscated.

Also, I've removed the "proprietary" warning. I was over-zealous there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@gregmacfarlane @PeterKucirek @4Step