[TRACKING] FEP-e232: Object Links #14
Labels
No labels
bug
contribution welcome
duplicate
enhancement
FEP Draft
FEP Final
FEP Withdrawn
final comments
good first issue
help wanted
invalid
meta
question
syntax fix
upstream
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
fediverse/fep#14
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Proposal by @silverpill
The proposal has been received. Thank you!
This issue tracks discussions and updates to the proposal during the
DRAFTperiod.Please post links to relevant discussions as comment to this issue.
dateReceived: 2022-08-01If no further actions are taken, the proposal will be automatically set to
WITHDRAWNon 2022-12-01 (in 4 months).Thank you @silverpill if the outstanding review comment on #13 is resolved we can merge the DRAFT.
After that is done, can you create a discussion on SocialHub in Fediverse Enhancement Proposals category titled "FEP-e232: Object Links", with tags
fepandfep-e232, a brief introduction and a link to your draft at Codeberg?Relevant conversations I'm aware of:
@circlebuilder I've resolved trwnh's review. I would like to keep two remaining comments open if it's possible, as they explain certain design decisions.
We already have a discussion about quotes on SocialHub, should I create a new one regardless?
There's no hurry on getting the draft merged. A separate SocialHub topic is part of the FEP process and can help attract attention to your document. It is also easier to find later. The forum is like an archive in that regard.
In the new topic you can make reference to the other one (where you can add a comment to fully cross-ref). Text can be short, that is up to you. But you might point out aspects that you are most in need of feedback for. Among goals of the FEP is to get exposure to the enhancement, and as much consensus and buy-in so other apps will adopt it hopefully.
Thanks, I've created the topic: https://socialhub.activitypub.rocks/t/fep-e232-object-links/2536
I can't find a way to add new tag, so for now I only added
fepanddraft, withoutfep-e232.Is there anything else that needs to be done?
To match newly implemented automation the discussion topic was moved to: https://socialhub.activitypub.rocks/t/fep-e232-object-links/2722
If you feel everything's been addressed, then in a few days it becomes eligible for FINAL.
We discovered that this FEP is not backwards compatible with Pleroma.
I would prefer to not finalize it until this issue is addressed (either by patching Pleroma or by changing the FEP). I also think there should be at least two interoperable implementations before we can consider it FINAL.
This would be good to discuss in a new issue.
That's just my preference in regards to FEP-e232. I think it shouldn't be applied to all proposals, which may describe something other than a protocol extension.
Proposal was updated via #173
Another update: #203
And I'm requesting finalization of this proposal: https://socialhub.activitypub.rocks/t/fep-e232-object-links/2722/58
Looks like no final comments so created a new branch
finalize-e232. Was going to edit the README.md but it says to use the create_readme.py script so leaving a note here until I can get the script going. Feel free to update the branch and create a PR if you see this and have the script handy.Can you describe your problems?
I just have to run
and README.md is updated. Maybe I should add the missing "python" in the note?