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.

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

How to structure the files in your software project #195

Closed
shoaibsufi opened this issue Jan 14, 2025 · 7 comments · Fixed by #226
Closed

How to structure the files in your software project #195

shoaibsufi opened this issue Jan 14, 2025 · 7 comments · Fixed by #226
Assignees
Labels
new content request New page request

Comments

@shoaibsufi
Copy link
Collaborator

To create a task page titled - 'How to structure the files in your software project' - this is from the prioritised list of pages people would like from the Jan WP2 and TF1 meetings - you can see the list in the spreadsheet - https://docs.google.com/spreadsheets/d/1TMzE5umQ2rkS9POAmhlAPNptBKin4eC3YW3YbijGci4/edit?gid=0#gid=0

Please

@jmaassen
Copy link
Collaborator

Isn't this very language / build system / framework specific? While it's good to adhere to the 'standard' there are many to choose from ;-)

@shoaibsufi
Copy link
Collaborator Author

Add general concepts and then give specifics examples based on context (language, build system and framework)

@shoaibsufi
Copy link
Collaborator Author

Maybe @jmaassen should be a reviewer for this one

@egpbos
Copy link
Contributor

egpbos commented Jan 21, 2025

Also a separate folder for notebooks, tutorials, demos, etc. is common and useful (otherwise it gets hidden somewhere in src or code).

@graeme-a-stewart
Copy link

Shouldn't we give links to language specific documentation on this? I am not sure how useful general advice is. I don't care much how Python structures projects if I am writing a Julia package?

@stranak
Copy link

stranak commented Jan 24, 2025

Hi, this tool is mentioned on the https://rdmkit.elixir-europe.org/licensing page, but you decided not to link to it in RSQKit: https://github.com/ufal/public-license-selector

I am just curious, do you find the "guided approach" less efficient than describing everything in a long(ish) text?

We are the developers of the guide, and we are very happy to improve it if you think some important part, or notice, or a decision point is missing, and therefore you find it unsuitable.

Just wanted to put it forward, because I think that overall the content of our tool and this page is 95% the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new content request New page request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants