1. 18
  1.  

  2. 3

    I am very curious to see more of Pijul both when it stabilizes and also when it becomes even easier to collaborate. Does anyone have any good comparisons specifically between Nest and GitHub/GitLab or equivalent? There’s so much potential here and I can’t wait to explore.

    1. 1

      Hi! I’m one of the authors of Pijul. Have you tried to install it? In any case, what’s specifically blocking you from contributing? We are definitely looking for contributors, a number of people are already doing great work, but it isn’t moving as fast as it could. I know the Nest is quite far, feature-wise, from older platforms like GitHub/GitLab, but we use it quite productively for Pijul itself (the CI hasn’t restarted after the fire, but will be restarted soon).

      1. 1

        Hi! I’m one of the authors of Pijul.

        Hi there, I am so pleased you responded to my comment! First, please accept my heartfelt thanks for your efforts and congratulations on your progress. Way to go!

        Next, kindly allow me to answer your queries in the detail I can.

        Have you tried to install it?

        I am on macOS predominantly for work and would love to be able to install it with Homebrew. I’m afraid that the last time I tried to install Pijul with cargo it didn’t work quite right, however this was rather far in the past. I shall try again with Rust 1.53 (which I believe to be the latest).

        In any case, what’s specifically blocking you from contributing?

        My company’s policies are rather restrictive when it comes to such things. I will see what I can do, however, perhaps to write some tutorials even as a start.

        I know the Nest is quite far, feature-wise, from older platforms like GitHub/GitLab, but we use it quite productively for Pijul itself (the CI hasn’t restarted after the fire, but will be restarted soon).

        These two things are really where the rubber meets the road, I’m afraid. The workflow like pull/merge requests and code review are really essential ingredients as soon as you get to n+1 engineers in my book. However, I’d be very interested in talking out some of the use cases! Ideally I’d love to be able to stand up my own Nest instance and get going that way. Obviously I don’t expect Pijul to evolve in quite the same directions as alternative projects like Fossil.

        CI is also a really important part for me, as well. I wonder if it’d be sufficient for me to have pre-* hooks to ensure quality before pushing to a remote. This is something I can think about some more.

        I hope that the above answers your questions and know that I am happy to engage in further dialog to the best of my abilities.

        Love, +Jonathan

        1. 1

          Thanks for all the kind words! To answer some of your comments:

          • There’s a basic review tool in the Nest, but (1) it has a bug where you can’t share your review with others, and (2) I feel it lacks a “todo list” showing you all the actions you need to take across all your projects.

          • If you have a channel (named for example “main”), you can push to pseudo-channel “main/ci” to automatically merge if your changes pass the test.

          We also have applications of the algorithms other than source code, so that could solve the chicken-and-egg problem where people want to use it “when everybody else does”.

          1. 1

            I appreciate your response. If there’s anything I can do to help out with testing the features I mentioned, let me know and I’ll gladly provide some feedback.

            In the meantime, keep up the awesome!