Replies: 39 comments 35 replies
-
Do not allow Hosts to hide their hosted Collectives #5278I don't think we should wait on #5457 - let's prevent disabling Contributions for active hosts now |
Beta Was this translation helpful? Give feedback.
-
Record merchant account timestamps #5817OCF really needs this for accounting/compliance. |
Beta Was this translation helpful? Give feedback.
-
Ledger improvements #5509It's time to look back at the ledger and clear some technical debt before the start of the new year! |
Beta Was this translation helpful? Give feedback.
-
Expense based Contributions between Hosts #5100Let's make sure money can flow easily between Hosts. |
Beta Was this translation helpful? Give feedback.
-
e2c Comms WorkWe could do a better job surfacing the ongoing conversations around e2c, and making sure the conversations appear as active as they genuinely are: |
Beta Was this translation helpful? Give feedback.
-
Add local tax support to "Add funds" (VAT, GST) #5927Relatively small change to fix a painful issue that has no workaround and the dev team has to process manually. |
Beta Was this translation helpful? Give feedback.
-
#5815 Add Ask for Collective slug/url in 'Contact Us' formI think this should be a simple fix that would really assist the support team |
Beta Was this translation helpful? Give feedback.
-
#3781 Page in user settings to manage sessionsAn important security feature. |
Beta Was this translation helpful? Give feedback.
-
#5736 Revamp "Applications" and replace with "Personal Tokens"This is getting old and ugly. And "scope" support is much needed. Would be nice improvement for Developers. |
Beta Was this translation helpful? Give feedback.
-
Host admin can set date when confirming or adding contribution #5693This change would help a lot with accounting a bookkeeping practices. |
Beta Was this translation helpful? Give feedback.
-
Pledges ReduxI'm adding this mainly to get feedback on the idea of revitalising pledges in order to solve some of the fractalization issues that exist and to encourage more projects — across all hosts — to adopt transparent financial management. Please dive into the discussion at #6027 |
Beta Was this translation helpful? Give feedback.
-
Users cannot approve their own expenses as an enforceable policy #6075A while back we asked that this feature be implemented as something a host could enact as policy, instead it was argued that we should implement it as a good will policy tool for collectives. This isn't working for us. Given recent events we have begun paying more attention to the small (2%) of transactions that are considerable sums. In these cases any signal that we can get that others in a collective approve of expenses eases the burden on us. Without it we must try to track down historical behaviours and/or wait and hope that someone else in the community notices. For example (private link) Edit: apologize, removed a Bernie Sanders meme which made its time and could unfairly attract attention when looking at all proposals --François |
Beta Was this translation helpful? Give feedback.
-
Public Collective activity timeline #5767My understanding is the current activity log work is focused on a more back-end feature mainly used by admins. I think there's big potential for a more public version of it used for community accountability and trust-building, funder due diligence, and many other functions that are only possible if it's publicly transparent. I don't imagine we'd include as much detail as the admin version of the log and we'd need to make it more user-friendly and pretty. |
Beta Was this translation helpful? Give feedback.
-
Get OCF's custom application form ready to replicate #5354I am assuming we are still looking for a cheap MVP in this area, but there has also been a suggestion to do a custom form builder feature or integration with form builder(s) to enable this. OCEU, Gift Collective, OCNZ, and other hosts would benefit a lot from not having to juggle an external application form. |
Beta Was this translation helpful? Give feedback.
-
I'm concerned about the speed of our website - #6036 |
Beta Was this translation helpful? Give feedback.
-
Alternative Captcha provider #6060We're hearing some frustration from contributors on support channels. |
Beta Was this translation helpful? Give feedback.
-
Onboarding flow - Find a host #5672Follow-up with the work to improve our onboarding flow, specifically with the experience of finding a host embedded inside the onboarding flow for Collective admins. We said we wanted to make the onboarding flow a priority, and we have only done #5399; I propose to take on 2 or 3 more projects from #4829 (comment) before this year is over. |
Beta Was this translation helpful? Give feedback.
-
Contribution flow improvementsSome time ago, we prioritized this project #4893. It was split into #5631, and design research is documented here #5732. |
Beta Was this translation helpful? Give feedback.
-
Profile page iteration (Continuation) #5680We need to follow up on this project so it does not lose momentum; we will do the first round of designs this sprint, but there is still a lot to do, and I think we need to involve the dev team starting this next sprint cycle. |
Beta Was this translation helpful? Give feedback.
-
Improve storytelling for Collectives #4823We prioritized this project earlier this year, and it's a great idea, IMO. The design is ready; we just need to implement it. |
Beta Was this translation helpful? Give feedback.
-
Confirm your credit card email looks phishy #5812Common support request currently - very confusing for users |
Beta Was this translation helpful? Give feedback.
-
Pending Contributions #5769This issue was originally proposed by @natehn |
Beta Was this translation helpful? Give feedback.
-
Dedicated page for users to see all submitted expenses #3749Common ask in support especially caused drama when the paypal outage happened recently and users had trouble finding their submitted expenses |
Beta Was this translation helpful? Give feedback.
-
Enable new PayPal integration for all hosts #4210Also includes #5923.
|
Beta Was this translation helpful? Give feedback.
-
Redesign the page to edit tiers #3438The page is actually implemented, we just need to figure out a release plan:
|
Beta Was this translation helpful? Give feedback.
-
Horizons: funder oriented discovery experience of what is happening in the OpenCollective ecology #6073This has been in preparation for the last few weeks (details in the issue) and is now being pitched for implementation. |
Beta Was this translation helpful? Give feedback.
-
#6077 Tags should be required when creating a CollectiveThis is a follow-up of #4764. We are investing a considerable amount of resources in creating new features such as the new discovery (a.k.a. Collective weather report), the Funders Contributors' dashboard, and the search-related targets like #3892 #3782 #5793 #5809 . |
Beta Was this translation helpful? Give feedback.
-
Transform E2C page into a CMSCurrently changes to the E2C page require intervention of a designer and possibly an engineer. |
Beta Was this translation helpful? Give feedback.
-
Introduce a centralized authentication permissions library #6085The recent introduction of OAuth, 2FA (and fraud protection?) have made our mutations quite messy because of the numerous permission checks that need to take place. It is error prone (easy to forget something) and won't help us to enforce best practices in the team. I'm expecting this project to have a limited complexity, the most expensive part is probably to discuss and agree on specifications. |
Beta Was this translation helpful? Give feedback.
-
quick update on prioritisation following a conversation between myself and @znarf: external commitments strategic priorities Tactical priorities Engineering, Support and Ops Extra capacity |
Beta Was this translation helpful? Give feedback.
-
This is the discussion to begin surfacing ideas for Q4S1.
How to use this discussion
Surfacing an idea looks very similar to ideas that have been shared in previous discussions we ask that you think about problems, (not solutions) and the impact of those problems. Consider the following questions:
Who is your user?
What are they trying to achieve?
It's useful to use the following format when trying to reflect this:
When ____ , I want to ___ , so I can ___
We ask submitters to select problems that have both a high degree of impact and a high degree of alignment with our focus areas. If there's an existing issue, please reference it, if not please click here to create one.
We encourage everyone to surface ideas as early as possible so that we can start working toward a project pitch.
During the sprint (in parallel with development) we work together to create a pitch that can then be reviewed in prioritisation.
If you'd like to read more about pitches, or generally find out more about our preferred approach to development check out Shape Up by Ryan Singer (it's free)
Beta Was this translation helpful? Give feedback.
All reactions