Skip to content

Milestones

List view

  • No due date
    4/4 issues closed
  • No due date
    32/32 issues closed
  • No due date
    10/10 issues closed
  • No due date
    9/9 issues closed
  • No due date
    38/38 issues closed
  • No due date
    13/13 issues closed
  • No due date
    46/46 issues closed
  • No due date
    55/55 issues closed
  • No due date
    40/40 issues closed
  • 1# version

    Due by March 18, 2025
  • No due date
    10/10 issues closed
  • this error shows up a lot when deploying a bonfire instance

    No due date
  • No due date
    131/131 issues closed
  • No due date
  • No due date
    7/7 issues closed
  • No due date
  • No due date
  • - Add a built-in moderator role (for instance and groups) - Implement ability to edit an existing object's boundaries - Organize instance circles in categories and add pagination - etc

    No due date
    19/19 issues closed
  • No due date
    18/18 issues closed
  • No due date
    34/34 issues closed
  • No due date
    2/2 issues closed
  • No due date
    10/10 issues closed
  • No due date
    3/3 issues closed
  • No due date
    8/8 issues closed
  • No due date
    38/38 issues closed
  • No due date
    11/11 issues closed
  • Basic boundary system (local and federated) and test coverage

    No due date
    14/14 issues closed
  • Feedback: - UX: I wasn't sure if Topics functioned like a forum topic, or if they were more like a hashtag that grouped related posts. Still not totally sure, to be honest. It felt strange that the list of topics and recent posts were split into two even columns—I wasn't sure which was supposed to be the main content of the page, and what I should be looking at. I also wish each Topic told me things like number of comments/sub-topics and when the last post in it was, so that I could see which Topics are active without having to open each one. Also odd that on the front page, Trending Topics lists topics that start with hashtags and ones that do not (e.g. "#humour" alongside "bonfire") which adds to my confusion of how they work and what they are. I wanted to reply to one topic, but when I hit "Reply" it said I was creating a "sub-topic" (with fields for "category" name and description) and prompted me for a title, so I wasn't sure if I was creating a comment thread/chain, or if it would create a separate sub-topic within the main topic, or how things work at in general. - UX: Topics in general feel really weird to me. The reverse-chronological order is really off-putting, as is the lack of clarity of how replies go together. I tried replying to someone and it seemed to create an entirely different topic. It looks like these subtopics have threaded replies within them. None of this makes much sense to me at all. I did see some of the team's discussions on Matrix or something about trying to come up with a better way of having discussions, which I think is a great and admirable goal, but this current implementation is far less clear to me than any forum or comment page I've ever visited before. When I replied to someone's topic, I just ended up creating a series of sub-topics, which I then had no way of deleting. - Tried to reply to a topic, got the error "A condition didn't receive data that matched a format it could recognise." Refreshed and tried again, and it worked. - UX: Things feel split up in a non-intuitive way that I'm still struggling to figure out. It looks like Topics are more of a forum-type discussion where people can post about a specific subject, and the main feed is where you're meant to post about anything you want (like a Twitter or Facebook profile). However, I'm not sure how they connect, or if they do, or which one is the "main" one. Maybe that's up to the admin of the individual instance. But at this point I remain somewhat confused. Little things like my Feed and the homepage having a box for "Trending topics" when the Topics page doesn't are minor details that lead to me feeling a little los - UX: I also find it a little weird how sometimes I'm making a "Post" and sometimes it's a "Sub-topic" — I get that it just depends on whether or nor I'm in the Topics page, but I wish there was a clearer visual differentiation. For instance, a floating textbox whenever I make a post, and a nested textbox within topics (and maybe it floats when scrolling through a topic, but maintains the width/position of the topic column so that it feels more integrated).

    No due date
    0/4 issues closed
  • - [ ] Delete a page works but redirect to error after the deletion - [ ] fix drag-drop ordering of sections on page & pages in nav

    No due date
  • - [ ] I have an "Untitled task" that I can't open or delete. Opening it brings me to a page reading "An error occurred" while deleting it allows me to hit "Delete this intent" but then the page reloads and it's still there. It's also always at the top of my Feed and can't be removed from there either. It wasn't there at first, I think it appeared after I played with the tasks feature. - [ ] it's not clear whenever i'm looking at a task or at a milestone in the tasks feeds - [ ] When I mark as completed a task in the list view, it does not update automatically (need refresh) - [ ] Assign to myself a task in list view not working - [ ] Tasks page: Assigned to not working - [ ] Due date not update automatically - [ ] Due date UI needs improvement - [ ] Delete a task redirects to the error page (and remain a "Untitled task" leftover in feeds) - [ ] add edit task title - [ ] Add correct actions to process activity preview - [ ] show task and process as preview when navigating from feeds -> WIP but leaving for later - [ ] task and process as preview -> ? - [ ] delete a task not remove from feed - [ ] show relative dates for tasks based on only day (eg today) vs time (eg. 6h ago)

    No due date
  • Tracking all the bugs and features we want to have in place, preparing for a Release Candidate

    No due date
    22/22 issues closed
  • No due date
    13/13 issues closed
  • No due date
    12/12 issues closed
  • No due date
  • No due date
    30/30 issues closed
  • Users can create or subscribe to opt-in moderation lists, and - according to permissions - contribute to them. Such opt-in lists may include flagged and blocked content (incl. posts, links, people, bots and instances) that are considered harmful, as well as trusted and verified content. Users can subscribe to multiple lists, focused on different topics or with different governances.

    Due by July 31, 2022
  • The community can decide to decentralise power and responsibility from admins by adding more custom roles to efficiently manage moderation and resolve conflicts.

    Due by June 15, 2022
    2/2 issues closed
  • Users, moderation list editors, or instance moderators can add labels to content, either by hand or by creating filters for auto-labelling (based on the source of information, keywords or patterns in the content or metadata, etc). Labels are shown in feeds to aid with quickly identifying certain aspects of information or misinformation. Each label can link to a wiki page with explanations and context.

    Due by July 15, 2022
    13/13 issues closed
  • Due by May 30, 2022
    53/53 issues closed
  • Due by April 30, 2022
    6/6 issues closed
  • Due by April 10, 2022
    7/7 issues closed
  • Attempting to stabilise as much of the framework as possible so that developers are free to build against it without risking their code breaking.

    Due by May 31, 2022
    21/21 issues closed
  • 1. Develop the needed features for the 1.0 official release. 2. Fix major/blocking bugs

    No due date
    106/106 issues closed
  • Due by October 15, 2022
  • Prototype an optional extension to experiment with machine learning algorithms to expand on Zappa's community assessments.

    Due by August 15, 2022
    0/1 issues closed
  • Design and develop an alpha version of the Zappa extension, iterating with feedback sessions with pilot users. Includes both the backend and user interface.

    Due by June 15, 2022
    2/2 issues closed
  • Focused on user safety, like flag/block/delete, and federating with other ActivityPub apps.

    Due by February 28, 2022
    25/25 issues closed
  • People and communities should be able to setup and customise their own instance, follow each other, share content, have discussions (private or public), etc, whether they use Bonfire or other fediverse software.

    Due by April 30, 2022
    12/12 issues closed
  • Run a series of co-design sessions, with pilot groups and the wider fediverse community to create a set of comprehensive and inclusive user stories that will guide us during the development of the Zappa extensions.

    Due by April 15, 2022
    3/3 issues closed
  • Let's solve all the main bugs that prevent us to setup and use the social flavour among us. Dogfooding includes: - Basic Auth flow - Create a post, specify its privacy levels (choosing from a predefined list of boundaries) - Start a thread over a post - Follow / Unfollow / Mention users - Like, boost, report posts - View different feeds correctly (Federated, Local, Home, Profile, Notification) - Receive browser push notifications - Let admins invite users with an invitation link - Let admins delete a flagged post from feeds - Federate between different instances of Bonfire

    Due by January 15, 2022
    18/18 issues closed