Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewrite and Review Supplier Agreement #283

Closed
ghost opened this issue Apr 11, 2017 · 26 comments
Closed

Rewrite and Review Supplier Agreement #283

ghost opened this issue Apr 11, 2017 · 26 comments
Labels
blocker priority-1 Highest priority issue. This is costing us money every minute that passes. T1h Time Estimate 1 Hour

Comments

@ghost
Copy link

ghost commented Apr 11, 2017

Mark has written draft:
https://docs.google.com/document/d/1Le14_UyBBe-ADoCJS1yUvK266WE2ffETBnAVSadfM88/edit#

Inês to review

@ghost ghost added the priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished label Apr 11, 2017
@ghost ghost assigned iteles Apr 11, 2017
@ghost ghost added priority-1 Highest priority issue. This is costing us money every minute that passes. and removed priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished labels Apr 12, 2017
@ghost ghost closed this as completed May 8, 2017
@ghost
Copy link
Author

ghost commented May 19, 2017

Please note when I originally wrote the contract I defined working day as follows:

“Working Day(s)” means eight (8) hours of accrued work by Supplier.

I have now updated this to:

“Working Day(s)” means seven (7) hours of accrued work by Supplier.

@ghost
Copy link
Author

ghost commented May 19, 2017

@iteles to review contract

@ghost ghost reopened this May 19, 2017
@iteles
Copy link
Member

iteles commented May 23, 2017

Reviewed! And left comments.

Need to get this out to a client so please make it the top priority 👍

@iteles iteles added the blocker label May 23, 2017
@iteles iteles assigned ghost and unassigned iteles May 23, 2017
@ghost
Copy link
Author

ghost commented May 24, 2017

@iteles I have replied to your comments in the doc

@ghost ghost assigned iteles and unassigned ghost May 24, 2017
@iteles
Copy link
Member

iteles commented May 24, 2017

@markwilliamfirth Have resolved the majority of the questions and replied to your replies 😉

@iteles iteles assigned ghost and unassigned iteles May 24, 2017
@ghost
Copy link
Author

ghost commented May 25, 2017

@iteles I have replied to your replies to my replies 😉

@ghost ghost assigned iteles and unassigned ghost May 25, 2017
@ghost
Copy link
Author

ghost commented May 31, 2017

@iteles I think it is only clause 16 that requires attention now

@iteles iteles added the T1h Time Estimate 1 Hour label May 31, 2017
@ghost
Copy link
Author

ghost commented Jun 7, 2017

Mark to add no approaching clause

@ghost ghost self-assigned this Jun 7, 2017
@ghost ghost added priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished and removed priority-1 Highest priority issue. This is costing us money every minute that passes. labels Jun 7, 2017
@ghost
Copy link
Author

ghost commented Jun 8, 2017

@iteles this was actually already included (clause 33)

No Party to this Agreement will, during and for a period of six (6) months following the expiry or termination of this Agreement, induce any employee of the other Party who was directly involved in the performance of this Agreement, to leave such other Party’s employment.

Let me know if you'd like it changing

Next step in this issue is for you to review clause 16 and let me know if you're happy with it

@ghost ghost removed their assignment Jun 8, 2017
@iteles iteles assigned ghost and unassigned iteles Jun 8, 2017
@iteles iteles added priority-1 Highest priority issue. This is costing us money every minute that passes. and removed priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished labels Jun 8, 2017
@ghost
Copy link
Author

ghost commented Jun 8, 2017

@iteles I responded back

@iteles
Copy link
Member

iteles commented Jun 8, 2017

And me :) I agree - let's keep the open source/non-open source details in the schedule and refer to the schedule in the main body of the document

@ghost
Copy link
Author

ghost commented Jun 8, 2017

@iteles I've updated - if you're happy then please send me the client details and I can create the first contract

@ghost ghost assigned iteles and unassigned ghost Jun 8, 2017
@iteles
Copy link
Member

iteles commented Jun 8, 2017

If we're going to go this route, I think we want to start with OSS as the default as it better reflects our values. I've suggested:

The code and documentation created by the Supplier for the Project will be covered by an open source license (https://opensource.org/licenses) to will be mutually agreed by both Parties. Should the Client decide that the Project will be closed source, all Intellectual Property Rights associated with the Project shall be owned by the Client. The agreed Intellectual Property Rights for the Project are outlined in Schedule 1.

Will send you the details

@ghost
Copy link
Author

ghost commented Jun 8, 2017

Have reworded slightly

All Intellectual Property Rights associated with the Project shall be owned by the Client, except the code and documentation created by the Supplier, to which the Client hereby expressly agrees and understands that it will be assigned by default to an open-source license (https://opensource.org/licenses), which will be mutually agreed by both Parties. The Client may opt-out of making the Project open-source and thus retain complete Intellectual Property Rights, confirmation of the Project’s open/closed source status shall be outlined in Schedule 1.

@iteles
Copy link
Member

iteles commented Jun 8, 2017

Open source doesn't have a hyphen, but other than that, this is fine.
I would make the last section of the last sentence a sentence in its own right.

@ghost
Copy link
Author

ghost commented Jun 8, 2017

Updated 👍

@iteles iteles closed this as completed Jun 8, 2017
@ghost ghost mentioned this issue Jun 22, 2017
3 tasks
@ghost ghost reopened this Aug 1, 2017
@iteles
Copy link
Member

iteles commented Aug 1, 2017

@markwilliamfirth Why was this reopened?
I would suggest that given stated priorities, this is really not as important this week as dwyl/process-handbook#35

@ghost
Copy link
Author

ghost commented Aug 1, 2017

Yep - it's behind it in priorities - was just updating github as it was on my other todo list

@ghost
Copy link
Author

ghost commented Aug 18, 2017

This is a p1 now after various frictions that have occurred with MV

@iteles
Copy link
Member

iteles commented Aug 18, 2017

#321 is a higher priority than this. I'm not sure how useful it is to move everything else to a p1 until that is complete.

@ghost
Copy link
Author

ghost commented Aug 25, 2017

  • Include clause allowing time for dwyl team retrospective

@iteles
Copy link
Member

iteles commented Aug 25, 2017

?! A retrospective is an essential part of the agile development process. It's never a question.
Are you proposing we add all of our ceremonies into our contracts?

@iteles iteles assigned ghost and unassigned iteles Sep 27, 2017
@ghost
Copy link
Author

ghost commented Oct 9, 2017

Interest on late payments

@iteles
Copy link
Member

iteles commented Oct 9, 2017

Is this a suggestion that charging interest on late payments should be added to our contracts with clients in light of the 2 client non-payment of invoices and 1 client who is paying us 3 months past the due date of invoices?

It would be a great idea to do a little research and suggest a sensible (spurs action but doesn't offend) interest rate 👍

@jammur jammur unassigned ghost Dec 14, 2017
@iteles
Copy link
Member

iteles commented Apr 16, 2018

Closing in favour of #459

@iteles iteles closed this as completed Apr 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker priority-1 Highest priority issue. This is costing us money every minute that passes. T1h Time Estimate 1 Hour
Projects
None yet
Development

No branches or pull requests

1 participant