dotya.ml/community
2
1
Fork 0
Code Issues 24 Projects 2 Activity

Distributed compilation #11

New Issue
Open
opened 2020-11-01 11:32:46 +01:00 by kreyren · 3 comments
kreyren commented 2020-11-01 11:32:46 +01:00
Copy Link
Copy Source

Provide handling of DistCC https://github.com/distcc/distcc that would allow crowdsourcing with the intention to support development through providing spare resources with optimized scheduler to not affect the main runtime that anyone can contribute their system resources to.

Provide handling of DistCC <https://github.com/distcc/distcc> that would allow crowdsourcing with the intention to support development through providing spare resources with optimized scheduler to not affect the main runtime that anyone can contribute their system resources to.
kreyren changed title from distcc to Distributed compilation 2020-11-01 11:52:06 +01:00
kreyren commented 2020-11-01 11:52:40 +01:00
Author
Copy Link
Copy Source

Relevant: https://github.com/icecc/icecream

Relevant: https://github.com/mozilla/sccache (should work for rust-lang)

Relevant: https://github.com/icecc/icecream Relevant: https://github.com/mozilla/sccache (should work for rust-lang) - https://github.com/rust-lang/rust/issues/32664
wanderer commented 2020-11-01 22:58:59 +01:00
Owner
Copy Link
Copy Source

@kreyren - what are the security implications of "crowdsourcing" the computing resources that anyone could contribute?
I've read it's best if you are in control of the machines running the jobs (makes sense)..

@kreyren - what are the security implications of "crowdsourcing" the computing resources that anyone could contribute? I've read it's best if *you* are in control of the machines running the jobs (makes sense)..
kreyren commented 2020-11-02 05:29:37 +01:00
Author
Copy Link
Copy Source

Well in general you should optimize your permission handling so that running processes woudn't have unwanted access.

Needs to be brainstormed, but my approach would be to let the contributors to handle their system and on demand provided a pre-set method e.g. AppImage

Well in general you should optimize your permission handling so that running processes woudn't have unwanted access. Needs to be brainstormed, but my approach would be to let the contributors to handle their system and on demand provided a pre-set method e.g. AppImage
wanderer added the enhancement label 2021-05-02 04:56:02 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
FCKPTN
Fuck you, Putin!
WIP
Work in progess.
 bug
Something is not working
 docs done
Documented
 docs needed
Missing documentation
 duplicate
This issue or pull request already exists
 enhancement
Brings improvements
 feature
Adding a feature
 gemini
Pertaining gemini
 invalid
Something is wrong
 legal-ish
Concerning a legal issue
 needs help
Help is welcome
 onionz
Related to an onion service 🧅
 proposal
Proposes a change
 question
More information is needed
 resolved
The issue has been resolved
 security
This issue impacts security
 spam
Spam
 todo
Waits to be done
 upstream-related
This issue is related to an upstream project's issue
 wontfix
This won't be fixed
No Label enhancement proposal question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dalahast wanderer
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dotya.ml/community#11
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?