Conversation
|
T&C Assistant Lite bot All Contributors have signed the latest T&Cs. |
|
I have read and hereby sign the JAM Prize Terms and Conditions. |
|
Hey @sourabhniyogi , thanks for your submission. I'm going to evaluate it. The rules of the JAM Prize require your repository of the JAM client to be open source and public. See rule 26. Let me know if you have an questions. |
@PieWol Here you go: https://github.com/jam-duna/jam I had thought:
I believe this notion is worth aiming for, and that the "I just sent an invite..." pattern should be dominant. More than a few teams have M2/M3 type code (and more than few do not) I'm sure, and we should continue striving for max clean room compliance, which is best supported by the "I just sent an invite..." pattern, with most all teams continuing "closed source" for most of 2026. Did this notion disappear? |
@PieWol Thank you for adjusting Rule 26 to "The repository must include a clear and permissive open-source license. Members of W3F and the Technical Fellowship must be invited to the repository upon request." -- this will support clean room objectives well. We have invited to https://github.com/jam-duna/jamduna @PieWol and @CrackTheCode016 and @semuelle -- please let us know if there is anyone else needing an invite and what the sharing process is for the fellowship. Update: We have updated our binary in 0.7.2.15 to address what we believe we have observed (11+ IO errors that we believe are memory issues + 1 real code issue) |
|
Thank you for your submission. Please note that you need to accept our latest Terms and Conditions before your submission can be considered for the JAM Prize. Please submit the following text as a separate comment:
|
|
I have read and hereby sign the latest JAM Prize Terms and Conditions. |
Milestone Delivery Checklist