Re: summary of call with DAISY

> On 4 Sep 2018, at 14:37, Siegman, Tzviya <tsiegman@wiley.com <mailto:tsiegman@wiley.com>> wrote:
> 
> Hi Ivan, <>
> 
> I am hoping for that time frame as well.
> 
> To simplify matters, what if the donate button simply leads to the DAISY donation page? Then there is no data duplication.

I really think that would be the simplest.

You have any text that I should use for that? Do you have any other change to propose for the page?

Thx

Ivan


> 
> Tzviya
> 
> Tzviya Siegman
> Information Standards Lead
> Wiley
> 201-748-6884
> tsiegman@wiley.com <mailto:tsiegman@wiley.com>
> 
> From: Ivan Herman [mailto:ivan@w3.org <mailto:ivan@w3.org>]
> Sent: Saturday, September 1, 2018 1:02 AM
> To: Siegman, Tzviya <tsiegman@wiley.com <mailto:tsiegman@wiley.com>>
> Cc: W3C Publishing Steering Committee <public-publishing-sc@w3.org <mailto:public-publishing-sc@w3.org>>; Richard Orme <rorme@daisy.org <mailto:rorme@daisy.org>>
> Subject: Re: summary of call with DAISY
> 
> Tzviya,
> 
> The Web site is indeed there, but there is one thing. We said we would have a form for payment. The idea we has so far is to have a form (eg, via WBS of W3C or google forms) to register the user's data plus a payment. However, I wonder whether that is the best format, because if the payment goes through Daisy then, I presume, they would have to have an immediate access with the name and organization to perform the payment, meaning that the user would have to type in the data twice. Wouldn't it be better to combine the collection of data and the effective payment at one place, which would then be at Daisy?
> 
> The practicality is that I will be on my way to Tokyo on Wednesday September 12, and I will be mostly on vacations for 10 days (apart from the two workshop days). This means I may be offline. The web site is on github[1], ie, you can make pull requests for any changes that must be done on the page content but, at this point, only staff members have admin access to that site (which is the repo for thehttps://www.w3.org/publishing/ <https://www.w3.org/publishing/> page on W3C). Ideally, we should have everything final on the page before I am out of reach...
> 
> Cheers
> 
> Ivan
> 
> [1] https://github.com/w3c/publishing <https://github.com/w3c/publishing>
> 
> 
> 
> On 31 Aug 2018, at 19:21, Siegman, Tzviya <tsiegman@wiley.com <mailto:tsiegman@wiley.com>> wrote:
> 
> Hi All,
> 
> I had a great call with George and Richard Orme, CEO of DAISY this morning to talk about logistics of epubcheck fundraising and getting started on the SOW and MOU.
> 
> Richard will join us for next week (7 September) SC call to follow up on details.
> 
> Here are my notes:
> 
> Website
> We (Pub SC) already has a website ready to go, thanks to Ivan and the SC’s efforts to prepare copy.
> We should be prepared to go live in about 1.5 weeks
> 
> Donation and invoicing mechanism
> DAISY has worked on similar fundraising projects with organizations such as WIPO in the past. This will appear as a line item in the audit.
> 
> Our expectation is that there will be some amount of set up for the payments system, but minimal processing because our best guess is that there will be a small number of larger donations. If that is the case, then there will be a fee of approximately $1000 for DAISY’s services. Richard will confirm that amount next week. If (as a result of the tremendous success of the campaign) DAISY needs to devote more time and resources, we will revisit that amount.
> 
> DAISY will be able to help us with the “donate here” mechanism. The software can accept wire transfer, check, or PayPal. PayPal allows for credit cards with a small commission (2.something %).
> 
> Donors can request an invoice and pay upon invoicing.
> 
> Funds will be restricted to this specific project, bound by the terms we set. We need to establish in our MOU what happens with any funds that remain at the end of the project. George has suggested that any unused funds go to the PBG for not yet identified projects.
> 
> DAISY will set this up via their US not-for-profit, which is a 501c3. DAISY will offer an option to check a box if donors would like a receipt for a charitable donation.
> 
> VAT is not a concern because this is the US arm of DAISY.
> 
> We plan to send thank you letters to donors automatically. Please be in touch if you’d like to write the thank you letter.
> 
> SOW and MOU:
> Richard has sent me an MOU that DAISY used with another organizations in the past. It is more detailed than what we need, but it is a starting point. We are looking for a lightweight MOU to set the payment terms and an SOW to set the timelines and milestones. I will work with Luc and DAISY based on their proposal to hammer this out. I will also consult with a Wiley colleague who has advised on MOUs in the past. The MOU will also help establish the dividing line between DAISY as a donation collector with a discreet fund for this project and DAISY as the developer.
> 
> Permission to use logos:
> We plan to display logos of organizations that donate to epubcheck on the epubcheck site/fundraising website. We need to get formal permission for this. W3C has a permissions agreement, and I will work with Wendy Seltzer to get that to donors. Some donors may not want their logos display, and we need to respect that as well.
> 
> Getting started on the work:
> We can get the fundraising site launched before the MOU and SOW are completed. At next week’s SC meeting we hope to finalize the details of the fundraising and go live with the website. Once DAISY has the donation tooling in place, we can send the link to those organizations that have committed to donate and link it to the website.
> 
> We cannot begin the actual work until we have an MOU in place, so it’s important that we move quickly.
> 
> We think that it’s okay to begin the work before we’ve raised the entirety of the funds. We just have to keep at the fundraising to ensure that we can pay our fine development team.
> 
> Feedback welcome!
> 
> Tzviya
> 
> Tzviya Siegman
> Information Standards Lead
> Wiley
> 201-748-6884
> tsiegman@wiley.com <mailto:tsiegman@wiley.com>
> 
> 
> ----
> Ivan Herman, W3C
> Publishing@W3C Technical Lead
> Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
> mobile: +31-641044153
> ORCID ID: https://orcid.org/0000-0003-0782-2704 <https://orcid.org/0000-0003-0782-2704>

----
Ivan Herman, W3C
Publishing@W3C Technical Lead
Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
mobile: +31-641044153
ORCID ID: https://orcid.org/0000-0003-0782-2704 <https://orcid.org/0000-0003-0782-2704>