This engine and included bots allow you to build bots to play Loot - a card game: http://www.amazon.com/Gamewright-231-Loot/dp/B0009XBY30
webhook is a lightweight configurable tool written in Go, that allows you to easily create HTTP endpoints (hooks) on your server, which you can use to execute configured commands.
Bitcoin Core integration/staging tree
Bitcoin peers.dat reader in python
simple, flexible, fun javascript test framework for node.js & the browser
asood123/open-source-sponsors 0
A list of companies that sponsor open source software
:scream: Modern static* website generator based on the React and Webpack ecosystem :sparkles:
asood123/react-native-image-crop-picker 0
iOS/Android image picker with support for camera, configurable compression, multiple images and cropping
issue openedopencollective/opencollective
Force standalone page toggle not sticking
I created a standalone tier by switching on the toggle.
But when I go back to edit/tiers the toggle shows as turned off. It's not though, because the standalone page is still active. The toggle should stick with the saved setting.
created time in a minute
issue commentopencollective/opencollective
2FA: ability to turn off 2FA if you don't want it for login anymore
@sbinlondon Yes, it sounds good.
comment created time in 2 hours
issue commentopencollective/opencollective
Consensus on naming and behaviour of sections and subsections in the Collective page
Agree about the navigation consistency. The proposal described above is meant to be consistent on all Collective's instances, from the Collective page and all of its possible sub-pages.
So if you click on any of the 'Section Categories' like 'Budget,' it will take you to the Collective page, down to the 'Budget' section on both desktop/mobile, and only 'Expandable sections' using @sbinlondon term will be displayed in a dropdown.
One thing also I want to surface is @alanna 's comment about the 'Goals' feature:
Don’t combine goals and budget - some people need to put the goals progress bar right at the top and want the budget stuff elsewhere. Basically, I think we should split up things to customize, reorder, and hide/show what they want more flexibly.
I don't think we should make 'Goals' a section of its own. These types of small decisions generated a lot of complexity in the current Collective Navigation, which was one of the main points of the design need for this update. Anyway, I wonder if that could be a widget integrated to the top part of the Collective page. @Betree, any thoughts on this?
(Also, we should also remember that we brought back this feature after a couple of negative reactions from users, so if we want to keep it, we should rethink how it plays out with the new stuff that we are planning for the near future. I decided to put it under budget because it will also be featured in the new 'Transparency' page for Collectives for sure.
comment created time in 3 hours
push eventopencollective/opencollective-frontend
commit sha fa839d3fe0619b263c6454191a4a637ee466e895
refactor: migrate index.js to styled components Related to https://github.com/opencollective/opencollective/issues/3289
commit sha e1263f59d2ee4e95f9705ab66ebeda0602209737
feat: allow user to filter search results
commit sha e5d565297a0a6147cbad7c7c1e4d34c69f05c304
chore: improve internationalization Co-authored-by: Benjamin Piouffle <[email protected]>
commit sha 872a25ee3a385403c484231d96d991ac58fcfaba
feat(HostDashboard): New orders tab
commit sha 92501f84135145d536f4cba3af47231eb03d02f0
enhancement(Orders): Update page to new design
commit sha 4cb2943ab13adce4a4051a222bf8578cbbdb27fc
fix(ContributionFlow): Fix prepaid host limit
commit sha 3b1c5e6f733097b8b3987e777d52089b9fa9b073
test(E2E): Update dashboard orders test
commit sha 066069a520ae48baafcabf2c5f8cacf223d02e13
fix: wrong value on success page
commit sha 4b5dd4907a68ddde9c6550cca6adbe918097425d
enhancement(DashboardOrders): Rename to Pending bank transfers
commit sha ef5956929c155ac17ff19a68fbfeba3ea6344db7
refact: Rename processOrder to processPendingOrder
commit sha 8cc8993800c4b23841d870a91ef0ad1a2eb19e93
chore: update schemas
commit sha d1de567eaf61516cbefbd314f9a85918c60e581e
fix: fetch platformContributionAvailable from organizations too
commit sha 11174e07e8cf4f1521683efe63d288dc7cb98707
refact: remove unused conditional We are now selecting the donation value before picking the profile, so this would always be false
commit sha a3d3e6837d0ac9e25b4b5e778d292836e5047ecc
fix: do not reload legacy keys from cached expense drafts
commit sha 1bf6c7942ecf366a2f4645b2fc1b698cee8013db
Merge pull request #5428 from opencollective/fix/host-donation-platform-tips Fix: Display Platform tips when donating to Self-Hosted Organizations
commit sha 9ddadfb691c0da1c49398d336a4fe7f8590ccd19
chore(deps): bump polished from 4.0.3 to 4.0.4 Bumps [polished](https://github.com/styled-components/polished) from 4.0.3 to 4.0.4. - [Release notes](https://github.com/styled-components/polished/releases) - [Commits](https://github.com/styled-components/polished/compare/v4.0.3...v4.0.4) Signed-off-by: dependabot-preview[bot] <[email protected]>
commit sha 52392db85e0be93a613ddc57c914881288ac2887
Merge pull request #5449 from opencollective/fix/prepaid-host-limit ContributionFlow: Fix prepaid host limit
commit sha 4df30b6ce08e84d939cdf5473dde189bd8221d50
Merge pull request #5424 from opencollective/feat/dashboard-orders HostDashboard: New "pending bank transfers" tab
commit sha 845c88ad60987cdae79466716f59a20c628f29cc
Merge pull request #5367 from opencollective/migrate-index-to-styled-components Migrate editCollective/index.js to styled components
commit sha b2e204bc6a44d62f23e40c425a465555424e4ed2
fix(Policies): Update frontend char count to match API allowed char count (#5440)
push time in 3 hours
pull request commentopencollective/opencollective-frontend
Enable Brazilian Portuguese as language
Your Render PR Server URL is https://oc-styleguide-pr-5462.onrender.com.
Follow its progress at https://dashboard.render.com/static/srv-buuknvgti7j96vj4fac0.
comment created time in 3 hours
pull request commentopencollective/opencollective-frontend
Enable Brazilian Portuguese as language
This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.
🔍 Inspect: https://vercel.com/opencollective/opencollective-frontend/kt96kqpc5
✅ Preview: In Progress
comment created time in 3 hours
PR opened opencollective/opencollective-frontend
As requested by Casa Hacker, I forked Brazilian Portuguese from the existing Portuguese translation.
pr created time in 3 hours
create barnchopencollective/opencollective-frontend
created branch time in 3 hours
issue commentopencollective/opencollective
2FA: ability to turn off 2FA if you don't want it for login anymore
@znarf Does this implementation sound ok to you?
comment created time in 3 hours
issue commentopencollective/opencollective
Consensus on naming and behaviour of sections and subsections in the Collective page
Another outstanding question is how much control do we give users over their profile page? Can they reorder/hide entire categories on the page, but not the sections within them? Can they reorder/hide both categories and sections within categories?
That will be the most complex part, especially because we'll need to migrate the existing
sectionsto a new format like:sections = [ ABOUT: [ { section: ABOUT, isEnabled: true }, ], BUDGET: [ { section: TRANSACTIONS, isEnabled: true }, { section: EXPENSES, isEnabled: true }, ] ]
This is fine by me. I want extra extra clarity though:
- This
sectionsarray is the one insettings.collectivePageright? - Does the
isEnabledon a section in thesettings.collectivePage.sectionsarray ONLY pertain to whether that section is visible/not visible on the collective page? settings.collectivePage.sections[section].isEnabledis different tosettings.features[feature].enabled? What happens if we havesettings { features { conversations: false } }because the collective has opted out of having conversations but
settings {
collectivePage: {
sectionCategories: {[
CONNECT: [
{ section: CONVERSATIONS, isEnabled: true },
]
]}
}
}
wouldn't have an effect because we're opting out of the feature? Or would we have logic on the API side to say when we opt out of conversations via settings.features.conversations it also sets the bit in settings.collectivePage.sectionCategories... to false? Or maybe vice versa where if they hide conversations from their collective page in this proposed menu below, that is effectively seen as opting out of the feature?
To me we should be able to re-order section categories (ABOUT, BUDGET, etc) and sections inside of them. But you can't get a section out of it's Section category.
Translated to UI:
That's pretty much what I was imagining for the edit profile page menu, thank you for visualising! 🙌
I agree with @kewitz that navigation should be consistent wherever it's used. We don't mutate the top bar profile menu's design or functionality across pages, and I feel we should try our best to keep a similar consistency with the collective navigation.
comment created time in 3 hours
pull request commentopencollective/opencollective-frontend
Migrate Form.js to styled components
@Betree : Thanks for pointing that out. I've corrected that. Let me know if you see anything else. 👍🏽
comment created time in 4 hours
push eventopencollective/opencollective-frontend
commit sha fa839d3fe0619b263c6454191a4a637ee466e895
refactor: migrate index.js to styled components Related to https://github.com/opencollective/opencollective/issues/3289
commit sha 482b13682d0d1d0aab64b841516742dc536cf451
enhancement(ContributionFlow/Progress): Emails/profile info truncation
commit sha e3cab0a2de6dc9149c8a171e6eb19990c5d236e5
refactor: migrate createUpdate.js to styled components Related to https://github.com/opencollective/opencollective/issues/3289
commit sha 4cc00febb3345c5db5ad7d35b78229f0d3d50c64
refactor: migrate HostsWithData.js to styled components Related to https://github.com/opencollective/opencollective/issues/3289
commit sha f6936cc31cd8797098b3a5a6a2c3d8db64fb9034
refactor: migrate Response.js and Responses.js to styled components Related to https://github.com/opencollective/opencollective/issues/3289
commit sha 01bc22dbfa91c6c37dcd6e1c00f18900582f0122
fix: flashing state when opening draft invitation
commit sha 696ee9db5fc3afacb086c67b9960056706c14804
fix: undefined slug when editing draft
commit sha b94344b3ba2880ccf96e2730f37a00e2f701ad50
fix: wrong payee details in the expense summary
commit sha e35545cd793cf64b72723742846ce407bacdf124
feat(Dashboard/PendingApplications): Move to new design
commit sha 59d84abebeeb82e85e887aeeccca8432258a3262
fix: draft page SSR state
commit sha e764cc7dd35ce457929b58971be6fee6c5c1ba91
display name and not slug on expenses
commit sha 0fae839eca9bafc3d770fce2061a9c534da13eb3
enhancement(StepsPogress): Apply latest design
commit sha 6a77d476bd64e76f8e6120170dbef65ab2b1f429
fix: expense validation without draftKey
commit sha 83fa15134123e85dfacefcca17b16f9303502ea3
refact: use requestByAccount
commit sha 738d18c1f6c8eaa8f390f1cad9c2c150fda4df17
fix: expense page loading and SSR state
commit sha 5708a2cdfc34c542717c119f19256fcc62ba8b82
fix: design tweaks and copywrite
commit sha 5cbbb587d2305d2424f7fa2fde5516c9c92cb12a
chore: update langs
commit sha a26d4f3fff22245f3ff56f676359c233400824f2
chore(deps): bump @sentry/browser from 5.27.3 to 5.27.4 Bumps [@sentry/browser](https://github.com/getsentry/sentry-javascript) from 5.27.3 to 5.27.4. - [Release notes](https://github.com/getsentry/sentry-javascript/releases) - [Changelog](https://github.com/getsentry/sentry-javascript/blob/master/CHANGELOG.md) - [Commits](https://github.com/getsentry/sentry-javascript/compare/5.27.3...5.27.4) Signed-off-by: dependabot-preview[bot] <[email protected]>
commit sha 95ea60ab2ca32334b46699b0a0f5df6279dd9a58
Merge pull request #5397 from opencollective/enhancement/cf-progress ContributionFlow steps progress design enhancements
commit sha 58dfbae8ab02b78ae0edf748350829675fb5556a
Merge pull request #5408 from opencollective/dependabot/npm_and_yarn/sentry/browser-5.27.4 chore(deps): bump @sentry/browser from 5.27.3 to 5.27.4
push time in 4 hours
push eventopencollective/opencollective-frontend
commit sha dbf339dc9a4ca6970c55573e66e8b07bc59a4ffc
update pricing
push time in 4 hours
push eventopencollective/opencollective-frontend
commit sha 2c261e544c7bbb76da192f8beb0706d01b3c40f9
i18n(Japanese): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha e24f5a25ac4003c9e246ea0ec0d939b33ddda91b
i18n(Italian): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha b56ac30062b6f96da1993e6d32eb422785513006
i18n(Hungarian): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha 7f1bf596d0901960423d3c04f0126a2162b590ad
i18n(German): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha 3a7b0eb89f4eebfa0727beabc8635a9198d69452
i18n(Korean): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha f92f531320fcfa73c22663d29342c9b9ca95480e
i18n(Czech): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha ae7703a5786919955c4d71180b8c0b2dc8527bf1
i18n(Catalan): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha 5cf6a63f3542be2d0ecf02a4f3189dd934b533ce
i18n(Arabic): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha 48ca34f4ca677b02f290ec052930375728c06dc1
i18n(Spanish): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha 16136e993089ccf8b47bb1e83571d92e979afcb6
i18n(Dutch): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha c9ab2b7695557e4d9a85be1a7ed1a3bb329cae98
i18n(Swedish): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha 81199d3ef55bd5f44672183887215d01d079a549
i18n(Welsh): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha a868909606fe8eacc1b10f5da8369a1b3f9a5397
i18n(Persian): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha 6a15e9d5e15139edec595c9da92fc4c153c64939
i18n(Chinese Simplified): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha 19689c4fa0fab32d423cca9c684fb5bdf1b73e38
i18n(Turkish): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha a696d98a4605d7f31f17ea278f3b4ed638eccd20
i18n(Russian): update en.json
push time in 5 hours
push eventopencollective/opencollective-frontend
commit sha be09ef0918421c9b00f2484ec06c0fdd256f7414
i18n(Portuguese): update en.json
push time in 5 hours