Skip to content

Activity Maintaining #463

Open
Open

Description

@t-kruth

Hello!,

I created a discussion a few weeks back #460

I was curious of the status of this project, and if maintainers/community is active. it's very appealing but the lack of recent activity is a little alarming

Activity

  1. knidarkness commented on Sep 5, 2024

    @knidarkness

    Also am curious as to current status of the project.

  2. chbomtempo commented on Sep 24, 2024

    @chbomtempo

    Is there a way to contact hyperjumptech ? They claim to be a company, but I do not found a single way to contact them other than maybe job@hyperjump.tech... Has anyone tried to contact an employee? https://www.linkedin.com/company/hyperjump/people/
    Maybe @newm4n ?

  3. t-kruth commented on Sep 27, 2024

    @t-kruth
    Author

    Is there a way to contact hyperjumptech ? They claim to be a company, but I do not found a single way to contact them other than maybe job@hyperjump.tech... Has anyone tried to contact an employee? https://www.linkedin.com/company/hyperjump/people/ Maybe @newm4n ?

    @chbomtempo I this was my attempt at reaching out. I haven't tried any other avenues. If you do, please let us know here!

  4. stampthecoder commented on Dec 9, 2024

    @stampthecoder

    We may have to fork.... Is there enough maintainers willing to maintain a new version of go rules?

  5. 5idu commented on Dec 10, 2024

    @5idu

    We may have to fork.... Is there enough maintainers willing to maintain a new version of go rules?我们可能要分叉....是否有足够的维护者愿意维护一个新版本的围棋规则?

    good idea!

  6. 5idu commented on Dec 25, 2024

    @5idu

    I have forked this repository and currently have some new features.

    Contributions welcome!

  7. jonaswouters commented on Jan 6, 2025

    @jonaswouters

    I think it would be better to make a new open organisation to put the fork under, and have some participants of this ticket be the maintainers? We currently have our private fork.

  8. stampthecoder commented on Jan 11, 2025

    @stampthecoder

    @jonaswouters @5idu I agree! Can we start one. I would like to be a contributor. I can start one if needed.

  9. jonaswouters commented on Jan 13, 2025

    @jonaswouters

    @jonaswouters @5idu I agree! Can we start one. I would like to be a contributor. I can start one if needed.

    go ahead 👍

  10. mts57017 commented on Jan 13, 2025

    @mts57017
  11. ralphg6 commented on Jan 13, 2025

    @ralphg6
    Contributor

    Add me too..

  12. Jonfor commented on Jan 22, 2025

    @Jonfor

    Hey guys, I'm also a user of Grule that is looking into forking this. I can only do light contributions like updating the go version and dependencies. Is there a new organization fork yet? I only see @5idu 's fork with a few commits.

  13. jonaswouters commented on Jan 22, 2025

    @jonaswouters

    I was about to mail @stampthecoder about it, who said he was willing to set it up.
    We just have to align that somebody does it, and not end up with 3 different ones :)

    EDIT: Mail sent.

  14. stampthecoder commented on Feb 11, 2025

    @stampthecoder

    @jonaswouters @Jonfor @ralphg6 @chbomtempo Sent out invites to new org!

  15. vijaykramesh commented on Feb 11, 2025

    @vijaykramesh
    Contributor

    @stampthecoder could I get an invite as well? we actively use grule-rule-engine in production, are considering deprecating it due to lack of development/maintenance but I'd much rather join in with an active fork!

  16. stampthecoder commented on Feb 11, 2025

    @stampthecoder
  17. jonaswouters commented on Feb 24, 2025

    @jonaswouters

    Is there a way to contact hyperjumptech ? They claim to be a company, but I do not found a single way to contact them other than maybe job@hyperjump.tech... Has anyone tried to contact an employee? https://www.linkedin.com/company/hyperjump/people/ Maybe @newm4n ?

    I tried reaching out a while ago, never got a response.

    Now we need some momentum for the fork, and a better way to communicate (I propose discord)?

  18. ralphg6 commented on Mar 9, 2025

    @ralphg6
    Contributor

    @stampthecoder, could we enable the Issues in the new repo?

    Because it can be a place to open the new discussions...

    Only for knowledge, our new repo is https://github.com/DataWiseHQ/grule-rule-engine

  19. stampthecoder commented on Mar 9, 2025

    @stampthecoder
  20. ralphg6 commented on Mar 9, 2025

    @ralphg6
    Contributor

    @jonaswouters @Jonfor @stampthecoder @chbomtempo @vijaykramesh

    What do you think about copying all current PRs to the new repo?

    We could evaluate which one we would merge with!

    I could try to use the GitHub API to do it.

  21. ralphg6 commented on Mar 9, 2025

    @ralphg6
    Contributor

    Maybe... A good idea is to copy the issues too..

  22. stampthecoder commented on Mar 9, 2025

    @stampthecoder
  23. ralphg6 commented on Mar 9, 2025

    @ralphg6
    Contributor

    Yes... A pipeline to copy the issues and another one to copy the PRs is a good idea..

    I will create it on the new repo...

    Soon, I will create a PR with it.

  24. ralphg6 commented on Mar 9, 2025

    @ralphg6
    Contributor

    Absolutely! I’ll do that today
    …

    @stampthecoder

    Image

    Please, enable the Issues and Discussions on:

    https://github.com/DataWiseHQ/grule-rule-engine/settings

  25. stampthecoder commented on Mar 10, 2025

    @stampthecoder
  26. t-kruth commented on Mar 10, 2025

    @t-kruth
    Author

    I'll def try to do some contributions to the new fork etc. Love seeing the community come together

  27. Jonfor commented on Jun 6, 2025

    @Jonfor

    @stampthecoder I'm not sure how else to message you - could you give me admin on the new repo so I can manage it's settings?

  28. WilliamDeBruin commented on Jun 30, 2025

    @WilliamDeBruin
    Contributor

    Given recent activity from @newm4n who appears to be the primary owner I believe it is appropriate to resurface this conversation. Multiple PRs/commits were recently merged so want to make sure than any fork(s) are kept up-to-date and that the project does not diverge

  29. newm4n commented on Jul 1, 2025

    @newm4n
    Collaborator

    Hi All, first of all, I would like to say THANK YOU ALL.
    Its all been my short comming. Mainly due to my health issue. But because of all of your invaluable trust on the project, the project
    keeps going alive, through continuous contributions and/or forks.

    I'm fully aware of my limitation and thus looking for good watcher and caretaker of this open source project, so it wont goes vacum like it was.
    I will fully help you if you're willing to contribute your time on the project, as long as I have the user right to do so in github, and under the organization, hyperjump. Eg. making new reviewer, grule admins, releaser, etc.

    In my current state, what I've been doing so far is.

    • Comment or Accept or Reject PRs.
    • Auto Merge new changes whenever possible if some commits in the master is ahead of the PR, If can't. I will comment to ask the PR maker to update their branch.
    • Approve the workflow to run, if needed or not done automatically by github.
    • Make a tag before release.
    • Make a new release.

    I have a good hope that you will help to do any of those and I willing to help to enable you to do it.
    Lets discuss this or advise me to do next appropriately.

    Ferdinand

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions