Replies: 57 comments 33 replies
-
Add PDF attachments to expense comments #3433I think this falls under Communication - between us and our users, primarily, though also occasionally for comms between users. From the outside, it seems easier than #4894 to implement and meets some (though not all) of its needs. There are many use cases:
It's also worth considering if there are other file types we'd like to enable in addition to pdf, though pdf would be priority. |
Beta Was this translation helpful? Give feedback.
-
Host admins can see Collective admins #5426This is one is important, because sometimes collective admins want to hide their admins (which is fine by me), but at minimum, their fiscal host should be able to see that they have admins - especially if minimum # of admins are required by the host |
Beta Was this translation helpful? Give feedback.
-
Host can automatically tweet when a new Collective is approved #4765We already have auto-tweets setup for when they reach 10 backers etc.; this would be a nice way to welcome a new group/connect on twitter with them right from the start (& many OCF-hosted groups use Twitter) |
Beta Was this translation helpful? Give feedback.
-
#5318 and #5275 e2c Contente2c Conversations & Work are ramping up, need to have our public-facing content organized and up-to-date |
Beta Was this translation helpful? Give feedback.
-
Contributions between hosts #3190We have a broken process for contributing using balances held by hosts. The error messaging is terrible #5504. Principally this creates a walled-garden for each host, creating friction for users on both sides of a contribution. This is a limitation for Funds and limits Open Source Collective's strategic objective to move toward an ecosystem-based approach to supporting open source communities. |
Beta Was this translation helpful? Give feedback.
-
|
I started implement it in opencollective/opencollective-api#6534 but we got stuck about the necessity of Host Admins to validate the contributions. We ended up with this proposal: #5100 |
Beta Was this translation helpful? Give feedback.
-
|
Cool, commented #5100 (comment) |
Beta Was this translation helpful? Give feedback.
-
Improve validations when inviting expense payee #5020Inviting expenses is already complex, and problems like this make it even more challenging for users to get through. The forms should work predictably and show clear error messages so the user can be informed and recover from mistakes. According to @Betree this will also solve #5306 which is important for simplification. I gave someone detailed 15 step instructions to complete the process of inviting some expenses, and they still got derailed because of this problem. See his prior comment. |
Beta Was this translation helpful? Give feedback.
-
|
@Betree said: Solving #5020 would solve #5306 directly. All these issues have the same root cause, which is that we changed the validation strategy at some point and it wasn't a good call. That's what I tried to summarize in #5330 (comment) last sprint. |
Beta Was this translation helpful? Give feedback.
-
|
Also relates to #5429 |
Beta Was this translation helpful? Give feedback.
-
Page in user settings to manage sessions #3781As an MVP, we can start with the backend part only (without the user's ability to manage sessions). This issue is an important step to improve the security of our login system. |
Beta Was this translation helpful? Give feedback.
-
#1738 Allow username/password loginPeople really want this |
Beta Was this translation helpful? Give feedback.
-
|
easier yes but it leaves SO much room for phishing and scamming and people are just really not good with maintaining strong passwords i would be worried about what it would open us up to. |
Beta Was this translation helpful? Give feedback.
-
#5516 Allow fiscal host to choose where to "Bill To" automatic invoices@alanna and I have different needs regarding info displayed on automated invoices generated by OC |
Beta Was this translation helpful? Give feedback.
-
Allow Host to turn off expense type(s) for Collectives #5525I see this as a small change (but maybe I'm wrong and it isn't so small?) that can help make the platform more legible for certain kinds of fiscal hosts. Strategic priority: Interoperability (in this case, with a different set of legal agreements haha) |
Beta Was this translation helpful? Give feedback.
-
Batch monthly payments |
Beta Was this translation helpful? Give feedback.
-
Purchase Cart modelAllowing users to subscribe to multiple collectives in one go instead of creating one payment per subscription |
Beta Was this translation helpful? Give feedback.
-
|
Is this like 'backyourstack for everyone'? |
Beta Was this translation helpful? Give feedback.
-
|
I'd just like to say that, to me, this is a solution looking for a problem. And from what I have seen the real, underlying problems here are:
maybe there are more, but I think it enables to team to contribute better to creating a solution rather than pre-supposing one and having the team work back to understand what the actual needs/problems are. |
Beta Was this translation helpful? Give feedback.
-
|
there is, of course, the other side which is the opportunity which we might frame as
FundOSS showed us that, on average, users supported ~2.4 projects when they were presented using a cart-like contribution flow (presentation over here). So I think we've enough information to show that this could work. |
Beta Was this translation helpful? Give feedback.
-
|
ok - so I would flip this around: we have a problem with people getting too many notifications and their banks blocking cards because we ping several small transactions at the same time. This is also problematic for companies that need to reconcile each individual transactions. One option is to batch payments on the backend - Another options is to make a cart which has the added bonus that doing it in the front end that makes it easier for people to give more because 1) it makes the contribution flow feel less one-off and 2) is less annoying for people as they only input their information once. |
Beta Was this translation helpful? Give feedback.
This comment has been minimized.
This comment has been minimized.
-
Enable recurring bank transfer contributions #2734Falls under Simplification: making it simple for donors to pay via bank account. It is currently complex because they either need to make a transfer outside the platform or they have to know that they can make a bank account contribution through PayPal (which perhaps we could make more clear). I think it would be great to completely replace the current bank transfer flow with one that lives entirely within the platform. |
Beta Was this translation helpful? Give feedback.
-
|
Recurring bank transfer can take many forms and we would need to nail down what kind of bank transfer integration we want to use. If using Stripe we would have to pick between ACH and SEPA for example. If that works, we can later replicate to the other.
|
Beta Was this translation helpful? Give feedback.
-
Tagging Issues
Some edits that would be very helpful -> based on direct user feedback! |
Beta Was this translation helpful? Give feedback.
-
|
This is also very important for the funder of the OCF Dev and the reporting we need to do. I would add a specific tag about region / state to be able to notice regional / state-specific activity for funders who are looking to support OC and OCF based on the # of collectives in the geographic area named in their mission as grantmakers. |
Beta Was this translation helpful? Give feedback.
-
|
As a collective admin I want to be able to edit the status of other people on my team on my page directly, as I can with the image on my page (for example, to change them from contributor to admin) without going into the settings panel. See this Loom about it |
Beta Was this translation helpful? Give feedback.
-
|
As a collective admin I tried for weeks to double click on the text about my group only to give up and think "I guess I can't change it." I want to be able to edit the text about my group directly, as I can edit the logo and image on my page, in addition to going into the settings panel. See this Loom about it |
Beta Was this translation helpful? Give feedback.
-
|
As a collective admin I want to automatically post about the launch of my OCF - or insert any Hosts name - collective and the money we are raising on Instagram (and possibly TikTok) in addition to Twitter. |
Beta Was this translation helpful? Give feedback.
-
|
As a collective admin I am frustrated when my contributors and community show up at the wrong time to an event because it is shown in the timezone it was created in, rather than the timezone of the person singing up. They view the event on their phone and in an email from another person and don't check the tooltip that corrects the time. As a collective admin I want to create an event and have it displayed in the timezone of the person who is viewing the event. This might be out of scope but is one aspect of simplification has impacts on the OCF homepage which will be usable by all first party hosts as Julian is pulling events into this open source homepage that Memo designed. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Improve eventsLots and lots of events improvements in the backlog and we should consider when the right time to take it on as a project theme might be. |
Beta Was this translation helpful? Give feedback.
-
|
@alanna humble late suggestion post: Onboarding flow follow up
#5195 Collective activity log
#5368 Receipts templates
|
Beta Was this translation helpful? Give feedback.
-
|
+1 on continuing the onboarding project, and trusting the team to come up with the next priority. |
Beta Was this translation helpful? Give feedback.
-
|
Also, I have been scoping a project I would like to do with an external contributor about organizing the different brands we have in our family and setting up some guidelines for their use. I feel this is necessary to ensure the marketing autonomy of our internal hosts and add to the much-needed branding strategy for the long term. It would also not involve any time whatsoever for development. |
Beta Was this translation helpful? Give feedback.
-
|
This is 100% connected to Communication - agreed - related to "people really don't get the difference between the platform and the hosts" https://opencollective.slack.com/archives/G46PNRCGP/p1652430432923949?thread_ts=1652056427.077229&cid=G46PNRCGP This has to do with 4 primary things: |
Beta Was this translation helpful? Give feedback.
-
|
This speaks to our need to have another place/process to discuss non-dev work outside this sprint process |
Beta Was this translation helpful? Give feedback.
-
Enable new PayPal integration for all hosts #4210The project will be scoped next week and we will know how much of an effort it is by then. |
Beta Was this translation helpful? Give feedback.
-
Collective activity log #5195The team worked this sprint on scoping the project. There is some aspects that are ready to be tackled. Mentioned by @Memo-Es there #5511 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
Notes from first discussion:
We've been talking about this for ages, we always put it off, but maybe it's finally time
Makes it so much easier instead of explaining all the steps by email
We have created expenses between hosts and started implementing the contribution side
Probably doesn't need to be prioritized this time |
Beta Was this translation helpful? Give feedback.
-
|
Notes from prioritization meeting: ComplexPage to subscribe or unsubscribe various email notificationsPart of a bigger attention management theme, this could be a starting point that's fairly well-scoped and concrete. Ronan is thinking about the bigger issue OAuthWe're just finishing the first phase. Now what? Do we improve on what we've done? We've done enough for Metagov to start coding already, but not to the level of a production app. Still haven't done: We have some momentum, let's get to a more solid stopping place before dropping it. We always expected it to take 2 sprints. Ideally we won't roll over again to next next sprint. Invite contributionWe have an easy MVP using URL params, but this doesn't take into account the creation of a new profile, like invite expense does, and the main use case is onboarding someone new to the platform. Maybe we can combine the light MVP with URLs plus guest contributions to make it simpler. Needs scoping and design. Receipt templatesWas meant to be worked on this sprint but the scoping hasn't yet been completed - it's still sitting with Memo. It's a bad compliance problem that will cause issues at some point if we don't fix it. Alanna thinks there is a very simple MVP version we can do cheaply. OSC application process updateThis wasn't ranked highly but OSC really wants it. Benjam has scoped the specs in detail and thought a bit about implementation. When OCF did its application update OCF paid for it. But the problem isn't money, it's capacity. Not easy to bring an outside dev in to build it either. We should do some scoping and see if it can be achieved simply or what's possible. A fair amount must be automated due to the volume. Olu can do some of this work, most likely, if it's about updating the form. Need more clarity about the scope before deciding whether it can be a side project for Olu or in the main sprint. MediumCustomizable thank you emailGood way to see what real uptake of template customization will be. We already have a version of this for custom text added to event notifications. The MVP is just a text box added to emails without changing the template itself. Remove noise accountsFrancois can think of a way to tackle it. Might not fit this sprint. We can do it manually to some extent via root admin. Going to be important in a few months but doesn't have to happen this sprint. Having a sandbox mode and automated deletion of inactive accounts will help a lot. Running balanceScoping can happen but can't commit to building it this sprint. It was surprisingly ranked high. Docs for error messagesWe already capture them all in Sentry. We could make a mapping. Non-engineering task. Activity logWe worked on it this sprint, not clear how far we got. Research/specs were done and specs are there. We want to finish design this sprint. |
Beta Was this translation helpful? Give feedback.
-
|
Complex Projects:
Smaller Projects:
Papercuts:
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
This is a great way to visualize it @znarf thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Status for Scoping week
Also someone needs to look at the Sprint checklist. #5626 |
Beta Was this translation helpful? Give feedback.
-
This is the discussion to gather ideas for prioritization of the following sprint: Y22Q2S2. A sprint lasts 6 weeks.
Context
Who should use this discussion
This issue is posted by the facilitator of the upcoming next sprint. Anyone who wants to submit an idea for consideration is welcome to post it here.
How to use this discussion
This is to gather ideas for things to be immediately built. This is not a backlog issue to dump every bug, request, etc. Ideas will be prioritized according to the current strategic priorities.
Strategic Priorities
Format
Think about problems, (not solutions) and the impact of those problems. Consider the following questions:
It's useful to use the following format when trying to reflect this:
Process
We ask submitters to select problems that have both a high degree of impact and a high degree of alignment with the strategic focus areas above, and to briefly explain their reasoning.
The sprint facilitator will consider all ideas, speak to stakeholders, and put forward selected issues for development based on the strategic priorities above.
Beta Was this translation helpful? Give feedback.
All reactions