Andrew, Michael,
I've countersigned this agreement and put the invoices into process for payment.
I remind you that the agreement between the OMF Board and the OASIS Board is that an officer of OASIS/OODF must execute all contracts and commitments to payment. As guarantor for these operations that is a process requirement. We will always take your lead on technical matters - what work is necessary, if the delivered work is complete as you expect, etc. But the financial commitments and executions related to the work belong on our side of the table.
We'll get those overdue payments out asap, now we have all the paperwork,
Scott...
On Sun, Jun 25, 2023 at 3:56 PM Michael Schnuerle <
> wrote:
Scott,
Attached is the signed contract, and the modified scope of work.
1 - 2023-01-12-OMF-Compiler contract
1 - MDS 2.0 Schema Updates -
Michael
On Thu, Jun 22, 2023 at 2:29 PM Scott McGrath <
> wrote:
Let's also chase the paperwork for the contract, without which the invoices just collect dust...
On Thu, Jun 22, 2023 at 11:50 AM Andrew Glass Hastings <
> wrote:
Thanks. Sorry, I am not sure why they were addressed directly to you. Let me circle up with Michael and find out more.
Thanks! -AGH
Andrew Glass Hastings Executive Director
www.openmobilityfoundation.org @andrewgh @openmobilityfnd
On Jun 22, 2023, at 4:26 PM, Scott McGrath <
> wrote:
Just sent them. They were in my inbox, but I didn't act on them - assuming I was receiving them as a cc to accounting@. The accounting team is where the association to the contract and scheduled payments take place, or any disconnect is identified. That is why the contracts al direct invoices to be sent to accounting@
Scott...
On Thu, Jun 22, 2023 at 11:02 AM Andrew Glass Hastings <
> wrote:
I haven t seen any invoices. Have they been sent to you directly? Will you please forward to me for review?
Thanks much! -AGH
Andrew Glass Hastings Executive Director
www.openmobilityfoundation.org @andrewgh @openmobilityfnd
<PastedGraphic-3.tiff>
On Jun 22, 2023, at 3:54 PM, Scott McGrath <
> wrote:
Michael, Andrew,
What is the status of this agreement? I read Jamie's comments and edits as his input -but I do not see any record of them accepting the changes - or a subsequently executed contract. The message below is the most recent communication I find related to this proposed contract.
There are now a number of outstanding invoices for work done by Compiler.
Before I respond to them directly based on what I know so far(with an answer they may find less pleasing than a check;-)) let me ask you - do you point me to the missing paperwork authorizing this work?
Scott...
On Thu, Feb 2, 2023 at 2:38 AM Jamie Clark <
> wrote:
Hello Michael and Andrew. Scott forwarded this to me; apologies that this took a couple of days to touch and reply.
I have inserted suggestions into the Google Doc draft agreement. (A fixed copy as annotated also is attached.) THOSE edit suggestions presumably are visible to your contractor, but THESE email comments are not. I remember Kegan. So:
if Contractor gives you code and code documentation, and you use it, of course it's freely usable as part of MDS , due to your overall licensing.
(See Section 10 on page 5.)
And that may be all their contract drafter is worried about. But if Kegan also shipped other non-code work, like analysis or critique, the CC-BY-4 terms do not necessarily apply .
You might want control over such
m aterial , to be exclusively provided by Compiler for OMF ' s use (as the original contract form said) . See my edits to
his
new "License" clause in Exhibit A on p age 10.
However, if you don't care about control, and are happy to have him contribute
all
of his work to you
in the open,
you could accept the
rest
of it under CC-BY-4 terms as well ... and delete the [bracketed] clauses ... as long as you are willing to have your materials permanently carry his attribution (the "BY" condition).
regards, Jamie
mobile 1-310-293-6739
James Bryce Clark General Counsel & CPO
OASIS Open
Xing
LinkedIn
Twitter
Mastodon
Setting the standard for open collaboration .
----------
Forwarded message
---------
From:
Michael Schnuerle
< michael@ openmobilityfoundation .org
>
Subject: Fwd: [Compiler Partners] Re: MDS 2.0 schema work proposal
To: omf-staff < omf-staff@ openmobilityfoundation .org >, Scott McGrath <
>
Cc: Cathie Mayo <
>
Hi Scott,
Back in September 2021 we had a company called Compiler do some MDS work for us. We are asking them to do some more work and have a scope of work and agreement draft.
They did bring up some valid questions about the licensing and ownership language in the agreement. Here are their suggested edits from their lawyer since the OMF will not own their work and the work is open source.
https://docs.google.com/document/d/1O1aSaTBhS7BOXKHqW5zCAv9D_XkbNFq-3Q7IBHAmNeo/edit
Let me know what you think and if this is acceptable, or feel free to leave comments and suggested edits of your own directly in the document.
Thanks,
Michael Schnuerle Director of Open Source Operations
@ MichaelMobility
@ OpenMobilityFnd
--
Scott McGrath Chief Operating Officer OASIS Open
+1 781-929-7308 Mobile
www.oasis-open.org
--
Scott McGrath Chief Operating Officer OASIS Open
+1 781-929-7308 Mobile
www.oasis-open.org
--
Scott McGrath Chief Operating Officer OASIS Open
+1 781-929-7308 Mobile
www.oasis-open.org
--
Thanks, Michael Schnuerle Director of Open Source Operations @MichaelMobility
@OpenMobilityFnd
--
Scott McGrath Chief Operating Officer OASIS Open
+1 781-929-7308 Mobile
www.oasis-open.org
