Visitar URL original
Move ViewComponent to its own org · Issue #1424 · ViewComponent/view_component · GitHub
Skip to content

Move ViewComponent to its own org #1424

Closed

Description

@joelhawksley

I’d like to propose that we move ViewComponent to its own organization, viewcomponent for the following reasons:

  1. So that ViewComponent’s identity can grow beyond the scope of just being a GitHub project. ViewComponent has > 165 contributors from across the industry, not just GitHub employees.
  2. So that we can formally extend ownership of the project to non-GitHub members of the community. This is currently not allowed under our organization policies.
  3. Allow for other repos to be added to the project. For example, I’d be interested in moving VC::Form, Lookbook, demo repo and others into this proposed org.

What do y’all think?

Activity

  1. finalburn commented on Jul 20, 2022

    @finalburn
    Collaborator

    All for it! I suppose it does beg the question of whether the gem gets renamed to viewcomponent too, but I think that's something we'd need to do with a major release... It's worth thinking through the consequences for developers there.

    Part of me wonders if there'd be a way to have Dependabot pick up on the rename. That'd give it a good signal boost.

  2. added a commit that references this issue on Aug 25, 2022
    f9d6c59
  3. added a commit that references this issue on Aug 31, 2022
    92a0f39
  4. finalburn commented on Jan 18, 2023

    @finalburn
    Collaborator

    I suppose it does beg the question of whether the gem gets renamed to viewcomponent too, but I think that's something we'd need to do with a major release...

    Was this idea dropped, or is it still something we plan to do for v3?

  5. joelhawksley commented on Jan 18, 2023

    @joelhawksley
    MemberAuthor

    @boardfish I haven't given it any further thought. What do you think?

  6. finalburn commented on Jan 18, 2023

    @finalburn
    Collaborator

    I guess there are two sides to it – from the perspective of it not being the same as the org name, it's unintuitive. But from the perspective of it being the snake-case form of the constant name, much like active_support, for example, it is. There's also the fear that anyone using ViewComponent more passively might miss updates through Dependabot for a good while.

    I feel like there might've been something else swaying me towards the idea at the time, but I think on the above basis, it seems sound to drop it.

  7. Spone commented on Jan 18, 2023

    @Spone
    Collaborator

    I agree, let's stick with view_component 👍

  8. added a commit that references this issue on Dec 22, 2023
    d55a6da
  9. added a commit that references this issue on Jan 3, 2024
    97021b9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions