1. 11 Jan, 2021 1 commit
    • Ilona Prikule's avatar
      [#429] Remove alphanet.sh mentions · 4957ce31
      Ilona Prikule authored
      Problem: there are still mentions of alphanet.sh in the code base.
      Solution: change them all to tezos-client. Add a link to
      tezos-packaging to README to point to where one can get the executable.
  2. 25 Dec, 2020 1 commit
  3. 22 Dec, 2020 2 commits
  4. 27 Nov, 2020 1 commit
    • Ivan Gromakovskii's avatar
      Remove remaining usages of indigo · b8e90757
      Ivan Gromakovskii authored
      Problem: indigo code is not in this repo anymore, but there are still
      some places where it's assumed to be here.
      Solution: remove remaining mentions and usages, except for those which
      still make sense.
  5. 17 Nov, 2020 1 commit
  6. 30 Sep, 2020 1 commit
    • Ivan Gromakovskii's avatar
      [#317] Update READMEs · 98329eea
      Ivan Gromakovskii authored
      Problem: the README of the morley package got a bit outdated. While
      the information there is mostly correct, the way it's written looks
      outdated. And it doesn't describe some commands/features that were
      added after this README was written.
      Solution: rewrite it in a way that looks better to me. Reviewers will
      evaluate whether it looks better now.
      I believe now it's clearer what the Morley packages consists of.
      The order is the following: executable, library, extensions.
      Extensions are rarely used nowadays, so they are the last.
      The library users can get documentation on Hackage and are more likely
      to scroll this README.
      Executable users are probably the main audience, hence I started with
      it. The root README was slightly updated as well.
  7. 10 Aug, 2020 1 commit
  8. 26 Jun, 2020 2 commits
  9. 15 May, 2020 1 commit
    • Kirill Elagin's avatar
      Add licensing information · 1776886c
      Kirill Elagin authored
      * Add licenses for everything
      * Almost everything is copyrighted by TQ and the license is MIT,
      * apart from some dot-files in the root (Unlicensed by Serokell)
      * and example contracts comming from Tezos.
  10. 09 Mar, 2020 1 commit
    • Roman Melnikov's avatar
      [TM-395] Add instructions · 5da3495d
      Roman Melnikov authored
      Problem: Patched node building was added to the CI, now we need to
      explain how to run local chain.
      Solution: Add README and sample `parameters.json` file.
  11. 19 Feb, 2020 2 commits
    • Ivan Gromakovskii's avatar
      [TM-309] Rename `morley-lorentz` to `lorentz` · 2b6b7ec6
      Ivan Gromakovskii authored
      Problem: we had a poll across developers and decided to rename
      `morley-lorentz` to simply `lorentz`.
      It does not have good argument, just some bikeshedding.
      Solution: rename everywhere.
    • Ivan Gromakovskii's avatar
      [TM-309] Move `morley` package into `code/morley` · 82cbcaf9
      Ivan Gromakovskii authored
      Problem: we have moved all packages except for `morley` into `code/`.
      `morley` is currently placed in the root which differs from everything
      else. Root `README` is mostly about `morley` package, but we also need
      `README` about the whole repo.
      Solution: move everything that constitutes the `morley` package to
      Update default MR template because we don't have root changelog
      anymore, but we have multiple changelogs and multiple `README` files.
      I removed `CONTRIBUTING.md` from `morley`'s `package.yaml` because
      it seems not very useful there.
      Also since relative path to `contracts/` has changed I have created
      a new variable to hold it (in tests).
      The root Makefile now contains commands that are applied to the whole
      repo, I have moved `link` and `stylish` definitions to it because
      they are used only there. Also fixed `stylish-haskell` usage.
  12. 16 Feb, 2020 1 commit
    • Ivan Gromakovskii's avatar
      [TM-309] Move Lorentz code into a new package · 55db7077
      Ivan Gromakovskii authored
      Over time some `morley` package became bigger and it seems that now
      is a good time to draw some boundaries between its parts.
      The main reason is that if a package contains X and Y while someone
      needs only X, they will be forced to depend on Y as well.
      Also it makes dependencies inside this repo more explicit and clear.
      Solution: create `morley-lorentz` package and move Lorentz code
      I had to move some utility testing code used by Lorentz tests to
      `morley` lib or to `morley-lorentz` (if it is used only
      by `morley-lorentz`).
      Also I moved `tOriginate`, `tTransfer` and `tExpectStorageConst` to
      `Michelson.Test.Integrational` because they do not use anything
      from Lorentz.
      Some difficulties arose because some tests in `morley` use Lorentz.
      They were solved as follows:
      1. `Test.Integrational` was rewritten using Michelson.Typed instead of
      2. `Doc.hs` and `DocTest.hs` tests were moved to `morley-lorentz`
      because they are heavily based on Lorentz. Also `Lorentz.*` tests were
      moved there.
      3. `Test.Interpreter` was split into two `Test.Interpreter` modules
      (in different test-suites). In the next commit we will clean it up.
      Another notable change is movement of Arbitrary instances for UStore
      types into UStore.Types module. As a bonus it removed 2 orphan
  13. 14 Feb, 2020 1 commit
    • Anton Myasnikov's avatar
      [#45] Update links and fix 'entrypoints' spelling. · 1c12c9d2
      Anton Myasnikov authored
      Problem: Currently some links in documentation are dead need to
      be replaced with stable ones, also somewhere in doc there're
      occurances of misspelling 'entry points' that should be changed
      as well.
      Solution: Stabilize links and replace all the occurances of
      'entry points' to 'entrypoints'.
  14. 08 Jan, 2020 1 commit
    • Roman Melnikov's avatar
      [#14] Update README · b692fead
      Roman Melnikov authored
      Problem: README states that there are two ways to get `morley`
      executable whereas later three ways are described.
      Solution: `s/two/three/`.
  15. 18 Dec, 2019 1 commit
    • Roman Melnikov's avatar
      [#14] Update README.md · 1018ae35
      Roman Melnikov authored
      Problem: Now it is possible to build morley using cabal.
      Solution: Mention cabal in the README.md.
  16. 30 Nov, 2019 1 commit
    • Ivan Gromakovskii's avatar
      [TM-309] Move Abstract and Managed ledgers into a new package · a2f8c242
      Ivan Gromakovskii authored
      Problem: some contracts contain functionality present in our
      AbstractLedger and ManagedLedger contracts. If we want to reuse
      that functionality we have to depend on whole `lorentz-contracts`
      package which contains some stuff besides these ledgers. So current
      structure of packages adds unnecessary dependencies to contracts
      that reuse ledger code.
      1. Create `morley-ledgers` package. I decided to avoid naming
      Lorentz there because one day it may be implemented with Indigo.
      Probably it will always be based on `morley`, hence it is in the name.
      It contains ManagedLedger and AbstractLedger.
      2. Move `contractConsumer` into `Lorentz.Test`. It is pretty small and
      is generally useful for testing.
      3. Also rename `lorentz-contracts-test` to `morley-ledgers-test`
      because it contains tests only for `morley-ledgers`.
      Note that I mostly preserve module names even if they refer to
      Lorentz. Currently contracts are still implemented using Lorentz and
      we don't want to make unnecessary breaking changes.
      Also note that I didn't bother changing anything in pkgs.nix and
      didn't test `nix` side of things because primary user of it is George
      and according to him he will nixify the repo differently.
  17. 20 Nov, 2019 1 commit
    • Ivan Gromakovskii's avatar
      [TM-353] Update issue tracker information · ffa9dc3a
      Ivan Gromakovskii authored
      Problem: we used to use YouTrack as primary issue tracker. Now we
      don't, but README and contribution guidelines still say we do.
      Solution: explain what happened in README, update issue creation link
      in contribution guidelines.
  18. 12 Nov, 2019 1 commit
    • Ivan Gromakovskii's avatar
      Add a sad note about issue tracker · 258b48fd
      Ivan Gromakovskii authored
      Problem: we say that one can login to our YT using GitHub account,
      but it does not work anymore.
      Solution: say that the issue tracker stopped being public and we'll
      fix it one day.
  19. 09 Aug, 2019 1 commit
    • Ivan Gromakovskii's avatar
      [TM-279] Update branching policy · b629cb9a
      Ivan Gromakovskii authored
      Problem: we decided to have a special branch for new version of
      Michelsonm, but it's not mentioned in our branching policy.
      Solution: describe this policy and refer to it from README to make
      it easier to figure out which version(s) we support.
  20. 20 Jun, 2019 1 commit
    • Ivan Gromakovskii's avatar
      Remove ZuriHac notice · a7d7f2f9
      Ivan Gromakovskii authored
      Problem: there was a temporary notice about ZuriHac which was supposed
      to be deleted when ZuriHac is over. It's over.
      Solution: just do it.
  21. 14 Jun, 2019 1 commit
  22. 12 Jun, 2019 1 commit
  23. 23 May, 2019 1 commit
    • Konstantin Ivanov's avatar
      [TM-169] Add `output` option to `morley print` · c3102ec3
      Konstantin Ivanov authored
      Problem: sometimes it is not convenient to print output to stdout
      and further redirect it because, when called from within a script,
      it can be mixed with output of other commands.
      Solution: allow specifying `--output` option to `print` command.a
  24. 20 May, 2019 2 commits
    • Konstantin Ivanov's avatar
      [TM-178] Add lorentz contracts registry · b42507b6
      Konstantin Ivanov authored
      Problem: we need to keep a registry of written Lorentz contracts
      which could be printed when necessary.
      Solution: add an executable which can dump contracts.
      A simple automatic contracts lookup is implemented which traverses
      haskell modules and finds all contracts of `contract_<name>` format,
      and fills a module of all found declarations like e.g. tasty-discovery
      does it.
    • Konstantin Ivanov's avatar
      [TM-136] Add `lorentz-contracts` package · 33b1bee5
      Konstantin Ivanov authored
      Where all Lorentz contracts and tests to them are moved to.
  25. 14 May, 2019 1 commit
    • Konstantin Ivanov's avatar
      [TM-131] Turn Haskell module refs to links · adacf7bb
      Konstantin Ivanov authored
      Problem: in documentation we mention Haskell modules, but if they
      get renamed it's easy to leave documentation outdated.
      Solution: wrap those into markdown links to actual modules.
      Markdown links are verified, which makes it more difficult to forget
      to update documentation.
  26. 30 Apr, 2019 1 commit
    • Roman Melnikov's avatar
      [TM-137] Remove `Michelson.Types` · ac2fe853
      Roman Melnikov authored
      Problem: `Michelson.Types` doesn't make much sense, its name is too
      broad, however, it contains only small subset of types, which are
      presented in Michelson.
      Solution: Split `Michelson.Types` into two parts: first (with macros and
      parsed types) moved to `Michelson.Macro` (unfortunately, we can't
      place `LetMacro` and `ParsedOp` in different modules, because they
      depend on each other), second (with LetValue and LetType) moved to new
      module called `Michelson.Let`
  27. 26 Apr, 2019 1 commit
  28. 23 Apr, 2019 1 commit
  29. 18 Apr, 2019 1 commit
  30. 15 Apr, 2019 1 commit
    • Ivan Gromakovskii's avatar
      [TM-128] Update links to `morley` · 87696268
      Ivan Gromakovskii authored
      Problem: `tezos-standards` has been renamed to `morley-framework`.
      Now all links to `morley` are obsolete (they still work, but they are
      not accurate and may get broken at some point).
      Solution: update all links.
  31. 04 Apr, 2019 1 commit
    • Ivan Gromakovskii's avatar
      [TM-105] Update links due to repo movement · 2f0f94fd
      Ivan Gromakovskii authored
      Problem: some links and other things got outdated because the
      repository has been moved to another GitLab group.
      Solution: update everything outdated that could be found by
      `git grep -i camlcase`.
  32. 03 Apr, 2019 1 commit
  33. 02 Apr, 2019 4 commits