I vote +1 in favor of the split. I was a bit torn between the two options, but overall I came to the conclusion that I prefer several smaller sub-projects over a large monolithic one.
In addition to the points Mikael already made, I like the sheer possibility of being able to downgrade parts of HPX independently of the rest. For example, right now I would actually like to have the CUDA executors introduced in HPX 1.5.0 together with the distributed part of HPX 1.4.1 for some tests (sure, this might still fail for a whole host of reasons/incompatibilities depending on the actual versions but it would be nice to have the possibility in the first place - the versions mentioned here are just meant as an example). This requires extensive testing of both repositories to work, of course. The latest releases should be guaranteed (best as possible) to work together. Ideally the CI of both repositories should trigger jobs which use them together (so that people who use master on both get fewer nasty surprises). All of this can be build on top of the already existing Jenkins CI at both LSU and CSCS. As long as we keep the already existing communication infracstructure (IRC, biweekly meetings, mailings lists, Github group ...) I am also rather optimistic that the community will not drift apart as a result of this. On the contrary, I could see having an HPX core sub-project attract additional users. Best regards, Gregor On Mon, Jun 07, 2021 at 07:53:06PM +0000, Simberg Mikael wrote: >Dear HPX users and developers, > >The HPX users and developers at CSCS (that includes myself) have expressed an >interest in separating the local-only and distributed functionality of HPX >into two separate projects and repositories. This is a contentious topic, so >before we do a large change like this we want to consult the community through >a vote. My personal vote and motivation for the change will follow in a >separate message. > >Practically speaking, the proposal is to move the on-node functionality of HPX >(this includes futures, algorithms, basic CUDA/HIP support, a local-only >runtime, and all the utilities required to support this) into a separate >repository. The remaining distributed functionality of HPX would keep the hpx >name, stay in the current repository, and it would gain one new dependency, >called (e.g.) hpx-local. Releases of hpx and hpx-local would often be done >together, but could be done independently of each other. The aim is to affect >current users of distributed features of HPX as little as possible, while >giving users of local-only features a project that, by default, gives them >only local functionality. If there's consensus to go ahead with a split, we >will also consider splitting HPX into more than two projects. > >Voting works as follows (from https://hpx.stellar-group.org/governance/): >If a formal vote on a proposal is called (signaled simply by sending a email >with [VOTE] in the subject line), all participants on the HPX user’s mailing >list may express an opinion and vote. They do this by sending an email in >reply to the original [VOTE] email, with the following vote and information: > >- +1: ‘yes’, ‘agree’: also willing to help bring about the proposed action >- +0: ‘yes’, ‘agree’: not willing or able to help bring about the proposed >action >- -0: ‘no’, ‘disagree’: but will not oppose the action’s going forward >- -1: ‘no’, ‘disagree’: opposes the action’s going forward and must propose an >alternative action to address the issue (or a justification for not addressing >the issue) >This is a "Concensus approval" vote (see governance document for details). >Responses from developers and users alike are encouraged. Please vote as soon >as possible, but we will leave the voting open until Thursday 17th June. > > >Kind regards, > >Mikael Simberg >_______________________________________________ >hpx-users mailing list >[email protected] >https://mail.cct.lsu.edu/mailman/listinfo/hpx-users _______________________________________________ hpx-users mailing list [email protected] https://mail.cct.lsu.edu/mailman/listinfo/hpx-users
