Welcome to MilkyWay@home

Pull request not having any attention--is that expected?


Advanced search

Message boards : Application Code Discussion : Pull request not having any attention--is that expected?
Message board moderation

To post messages, you must log in.

AuthorMessage
muzzdiez

Send message
Joined: 21 Mar 15
Posts: 2
Credit: 13,332,583
RAC: 9,361
10 million credit badge6 year member badge
Message 70217 - Posted: 4 Dec 2020, 23:14:35 UTC

Hi all,

I have a specific hardware platform that has Elbrus-8C CPU on board, and I've had some time porting Milkyway (along with some other projects, like RakeSearch and LHC@home) onto it: both as a proof-of-concept that BOINC may be run in anonymous platform mode on Elbrus, and as a compatibility and portability test for Milkyway. Finally I've had success in it, and I made a pull request to Milkyway's upstream: https://github.com/Milkyway-at-home/milkywayathome_client/pull/81

I even had a continuous run of BOINC with NBody and Separation on the host https://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=807088 for about a year since, and I consider it proven that these fixes I've done really made Milkyway apps compatible with Elbrus, and possibly, other alternative platforms like ARM, MIPS, SPARC, RISC V, etc.

But there's nearly a year has been passed since I did this, and I have neither any reaction to pull request mentioned, nor any conclusion from maintainers, to merge it or close without merge for some reason. But code isn't abandoned, commits are pushed and even other pull requests are merged, so development is active there.

Is there a chance anybody have an idea how I can draw some attention to my pull request? I'm up to add more Elbrus stations to my BOINC pack, and it would be much better if modern upstream is compatible with Elbrus, not just my year-old fork, so I clone, build, and go--instead of cloning current upstream and applying a diff I suggested in my pull request, to it.
ID: 70217 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilemikey
Avatar

Send message
Joined: 8 May 09
Posts: 2550
Credit: 462,666,679
RAC: 8
300 million credit badge12 year member badgeextraordinary contributions badge
Message 70220 - Posted: 5 Dec 2020, 11:52:56 UTC - in response to Message 70217.  

Have you considered bringing it to the attention of the Boinc Admin group that writes and maintains the Boinc software? The guy in charge Richard ? is very interested in advancing Boinc.
ID: 70220 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
muzzdiez

Send message
Joined: 21 Mar 15
Posts: 2
Credit: 13,332,583
RAC: 9,361
10 million credit badge6 year member badge
Message 70221 - Posted: 5 Dec 2020, 15:54:03 UTC - in response to Message 70220.  

For now, no, as I consider it the problem of Milkyway, not BOINC itself. Or do you mean BOINC type of Milkyway applications?
ID: 70221 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilemikey
Avatar

Send message
Joined: 8 May 09
Posts: 2550
Credit: 462,666,679
RAC: 8
300 million credit badge12 year member badgeextraordinary contributions badge
Message 70572 - Posted: 12 Feb 2021, 12:49:02 UTC - in response to Message 70221.  

For now, no, as I consider it the problem of Milkyway, not BOINC itself. Or do you mean BOINC type of Milkyway applications?


I meant overall Boinc and the guys name is Richard Hassellgrove, if it's a common processor then he might be interested but one off things that aren't very common he may not be interested in and you may be more lucky with getting a project by project app going.
ID: 70572 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ProfileTom Donlon
Volunteer moderator
Project developer
Project tester
Project scientist

Send message
Joined: 10 Apr 19
Posts: 145
Credit: 60,012,676
RAC: 123,236
50 million credit badge2 year member badge
Message 70573 - Posted: 12 Feb 2021, 15:36:43 UTC

Hi muzzdiez,

Thanks for your contribution to our project. I agree with mikey that it may be better to go down the road of contacting BOINC instead of pushing to MilkyWay, since we do try to follow BOINC updates.

I will contact the lead developer on the project and see if he has noticed this (and possibly other) requests.

Best.
Tom
ID: 70573 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Application Code Discussion : Pull request not having any attention--is that expected?

©2021 Astroinformatics Group