From: "Calvin Morrison" <calvin@fastmailteam.com>
To: 9front@9front.org
Subject: Re: [9front] Bounty: OneDriveFS
Date: Mon, 19 Oct 2020 11:51:54 -0400 [thread overview]
Message-ID: <9dbe35c6-5edd-4dab-991c-46d346c3fd6c@www.fastmail.com> (raw)
In-Reply-To: <B4190FE0A67012FA9AF6BFD9AC1A8671@sirjofri.de>
More generally useful is implementing webdav I think, as OneDrive exports over that for customers (as well as some other services)
On Wed, Sep 30, 2020, at 6:31 AM, sirjofri+ml-9front@sirjofri.de wrote:
> Hello all,
>
> I have a bounty for you. 20€ for a OneDrive filesystem. We can still
> negotiate the requirements and money. If anybody wants this too and
> wants to add money to the pool, feel free to do it.
>
> I can also try to help, but only with my currently limited time and knowledge.
>
> The following list are btw more like ideas. We can always talk about it
> and in some cases it might make more sense to adjust things.
>
>
> Must Have (20€)
>
> * File management (full CRUD support).
> * Works with OneDrive.
> * Works with Sharepoint Drives.
> * Works with official Microsoft servers (office.com stuff).
>
> Should Have
>
> * User keys in factotum.
> * No complicated configuration. Auth info, drive (and maybe server?)
> should be enough.
> * Native C preferred (9front).
>
> Nice to Have (+5€)
>
> * Access versions: File versions are provided by OneDrive/Sharepoint.
> Use these.
> * Lazy caching: OneDrive protocol provides sha1sums. Files could be
> stored in a persistent cache (simple directory?). cat file >/dev/null&
> for manually caching is fine.
> * some way to show files are cached (maybe with ls?).
>
>
--
Calvin
next prev parent reply other threads:[~2020-10-19 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 10:31 sirjofri+ml-9front
2020-10-19 15:51 ` Calvin Morrison [this message]
2020-10-20 8:31 ` [9front] " sirjofri+ml-9front
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9dbe35c6-5edd-4dab-991c-46d346c3fd6c@www.fastmail.com \
--to=calvin@fastmailteam.com \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).