diff --git a/bounties/001#-CMTAT-ligo.md b/bounties/001#-CMTAT-ligo.md new file mode 100644 index 0000000..fb6c655 --- /dev/null +++ b/bounties/001#-CMTAT-ligo.md @@ -0,0 +1,95 @@ +# LIGO - CMTAT-Ligo - #1 +## Current Status: Open for application +* Open for application (13/12/2023) +* Assigned +* In Review +* Closed + +## Bounty Details +* Total Bounty Amount (without bonus): 2500 xtz +* Time Left: Expires 15/03/2024 +* Project Type: Single Contributor +* Opened: 13/12/2023 +* Time Commitment: Weeks +* Type: Library creation + +## Description +### Goal : +Creation of a library using LIGOLang for Tezos. The library must implement the [CMTA Token](https://cmta.ch/standards/cmta-token-cmtat) developed by CMTA to tokenise securities in compliance with the Swiss law. + +After completion of the bounty, the library may be made available in the ligo [registry](https://packages.ligolang.org/packages). + +### Scopes : +- Creation of library + - Has to be compliant with [CMTAT guidelines](https://cmta.ch/standards/cmta-token-cmtat) + - Code constraint have to be available as [here for TZIP12](https://github.com/ligolang/contract-catalogue/blob/main/lib/fa2/common/tzip12.interfaces.jsligo) + - Implemented function can be called as [here for NFT](https://github.com/ligolang/contract-catalogue/blob/main/lib/fa2/nft/nft.impl.jsligo) + - Has to be tested with LIGO tests. +- Creation of the documentation related to the library. + +## Bounty Bonus +- Clean open-source project using your library is available (+600xtz) +- Blog post on how to use your library is published. (+400xtx) + +## Acceptance Criteria +- Interface code has to be documented +- Current LIGO version has to be used +- Resources are in english +- Readme is available and explains how to use the library (will be posted into registry) +- User experience to use the library has been validated by the LIGO team +- Security audit has been done and accepted by the LIGO team +- If bonus have been done, they have been validated by the LIGO team + +## To apply for this bounty you should: +- Understand Tezos and at least one syntax of LIGO +- Understand the [CMTA Standard](https://cmta.ch/standards/standard-for-the-tokenization-of-shares-of-swiss-corporations-using-the-distributed-ledger-technology) +- Understand the [CMTAT Token](https://cmta.ch/standards/cmta-token-cmtat) + +## Selection Process +LIGO core team will examine your profile. If you are selected we will contact you. The bounty will ideally attributed to 1 person. If bonus are not done, other bounties may be created to handle them. +LIGO core team or Tezos core team are not available to participate to the bounty. + +## To help you on bounty completion +- You will have a special channel on slack where you can contact members of the LIGO core team. They will try to answer to your questions quickly +- You can use the already existing [FA library](https://packages.ligolang.org/package/@ligo/fa) +- You can follow the structure of [FA library](https://github.com/ligolang/contract-catalogue) +- An [example implementation exist in Smartpy](https://github.com/CMTA/CMTAT-Tezos-FA2) +- An [example implementation exist in Solidity](https://github.com/CMTA/CMTAT) + +## Development process +- Keep your ongoing code in a public repository (a fork of the [CMTAT-Ligo](https://github.com/ligolang/CMTAT-Ligo) repository). +- Provide weekly updates through Discord or slack channel. +- Code commits count as updates if you link to your branch/fork from the bounty thread. We just need to be able to see that you are making progress. +- The code is merged in [CMTAT-Ligo](https://github.com/ligolang/CMTAT-Ligo) repository. + +## Legal conditions +### Payment condition + +- Your identity must be verified. +- The balance will be paid out upon completion. + +### Copyright and Licensing: +- Copyright: All work produced within the scope of this bounty is subject to copyright laws. Any creations, code, documentation, or other works produced initially belong to Ligolang (Accélérateur de Blockchain). We reserve the right to modify, distribute, and use these works freely as per our requirements. +- MIT License: By submitting your work for this bounty, you agree to apply the MIT License to the deliverables. All submitted work must be licensed under the MIT License to allow free use, distribution, and modification without restrictions, while acknowledging the copyright. + +### Rights of Use: +- By submitting your work, you grant Ligolang (Accélérateur de Blockchain) a non-exclusive, worldwide, royalty-free, and irrevocable license to use, reproduce, modify, distribute, and publicly display the delivered works for internal or public purposes. + +- Your identity have to be verified. +- The balance will be paid out at completion. + +## Bounty Abandonment and Re-awarding +If work on the bounty is paused for an extended period, or if the quality of work deteriorates to a level where it's deemed appropriate for someone else to take over, we might consider reassigning the bounty. We will maintain transparency throughout this process and make efforts to collaborate with you to overcome challenges and successfully finish the project. However, there might be situations where it becomes essential to either proceed in a different direction or enhance your efforts with additional resources, leading to a divided bounty. + +## Funding +The bounty is funded by the LIGO team. + +# Bounty Process +## Open for application +Developers can submit applications through Discord / Slack. +## Assigned +A defined number of developers are assigned to the bounty. +## In Review +The LIGO core team is reviewing the submission. +## Awarded +The award has been given and the bounty is closed. diff --git a/bounties/001-ligo-site-documentation.md b/bounties/001-ligo-site-documentation.md deleted file mode 100644 index d188c37..0000000 --- a/bounties/001-ligo-site-documentation.md +++ /dev/null @@ -1,127 +0,0 @@ -Bounty - - -# Ligo site documentation - #1 -## Current Status: Open for application -Ratification (29/08/2023) -Open for application (xx/xx/2023) -Assigned -In Review -Closed - -## Bounty Details -Total Bounty Amount (without bonus): N xtz -Time Left: Expires 15/10/2023 -Project Type: Single Contributor -Opened: xx/xx/2023 -Time Commitment: Days -Experience Type: Beginner -Type: Documentation - -## Description -### Context : -Following analytics, a lot of ligo new comers are afraid by documentation and stop after few minutes. That's a brake on ligo adoption and impact Tezos adoption. - -### Goal : -Rework Ligo documentation to be understandable and attractive for new developers. Concerned doc is https://ligolang.org/docs. Source are available here : https://gitlab.com/ligolang/ligo/-/tree/dev/gitlab-pages/docs?ref_type=heads -Have a better experience for current developers. - -### Scopes : -Introduction -> Should be handled by ligo team -Objectives: What is ligo and why is it -Rewards : N token -Get started -Objectives: Be able to write a first contract and deploy it in less than 15 minutes. With notions : -Of an entry -Of a view -Of a storage -Rewards: N token -Basics (not sure it's necessary) -Objectives: Add missing stuff on basics -Rewards: N token -First contract -Objectives: Be able to write a first contract. In less than one hour minutes with notions (the current taco shop can be rewritten) : -Big_map in storage -Interact with another contract -Receive and emit xtz -Sender, receiver, balance, amount, assert -Gas fees -Rewards: N token -Tests -Objectives: Be able to write a first contract with storage, entry and view. Show how to call it, Show how to deploy it. In less than 15 minutes. -Rewards: N token -Structure your code -Objectives: Explain how to structure contract code : -Modules -Import vs Include -Export (JSligo) -Package management (ligo registry) -Rewards: N tokens -Design a library -Objectives: Explain how to design a library : -How to implement and use interfaces -Explain how to publish it on ligo registry -Rewards: N tokens -Good practices -Objectives : -How to manage storage efficiently -Smart contract security -Optimise entry -Optimize size of contract -Rewards: N tokens -Anti pattern -Objectives list of anti pattern to avoid and explain why -Rewards: N tokens -Cheat sheet -Objectives: Rework the ligo cheat sheet -Rewards : N tokens - -## Acceptance Criteria -At least one language is managed using component -Written explanation are clear and concise -Code blocks are qualitative. -The code blocks are tested with ligo-mdx -Manage docusaurus sidebar to organize your pages. (Easy to learn, we can onboard if necessary) -## To apply for this bounty you should: -Understand Tezos and at least one syntax of Ligo -Good skills of redaction, make info clear and concise. -Already have written some ligo. -Contact Ligo team through Ligo-bounties channel in Tezos discord server. -At least one repository with smart contract written in ligo -The address of the contract deployed on mainnet or testnet -List of scope than you want to handle -##Selection Process -Ligo core team will examine your profil. If you are selected we will contact you. The bounty will ideally attributed to 1 person, if you want to handle some scopes only, inform it at submission, we will contact others selected users to complete the bounty scopes. -## To help you on bounty completion -You will have a special channel on slack where you can contact Ligo core team. They engage to answer to your questions as soon as possible. -## Bounty Completion -Keep your ongoing code in a public repository(a fork of Ligo repository). -Please provide regular (at least weekly) updates. -Code commits count as updates if you link to your branch/fork from the bounty thread. We just need to be able to see that you are making progress. -The balance will be paid out at completion. Each scopes can be merged and rewarded alone. -The Ligo team is the rightful owner of the accomplished work. -Once you have finished, please alert us through Discord Ligo-bounties channel and open a pull request. We will review and award the bounty reward if the terms have been met. If there is any modifications to do we will inform you of what is needed before we can award the reward. - -## Bounty Bonus -If you manage both languages a small bonus can be offered. (Depending on the amount of code lines) -If you find useful scope to add, ask to Ligo core team, if we accept we will offer an amount of token for it. -## Bounty Abandonment and Re-awarding -If work on the bounty is paused for an extended period (as determined by the Developer Advisory Board), or if the quality of work deteriorates to a level where it's deemed appropriate for someone else to take over, we might consider reassigning the bounty. We will maintain transparency throughout this process and make efforts to collaborate with you to overcome challenges and successfully finish the project. However, there might be situations where it becomes essential to either proceed in a different direction or enhance your efforts with additional resources, leading to a divided bounty. -## Funding -The bounty is funded by Ligo team. - -# Bounty Process -## Definition of the requirements -Ligo core team find a consensus on definition of the bounty and redact this content. -## Ratification -Ligo owner accept the bounty and purpose an amount for it -## Open for application -Developers can submit applications through bitcoin / discord channel -## Assigned -A defined number of developers are assigned to the bounty. -## In Review -The Ligo core team is reviewing the submission -## Awarded -The award has been given and the bounty is closed. - - diff --git a/bounties/002-example.md b/bounties/002-example.md deleted file mode 100644 index ac3d24e..0000000 --- a/bounties/002-example.md +++ /dev/null @@ -1,3 +0,0 @@ -# Ligo example bounty #2 - -blah blah blah