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

Monorepo structure and cleanup #383

Merged
merged 2,800 commits into from
Sep 3, 2024
Merged

Monorepo structure and cleanup #383

merged 2,800 commits into from
Sep 3, 2024

Conversation

LaurentRDC
Copy link
Member

@LaurentRDC LaurentRDC commented Aug 31, 2024

This is a pull request that reforms the distributed-process repository into a monorepo, containing most relevant packages in the haskell-distributed organization.

See #382 for discussion

List of merged packages:

  • distributed-process-async
  • distributed-process-client-server
  • distributed-process-execution
  • distributed-process-extras
  • distributed-process-simplelocalnet
  • distributed-process-supervisor
  • distributed-process-systest
  • distributed-static
  • network-transport
  • network-transport-inmemory
  • network-transport-tcp
  • network-transport-tests
  • rank1dynamic

This PR also includes some cleanup, including:

  • Harmonizing the dependency versions of all packages in the repo, such that all packages can be build using GHC 8.10 up to GHC 9.10
  • Dropping support for GHC before 8.10, and simplifying all the CPP cruft
  • Cleaning up all cabal files;
  • Added an explicit CONTRIBUTING.md file.
  • Continuous testing on Ubuntu

TODO after merge:

  • Update the links to this repo for all affected packages on Hackage
  • Archive the merged repositories

qnikst and others added 30 commits November 25, 2017 15:57
Fix link to lifted-base
Using the latest stackage lts
Fixed link for distributed-process-async
Add slack & use bootstrap rows over image-height formatting.
support building with GHC 8.2.1
rank1dynamic can't be built on GHC =< 7.8. This patch reflects that in dependency files.
@LaurentRDC LaurentRDC changed the title Monorepo structure Monorepo structure and cleanup Aug 31, 2024
@LaurentRDC LaurentRDC marked this pull request as ready for review September 2, 2024 18:47
@LaurentRDC LaurentRDC requested a review from davidsd September 2, 2024 18:47
@LaurentRDC
Copy link
Member Author

@davidsd This pull request is huge, so I can't expect anyone to actually review it.

Would you confirm to me that your workflow still works though? Can you build e.g. distributed-process?

I think you use Slack but I don't, so I'm not sure whether things still work.

Copy link
Contributor

@davidsd davidsd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After adding an extra-deps field for rematch in the stack.yaml files, I was able to build everything. It looks good to me!

@davidsd
Copy link
Contributor

davidsd commented Sep 2, 2024

I'm not sure what's going on with the one failing test.

@LaurentRDC
Copy link
Member Author

Some of the tests are quite flaky. There's an option to rerun failed runs on Github actions, which I had to use a lot

@davidsd
Copy link
Contributor

davidsd commented Sep 3, 2024

Regarding renaming this repo, I vote against. I think the name "distributed-process" makes sense, since it is the name of the "main" package here, and also the prefix of several other packages here. These are the names people will see on hackage when they search for this functionality -- they will likely not know what "cloud haskell" is unless they read some of the literature from around when cloud haskell was born.

@LaurentRDC
Copy link
Member Author

Makes sense, no name changes

@LaurentRDC LaurentRDC merged commit a8f1003 into master Sep 3, 2024
20 of 21 checks passed
@LaurentRDC
Copy link
Member Author

In the end, the website must be published from a special repo with the organization name for it to be published at haskell-distributed.github.io.

@joelmccracken
Copy link
Member

I see you're building a bikeshed and deciding on the color! May I just comment that I've noticed some confusion around the difference between "cloud haskell" and "distributed process", and I suspect that renaming back may somehow cause additional confusion?

@LaurentRDC
Copy link
Member Author

LaurentRDC commented Sep 3, 2024

@joelmccracken Do not worry, I will not rename this repository.

To address potential confusion about Cloud Haskell / distributed-process, I have created an organization README: https://github.com/haskell-distributed/.github/blob/main/profile/README.md

@joelmccracken
Copy link
Member

@joelmccracken Do not worry, I will not rename this repository.

To address potential confusion about Cloud Haskell / distributed-process, I have created an organization README: https://github.com/haskell-distributed/.github/blob/main/profile/README.md

Beautiful, thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.