Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

M3 initiating and planning #106

Closed
8 tasks done
sutty-coop opened this issue Dec 28, 2023 · 3 comments
Closed
8 tasks done

M3 initiating and planning #106

sutty-coop opened this issue Dec 28, 2023 · 3 comments
Assignees

Comments

@sutty-coop
Copy link
Collaborator

sutty-coop commented Dec 28, 2023

We are taking from mid-December to mid-January (aprox) to scope M3 and develope a schedule for tasks and deliverables inside the milestone.

We have clear goals (ready for effort estimation, issuing and calendarizing) and a few doubtful features (we need to discuss wether we keep or drop them, prioritizing)

Clear goals:
#103
#102
#104

Pending or doubtful:

  • a. Deletion of posts, is possible? ImDef asked about this. It's issued here: Ensure activities are deleted when requested #159
  • b. Bringing older posts prior to the following of ther account, is possible? Interesting from a usability POV.
  • c. Do we want to add metadata to images? / It's a nice to have, only if we get the time
  • d. M3 - Automated Announcements of Decentralized Websites #101 the “announcing new account” is vague and we need to define clearer scope before estimating effort / calendarize it
  • e. Mauve to write down their idea on “social reader” and we discuss it. See M3 - New ActivityPub Client #102
  • f. Decide on federating with Threads
  • Confirm that we are dropping this (was present in 1st document with FFDW): Content versioning. Distributed Press will officially support listing and fetching of specific versions of published content, along with API responses that it internally generates over time. Mauve says it could be valuable to re-visit this on Milestone 4, related to verification features.
  • Confirm that we are dropping this (was present in 1st document with FFDW): Content storage redundancy. Sutty adopting the activestorage-ipfs Rails plugin into their infrastructure. Distributed Press will add support for remote pinning for both IPFS and Hypercore.

M3 processes wishlist

  1. We'll do more calendarizing, having timelines, checking in periodically regarding the time-line.
  2. We'll take more time in testing. We should test prototypes, to validate our decisions, not just ready-to-launch features. Ben + users?
  3. We'll open issues for bugs, and follow the labels Bug- Review needed - Testing - Ready...
  4. We'll include Sutty's work in one card in the Board, whit links to the 0xacab issues.
  5. We'll have a new type of bi-weekly meeting for parallel goals: - business - organizational

Image

@RangerMauve
Copy link
Contributor

Thank you for putting this together! V useful summary of the state of things.

@sutty-coop
Copy link
Collaborator Author

sutty-coop commented Jan 6, 2024

Update from weekly meeting Jan 4th:

  • “announcing new account” was better defined. See details in 101

  • "bringing older posts prior to the following the account" was adressed. TO DO: @RangerMauve will find an issue re: "older posts not visible" and we'll continue from there. It's here

  • "moderation queue in CMS" will be presented as a prototype before Jan 15th. Others can validate and give feedback.

  • we'll add "workshops with communities" as a deliverable to M3

  • deletion of posts to be scoped by Mauve, could Sutty implement?

@sutty-coop
Copy link
Collaborator Author

Final step:

  • Each team estimates work packages and times of completion
  • Creates issues
  • We work on a common calendar where we also consider tasks that include dependencies of Sutty)(Hypha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants