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

🥔⛰️Neighborhoods #892

Open
1 of 4 tasks
zspencer opened this issue Oct 21, 2022 · 0 comments
Open
1 of 4 tasks

🥔⛰️Neighborhoods #892

zspencer opened this issue Oct 21, 2022 · 0 comments
Labels
⛰️ epic Work we expect will take multiple patches to complete ✨ feature Reduces Client's Burden or Grants them Benefits
Milestone

Comments

@zspencer
Copy link
Member

zspencer commented Oct 21, 2022

Use Cases

Frequently Asked Questions

What kind of Neighborhood are there?

While right now, there is only the Zinc Neighborhood Neighborhoods may specialize in a particular industry, region, or cultural touchpoint. Examples:

  • A regional solidarity economy network's Neighborhood provides fundraising, logistics, and community and donor engagement services to their mutual aid and mutual benefit programs.
  • A Healthcare Cooperative Network maintains a HIPPA compliant Neighborhood and streamlines appointment booking, medical record storage and transfer, and patient communications.
  • A Sci-Fi and Fantasy Writing Club's Neighbohood provides Authors spaces to sell physical and digital editions of their books directly to their fans.
  • A network of artisans hosts a Neighborhood that offers a shared online marketplace with individual sites for each of their members.
  • A University provides a Neighborhood for students and alumni to keep their social media, email and web-hosting.

If you are hosting a Neighborhood, get in touch so we can add you to our list!

@zspencer zspencer added this to the 1.0 - Andromeda milestone Oct 21, 2022
@zspencer zspencer changed the title Feature: Neighborhoods Feature: Neighborhood Feb 26, 2023
@zspencer zspencer added ⛰️ epic Work we expect will take multiple patches to complete 🛠️ infrastructure ci, build, deploy, networking, etc. labels Feb 26, 2023
@zspencer zspencer changed the title Feature: Neighborhood 🌱⛰️Neighborhood Feb 26, 2023
zspencer added a commit that referenced this issue Mar 2, 2023
- #892

This gets rid of the following deprecation warning:

`Calling `DidYouMean::SPELL_CHECKERS.merge!(error_name =>
spell_checker)' has been deprecated. Please call
`DidYouMean.correct_error(error_name, spell_checker)' instead.`
zspencer added a commit that referenced this issue Mar 3, 2023
`Neighborhood`: Update `bundler` gem

- #892

This gets rid of the following deprecation warning:

`Calling `DidYouMean::SPELL_CHECKERS.merge!(error_name =>
spell_checker)' has been deprecated. Please call
`DidYouMean.correct_error(error_name, spell_checker)' instead.`
zspencer added a commit that referenced this issue Mar 17, 2023
- #892

Piikup-Sandbox is experiencing some sadness because of policy issues it
seems.
anaulin pushed a commit that referenced this issue Mar 18, 2023
🧹 `Neighborhood`: Send Authorization errors to Sentry

- #892

Piikup-Sandbox is experiencing some sadness because of policy issues it
seems.
zspencer added a commit that referenced this issue Apr 2, 2023
- #892

When a domain object wants to be routed to via `:resource` vs
`:resources`, there are slightly different shapes to the value we intend
to pass to `polymorphic_path` (or `url_for` or... all the rails url
builders)

In particular, `[:edit, parent, object]` becomes `[:edit, parent,
:object_name]` and `[:new, parent, object]` becomes `[:new, parent,
:object_name]`, `show` and `update` and `destroy` actions remain
`[parent, object]` however!

Co-authored-by: Dicko Sow <[email protected]>
zspencer added a commit that referenced this issue Apr 3, 2023
- #892

When a domain object wants to be routed to via `:resource` vs
`:resources`, there are slightly different shapes to the value we intend
to pass to `polymorphic_path` (or `url_for` or... all the rails url
builders)

In particular, `[:edit, parent, object]` becomes `[:edit, parent,
:object_name]` and `[:new, parent, object]` becomes `[:new, parent,
:object_name]`, `show` and `update` and `destroy` actions remain
`[parent, object]` however!

Co-authored-by: Dicko Sow <[email protected]>
zspencer added a commit that referenced this issue Apr 3, 2023
- #892

When a domain object wants to be routed to via `:resource` vs
`:resources`, there are slightly different shapes to the value we intend
to pass to `polymorphic_path` (or `url_for` or... all the rails url
builders)

In particular, `[:edit, parent, object]` becomes `[:edit, parent,
:object_name]` and `[:new, parent, object]` becomes `[:new, parent,
:object_name]`, `show` and `update` and `destroy` actions remain
`[parent, object]` however!

Co-authored-by: Dicko Sow <[email protected]>
zspencer added a commit that referenced this issue Apr 6, 2023
- #892

We have some sad background jobs in the queue, this will let me purge
the heretics.

Co-authored-by: Kelly Hong <[email protected]>
zspencer added a commit that referenced this issue Apr 6, 2023
* 🛠️ `Neighborhood`: Expose `sidekiq-web` ui to Operators

- #892

We have some sad background jobs in the queue, this will let me purge
the heretics.

Co-authored-by: Kelly Hong <[email protected]>

* `Neighborhood`: Write some tests for the costraint

Co-authored-by: Kelly Hong <[email protected]>

---------

Co-authored-by: Kelly Hong <[email protected]>
zspencer added a commit that referenced this issue Apr 10, 2023
- #892

Surprised there weren't any errors, but I'll take it!
zspencer added a commit that referenced this issue Apr 10, 2023
…1339)

- #892

Surprised there weren't any errors, but I'll take it!
zspencer added a commit that referenced this issue Apr 13, 2023
- #892

This threw off a contributor recently 🙃
anaulin pushed a commit that referenced this issue Apr 13, 2023
📝 `Neighborhood`: Don't reference PostgreSQL 12 specifically

- #892

This threw off a contributor recently 🙃
zspencer added a commit that referenced this issue Apr 26, 2023
- #892

While ideally we would have a matrix of supported rubies in CI so
Contributors and Operators can run whatever Ruby they want; that's not
where we are yet.

So this bumps the `main` branch to 3.2.2; the most up-to-date
"Matz Ruby Implementation" (mri) Ruby.
zspencer added a commit that referenced this issue Apr 26, 2023
- #892

While ideally we would have a matrix of supported rubies in CI so
Contributors and Operators can run whatever Ruby they want; that's not
where we are yet.

So this bumps the `main` branch to 3.2.2; the most up-to-date
"Matz Ruby Implementation" (mri) Ruby.
zspencer added a commit that referenced this issue May 7, 2023
- #892

I normally just write these every time, but eh maybe someone else will
benefit from me putting them in here.

I've also seen a really lovely `make`-a-like written in Rust that the
former CTO of NPM seems to like; but I can't remember it's name 🙃.
@zspencer zspencer changed the title 🌱⛰️Neighborhoods 🥔⛰️Neighborhoods May 18, 2023
zspencer added a commit that referenced this issue May 27, 2023
- #892
- #74

I noticed that the `Convene` link in the footer was always to the
current `root_url`, which will be the `Space` when visiting the `Space`
via a `Domain`.

This shifts it to use the `APP_ROOT_URL`, and allows `Operator`s to
configure the Neighborhood name and Tagline.
zspencer added a commit that referenced this issue May 27, 2023
- #892
- #74

I noticed that the `Convene` link in the footer was always to the
current `root_url`, which will be the `Space` when visiting the `Space`
via a `Domain`.

This shifts it to use the `APP_ROOT_URL`, and allows `Operator`s to
configure the Neighborhood name and Tagline.
zspencer added a commit that referenced this issue May 27, 2023
- #892
- #74

I noticed that the `Convene` link in the footer was always to the
current `root_url`, which will be the `Space` when visiting the `Space`
via a `Domain`.

This shifts it to use the `APP_ROOT_URL`, and allows `Operator`s to
configure the Neighborhood name and Tagline.
zspencer added a commit that referenced this issue Jun 1, 2023
- #892
- #74

I noticed that the `Convene` link in the footer was always to the
current `root_url`, which will be the `Space` when visiting the `Space`
via a `Domain`.

This shifts it to use the `APP_ROOT_URL`, and allows `Operator`s to
configure the Neighborhood name and Tagline.
zspencer added a commit that referenced this issue Jun 1, 2023
- #892
- #74

I noticed that the `Convene` link in the footer was always to the
current `root_url`, which will be the `Space` when visiting the `Space`
via a `Domain`.

This shifts it to use the `APP_ROOT_URL`, and allows `Operator`s to
configure the Neighborhood name and Tagline.
zspencer added a commit that referenced this issue Jun 25, 2023
- #892

We used this early on to provide a degree of feature flagging; but we
haven't used it lately and we will probably want to rely on `flippa` or
something more fully featured and better maintained as we mature.
zspencer added a commit that referenced this issue Jun 25, 2023
`Neighborhood`: Get rid of unused `Feature` model

- #892

We used this early on to provide a degree of feature flagging; but we
haven't used it lately and we will probably want to rely on `flippa` or
something more fully featured and better maintained as we mature.
zspencer added a commit that referenced this issue Jun 25, 2023
zspencer added a commit that referenced this issue Jun 25, 2023
zspencer added a commit that referenced this issue Jun 25, 2023
zspencer added a commit that referenced this issue Oct 10, 2023
- #892

Per https://github.com/nodejs/release#release-schedule, Node 16 is
decommissioned! This bumps us to the newest LTS, Node 18! Hooray!

Make sure to delete your `node_modules` folder, since I have no idea how
any of this works but I expect that keeping old node modules around is
bad-idea-jeans.
zspencer added a commit that referenced this issue Oct 11, 2023
- #892

Per https://github.com/nodejs/release#release-schedule, Node 16 is
decommissioned! This bumps us to the newest LTS, Node 18! Hooray!

Make sure to delete your `node_modules` folder, since I have no idea how
any of this works but I expect that keeping old node modules around is
bad-idea-jeans.
zspencer added a commit that referenced this issue Oct 11, 2023
- #892

Per https://github.com/nodejs/release#release-schedule, Node 16 is
decommissioned! This bumps us to the newest LTS, Node 18! Hooray!

Make sure to delete your `node_modules` folder, since I have no idea how
any of this works but I expect that keeping old node modules around is
bad-idea-jeans.
rosschapman pushed a commit that referenced this issue Oct 23, 2023
- #892

Per https://github.com/nodejs/release#release-schedule, Node 16 is
decommissioned! This bumps us to the newest LTS, Node 18! Hooray!

Make sure to delete your `node_modules` folder, since I have no idea how
any of this works but I expect that keeping old node modules around is
bad-idea-jeans.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⛰️ epic Work we expect will take multiple patches to complete ✨ feature Reduces Client's Burden or Grants them Benefits
Projects
None yet
Development

No branches or pull requests

1 participant