{"__v":0,"_id":"576eba5b9c84a31900958ab7","initVersion":{"_id":"57595fb5a2d9990e00a86d77","version":"1.0"},"project":"57595fb5a2d9990e00a86d74","user":{"_id":"57595ebe18760817001e8bc9","username":"","name":"Virgil"},"hidden":false,"createdAt":"2016-06-25T17:07:39.981Z","fullscreen":false,"htmlmode":false,"html":"","body":"## I want to hop on a phone-call to chat!\nWe get about 2-3 requests like this per day.  And if we agreed to them, we would cease to be getting work done.  So, *no cold-calls*, ever.\n- If you have a specific proposal, email us at [collective@legalese.com].(mailto:collective@legalese.com).  If you do not have specifics, you are likely to get a response.\n- If you don't have a specific proposal, chat it up the community mailing list, [talk@lists.legalese.com](https://groups.google.com/a/lists.legalese.com/forum/#!forum/talk) or our Twitter [@legalese](https://twitter.com/legalese).\n\n## I propose a strategic partnership\nIf you or your firm wish a relationship that goes beyond an exchange of logos, please email [collective@legalese.com](mailto:collective@legalese.com) with a proposal that describes deliverables for both parties with specific dates. If your proposal does not contain these specifics, you are unlikely to get a response.\n\n## Tech Support needed!\nIf our app isn't working, use the [support forum](https://legalese.readme.io/discuss).\n\n## I like what you're doing, keep me posted on your progress\n* Bi-monthly announcements go out to the [wellwishers mailing list](https://groups.google.com/a/lists.legalese.com/d/forum/wellwishers).\n* We occasionally publish longer works on our [medium page](https://medium.com/@legalese).\n* You can also find us on the Twitter [@legalese](https://twitter.com/legalese).\n\n## I have advice/questions/news that is not confidential\nPlease join our [community mailing list, talk@lists.legalese.com](https://groups.google.com/a/lists.legalese.com/forum/#!forum/talk), and post to it directly so your message can reach the widest useful audience.\n\n## I have advice/questions/news that is confidential\nWe appreciate your forwardness, but if it's confidential, and we're not under NDA, then you probably shouldn't be sharing it with us.\n\n## I have advice/questions/news that is not confidential, but I don't want to post publicly!\nUnfortunately, we lack the resources to engage over private channels, with two exceptions: media inquiries and strategic partnerships.\n\n\n- ## I'm from the media\n    Logos and other print/web-ready assets are available at our [media kit](media-kit). Email us at [collective@legalese.com](mailto:collective@legalese.com) with questions, angle, and deadline. We are happy to be quoted about smart-contract (in)security, the potential and the risks of smart contracts both on-blockchain and off-, and how LegalTech is disrupting the legal industry generally.\n\n- ## I want to sell you something\nWe welcome marketing emails, whether targeted or not. But if you'd like us to respond, please email us at [collective@legalese.com](mailto:collective@legalese.com), tell us about Liz Lemon and Tom Jones, and incorporate the line \"there's always money in the banana stand\" in your introductory email.  \n\n\n## I want to invest\nIf you are an individual, please email [collective@legalese.com](mailto:collective@legalese.com) indicating whether you meet the criteria for an accredited investor in Singapore and proposed investment range. If you represent a venture fund, please email us, indicating your usual criteria for seed-stage investments. We will respond with a deck when we are not too early for you!\n\n# I want to join the team\nAre you sure? It is unglamorous work, like spam-moderation, reimbursement reviews, and compensation negotiations, and it requires several months' worth of unpaid volunteering and reading before you can become a full member of the opensource project, much less the possibility of pay. You can start at [How Legalese Works](https://github.com/legalese/legalese.github.io/blob/master/doc/company.org).\n\nIf you really want to get involved and can spend at least 10 hours a week, we seek volunteer contributors in the following areas:\n\n* **Design and Implementation of Domain Specific Languages**\n    Design a DSL suitable for drafting legal agreements and regulations. The users of the DSL—its \"programmers\"—may be lawyers or end-users.\n* **Source-to-source translation**\n    Write a compiler that reads the DSL and outputs to Haskell, Racket, or Elixir.\n* **Library Creation**\n    Develop a Creative Commons BY-SA-NC body of standard agreements and clauses in the DSL, adaptable for multiple jurisdictions.\n* **Formal Methods**\nModel checking, verification—is the contract complete? Are there internal inconsistencies?\n* **Data Visualization**\n    Show how the programs behave under different scenarios. What are the outcomes for different parties? What actions are required from parties in the future?\n* **Natural Language Generation**\n    Enhance the compiler to target English and at least one other natural language. Introduce an aggressive optimizer that matches patterns and substitutes terser alternatives without loss of semantics. The goal is to produce an isomorphism with the original legal text.\n* **Natural Language Processing**\n    Run the compiler in reverse. Read existing regulations and legal agreements. Write the isomorphic representation in the DSL.\n* **Fintech/Blockchain**\n    Adapt the compiler to output to Ethereum language source or bytecode.\n\n## Where do I sign up?\n1. Our community kibitzes on the [talk@lists.legalese.com](https://groups.google.com/a/lists.legalese.com/forum/#!forum/talk) mailing list. Start here.\n\n\n2. **Getting your feet wet.**  Our project management runs on [Github Issues](https://github.com/legalese/legalese.github.io/issues). Pick off some low-hanging fruit from the [Open Issues](https://github.com/legalese/legalese.github.io/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20). Ask any questions on the ticket. For a more pleasant interface, you can also use [waffle.io](https://waffle.io/legalese/legalese-io.github.io).\n\n3. **Jumping into the deep-end.**  You brave intrepid explorer. Email [collective@legalese.com](mailto:collective@legalese.com) for an invitation to join the Legalese Slack!  If you'll need access to the Legalese Google Drive repository, mention this in the Slack.\n\n\n[block:image]\n{\n  \"images\": [\n    {\n      \"image\": [\n        \"https://files.readme.io/8343915-PwlnhOj3QAuiuLVCUWhH_ss_2016-06-26_at_01.29.57-1.jpg\",\n        \"PwlnhOj3QAuiuLVCUWhH_ss 2016-06-26 at 01.29.57-1.jpg\",\n        1972,\n        1170,\n        \"#282e36\"\n      ],\n      \"caption\": \"Hard at work.\"\n    }\n  ]\n}\n[/block]","slug":"contact","title":"Contact"}

Contact


## I want to hop on a phone-call to chat! We get about 2-3 requests like this per day. And if we agreed to them, we would cease to be getting work done. So, *no cold-calls*, ever. - If you have a specific proposal, email us at [collective@legalese.com].(mailto:collective@legalese.com). If you do not have specifics, you are likely to get a response. - If you don't have a specific proposal, chat it up the community mailing list, [talk@lists.legalese.com](https://groups.google.com/a/lists.legalese.com/forum/#!forum/talk) or our Twitter [@legalese](https://twitter.com/legalese). ## I propose a strategic partnership If you or your firm wish a relationship that goes beyond an exchange of logos, please email [collective@legalese.com](mailto:collective@legalese.com) with a proposal that describes deliverables for both parties with specific dates. If your proposal does not contain these specifics, you are unlikely to get a response. ## Tech Support needed! If our app isn't working, use the [support forum](https://legalese.readme.io/discuss). ## I like what you're doing, keep me posted on your progress * Bi-monthly announcements go out to the [wellwishers mailing list](https://groups.google.com/a/lists.legalese.com/d/forum/wellwishers). * We occasionally publish longer works on our [medium page](https://medium.com/@legalese). * You can also find us on the Twitter [@legalese](https://twitter.com/legalese). ## I have advice/questions/news that is not confidential Please join our [community mailing list, talk@lists.legalese.com](https://groups.google.com/a/lists.legalese.com/forum/#!forum/talk), and post to it directly so your message can reach the widest useful audience. ## I have advice/questions/news that is confidential We appreciate your forwardness, but if it's confidential, and we're not under NDA, then you probably shouldn't be sharing it with us. ## I have advice/questions/news that is not confidential, but I don't want to post publicly! Unfortunately, we lack the resources to engage over private channels, with two exceptions: media inquiries and strategic partnerships. - ## I'm from the media Logos and other print/web-ready assets are available at our [media kit](media-kit). Email us at [collective@legalese.com](mailto:collective@legalese.com) with questions, angle, and deadline. We are happy to be quoted about smart-contract (in)security, the potential and the risks of smart contracts both on-blockchain and off-, and how LegalTech is disrupting the legal industry generally. - ## I want to sell you something We welcome marketing emails, whether targeted or not. But if you'd like us to respond, please email us at [collective@legalese.com](mailto:collective@legalese.com), tell us about Liz Lemon and Tom Jones, and incorporate the line "there's always money in the banana stand" in your introductory email. ## I want to invest If you are an individual, please email [collective@legalese.com](mailto:collective@legalese.com) indicating whether you meet the criteria for an accredited investor in Singapore and proposed investment range. If you represent a venture fund, please email us, indicating your usual criteria for seed-stage investments. We will respond with a deck when we are not too early for you! # I want to join the team Are you sure? It is unglamorous work, like spam-moderation, reimbursement reviews, and compensation negotiations, and it requires several months' worth of unpaid volunteering and reading before you can become a full member of the opensource project, much less the possibility of pay. You can start at [How Legalese Works](https://github.com/legalese/legalese.github.io/blob/master/doc/company.org). If you really want to get involved and can spend at least 10 hours a week, we seek volunteer contributors in the following areas: * **Design and Implementation of Domain Specific Languages** Design a DSL suitable for drafting legal agreements and regulations. The users of the DSL—its "programmers"—may be lawyers or end-users. * **Source-to-source translation** Write a compiler that reads the DSL and outputs to Haskell, Racket, or Elixir. * **Library Creation** Develop a Creative Commons BY-SA-NC body of standard agreements and clauses in the DSL, adaptable for multiple jurisdictions. * **Formal Methods** Model checking, verification—is the contract complete? Are there internal inconsistencies? * **Data Visualization** Show how the programs behave under different scenarios. What are the outcomes for different parties? What actions are required from parties in the future? * **Natural Language Generation** Enhance the compiler to target English and at least one other natural language. Introduce an aggressive optimizer that matches patterns and substitutes terser alternatives without loss of semantics. The goal is to produce an isomorphism with the original legal text. * **Natural Language Processing** Run the compiler in reverse. Read existing regulations and legal agreements. Write the isomorphic representation in the DSL. * **Fintech/Blockchain** Adapt the compiler to output to Ethereum language source or bytecode. ## Where do I sign up? 1. Our community kibitzes on the [talk@lists.legalese.com](https://groups.google.com/a/lists.legalese.com/forum/#!forum/talk) mailing list. Start here. 2. **Getting your feet wet.** Our project management runs on [Github Issues](https://github.com/legalese/legalese.github.io/issues). Pick off some low-hanging fruit from the [Open Issues](https://github.com/legalese/legalese.github.io/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20). Ask any questions on the ticket. For a more pleasant interface, you can also use [waffle.io](https://waffle.io/legalese/legalese-io.github.io). 3. **Jumping into the deep-end.** You brave intrepid explorer. Email [collective@legalese.com](mailto:collective@legalese.com) for an invitation to join the Legalese Slack! If you'll need access to the Legalese Google Drive repository, mention this in the Slack. [block:image] { "images": [ { "image": [ "https://files.readme.io/8343915-PwlnhOj3QAuiuLVCUWhH_ss_2016-06-26_at_01.29.57-1.jpg", "PwlnhOj3QAuiuLVCUWhH_ss 2016-06-26 at 01.29.57-1.jpg", 1972, 1170, "#282e36" ], "caption": "Hard at work." } ] } [/block]