Update README
This commit is contained in:
parent
113c4b1f7f
commit
e8ebe8f88b
1 changed files with 25 additions and 20 deletions
45
README.md
45
README.md
|
@ -23,12 +23,10 @@ Our (long-term) goal is to
|
||||||
|
|
||||||
Yes, imag is a rather ambitious project as it tries to reimplement functionality
|
Yes, imag is a rather ambitious project as it tries to reimplement functionality
|
||||||
for several "personal information management aspects". It is a hobby project,
|
for several "personal information management aspects". It is a hobby project,
|
||||||
keep that in mind. We try to use standards like vcard and icalendar wherever
|
keep that in mind. We try to use standards like vcard, icalendar and others
|
||||||
possible.
|
wherever possible.
|
||||||
|
|
||||||
imag consists of _modules_ (e.g. `imag-notes`, `imag-tag`, `imag-view`), where
|
Have a look at [the documentation](./doc/) for some more words on this.
|
||||||
each module covers one PIM aspect. Have a look at
|
|
||||||
[the documentation](./doc/) for some more words on this.
|
|
||||||
|
|
||||||
|
|
||||||
## Building/Running
|
## Building/Running
|
||||||
|
@ -48,6 +46,18 @@ Make sure to use a recent `cargo`, at least one with workspace support.
|
||||||
Building all crates works with `cargo build --all`, building individual crates
|
Building all crates works with `cargo build --all`, building individual crates
|
||||||
by `cd`ing to their directory and calling `cargo build`.
|
by `cd`ing to their directory and calling `cargo build`.
|
||||||
|
|
||||||
|
For building all commandline applications:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
find bin -maxdepth 3 -name Cargo.toml -exec cargo build --manifest-path {} \;
|
||||||
|
```
|
||||||
|
|
||||||
|
For building only the core functionality
|
||||||
|
|
||||||
|
```bash
|
||||||
|
find bin/core -maxdepth 3 -name Cargo.toml -exec cargo build --manifest-path {} \;
|
||||||
|
```
|
||||||
|
|
||||||
### Running
|
### Running
|
||||||
|
|
||||||
After you build the module you want to play with, you can simply call the binary
|
After you build the module you want to play with, you can simply call the binary
|
||||||
|
@ -57,48 +67,43 @@ If you installed the module, you can either call `imag-<modulename>` (if the
|
||||||
install-directory is in your `$PATH`), or install the `imag` binary to call `imag
|
install-directory is in your `$PATH`), or install the `imag` binary to call `imag
|
||||||
<modulename>` (also if everything is in your `$PATH`).
|
<modulename>` (also if everything is in your `$PATH`).
|
||||||
|
|
||||||
|
|
||||||
## Staying up-to-date
|
## Staying up-to-date
|
||||||
|
|
||||||
We have a [official website for imag](https://imag-pim.org), where I post
|
We have a [official website for imag](https://imag-pim.org), where I post
|
||||||
[release notes](http://imag-pim.org/releases/) and monthly(ish) updates what's
|
[release notes](http://imag-pim.org/releases/) and monthly(ish) updates what's
|
||||||
happening in the source tree ([RSS here](https://imag-pim.org/index.xml)).
|
happening in the source tree ([RSS here](https://imag-pim.org/index.xml)).
|
||||||
|
|
||||||
|
|
||||||
We also have a [mailinglist](https://imag-pim.org/mailinglist/) where I post
|
We also have a [mailinglist](https://imag-pim.org/mailinglist/) where I post
|
||||||
updates and where discussion and questions are encouraged.
|
updates and where discussion and questions are encouraged.
|
||||||
|
|
||||||
|
|
||||||
## Documentation
|
## Documentation
|
||||||
|
|
||||||
This is a hobby project, so sometimes things are not optimal and might go
|
We have some documentation in [the ./doc subtree](./doc/)
|
||||||
unrecognized and slip through. Feel free to open issues about things you notice!
|
|
||||||
|
|
||||||
Though, we have some documentation in [the ./doc subtree](./doc/)
|
|
||||||
which can be compiled to PDF or a website.
|
which can be compiled to PDF or a website.
|
||||||
These docs are not published anywhere and are not even integrated into our CI,
|
It might not be up to date, though.
|
||||||
so it might be broken (though it's unlikely).
|
Developer documentation for the last release is available
|
||||||
Developer documentation is also available
|
[on docs.rs](https://docs.rs/releases/search?query=imag).
|
||||||
[online on github.io](https://matthiasbeyer.github.io/imag/imag_documentation/index.html)
|
|
||||||
and [on docs.rs](https://docs.rs/releases/search?query=imag), though they might
|
|
||||||
be a bit outdated.
|
|
||||||
|
|
||||||
## Please contribute!
|
## Please contribute!
|
||||||
|
|
||||||
We are looking for contributors!
|
We are looking for contributors!
|
||||||
|
|
||||||
Feel free to open issues for asking questions, suggesting features or other
|
Feel free to open issues for asking questions, suggesting features or other
|
||||||
things!
|
things!
|
||||||
|
|
||||||
Also have a look at [the CONTRIBUTING.md file](./CONTRIBUTING.md)!
|
Also have a look at [the CONTRIBUTING.md file](./CONTRIBUTING.md)!
|
||||||
|
|
||||||
## Contact
|
|
||||||
|
|
||||||
Have a look at [our website](https://imag-pim.org) where you can find some
|
## Contact
|
||||||
information on how to get in touch and so on.
|
|
||||||
|
|
||||||
Feel free to join our new IRC channel at freenode: #imag
|
Feel free to join our new IRC channel at freenode: #imag
|
||||||
or our [mailinglist](https://imag-pim.org/mailinglist/).
|
or our [mailinglist](https://imag-pim.org/mailinglist/).
|
||||||
|
|
||||||
|
|
||||||
## License
|
## License
|
||||||
|
|
||||||
We chose to distribute this software under terms of GNU LGPLv2.1.
|
We chose to distribute this software under terms of GNU LGPLv2.1.
|
||||||
|
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue