User Details
- User Since
- Jul 2 2024, 11:16 (28 w, 3 d)
- Availability
- Available
Dec 17 2024
Perhaps we need an interact policy for events?
What do other CLAs do about this?
I'm... honestly not sure, I haven't signed one before. If I had to, I'd ask the maintainers before doing so ^^;
Dec 14 2024
Would the CLA have to be signed with one's legal name?
Dec 12 2024
I wonder if we can expand that to provide an authorUser too, in many places as possible 🤔
but i'm lazyyyy :(
Dec 11 2024
Turns out that this doesn't work if the file is uploaded via chunking
$params has an optional authorPHID key, whose value is... well, the PHID of the author (if applicable). I suppose we can reuse that here?
Move assertion to a different function
Wrote the code for the first phase :p
Sounds good to me :p
Dec 9 2024
Yeah, I agree, though I would then only work on implementing files.maximum-file-size because we don't really care that much about adding exceptions to the rule (as far as I know lol)
Dec 8 2024
Nov 25 2024
Oct 2 2024
Thanks for the very detailed answer! I may or may not take a stab at this if the person who originally asked for it decides that this is worth the effort.
Aug 19 2024
Aug 13 2024
Jul 3 2024
I haven't looked at Phorge's internals much yet, but perhaps the user could unmark a task as duplicate, or have the "Close As Duplicate" box be prefilled with the task that closed it and let the user deselect that and choose another one?
Jul 2 2024
I was able to reproduce this on a test instance even though the task is closed long ago: