You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To help attract more contributors and readers of the source code, it would be helpful to create a FileList that gives brief descriptions of the directories and files involved in the project. This gives short explanations to files outside the range of rustdoc. Creating this list saves an effort repeated by each new potential contributor.
I propose a simple text file so that people can add constructive criticism to that level. I expect it a couple days to field comments on this issue before putting in the first pull request. A later issue will add a self-contained html page.
Thank you in advance for constructive comments.
I am proposing a text file that runs about six pages:
Project Directory Tree
+ .
+--+ .github
+--+--+ workflows Configuration files for automated tasks on github.com
+--+ docs Druid Book in mdBook format
+--+--+ book_examples
+--+--+--+ src Source of code examples included in book
+--+--+ src Chapters (or topics) of Druid Book
+--+ druid Implementation of druid
+--+ druid-derive Implementation of derive macros
+--+--+ src
+--+--+ tests
+--+--+--+ ui
+--+ druid-shell Common interface for elements across platforms
...
Directory .
Files:
.gitignore Patterns of files not to placed in git (source control)
AUTHORS Partial list of copyright holders (contributors)
Cargo.toml Config for Cargo (build system and package manager)
CHANGELOG.md Generated changelog of latest release
clippy.toml Documented config for clippy (lint) tool
...
The text was updated successfully, but these errors were encountered:
To help attract more contributors and readers of the source code, it would be helpful to create a FileList that gives brief descriptions of the directories and files involved in the project. This gives short explanations to files outside the range of rustdoc. Creating this list saves an effort repeated by each new potential contributor.
I propose a simple text file so that people can add constructive criticism to that level. I expect it a couple days to field comments on this issue before putting in the first pull request. A later issue will add a self-contained html page.
Thank you in advance for constructive comments.
I am proposing a text file that runs about six pages:
The text was updated successfully, but these errors were encountered: