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

Rename this repo to "community-lounge" #36

Closed
mindthegab opened this issue Apr 28, 2020 · 5 comments
Closed

Rename this repo to "community-lounge" #36

mindthegab opened this issue Apr 28, 2020 · 5 comments
Assignees

Comments

@mindthegab
Copy link
Member

Once we are done with #31 (definitely NOT before), I would like to consider renaming this org into finos-projects and keeping it on using for meta/cross-project collaboration with all project leads.

@mcleo-d @maoo @toshaellison @brooklynrob @maoo:

can you give me a 👍 or 👎 (or elaborate if you really think this warrants a convo, seems pretty straightforward to me)

@mindthegab mindthegab self-assigned this Apr 28, 2020
@toshaellison
Copy link
Member

👍

@maoo
Copy link
Member

maoo commented Apr 29, 2020

👎

IMHO the name should be project-* or projects-*, given that any finos-* name would be redundant on github.com/finos/finos-*

I'd also like to point out that this repository COULD also serve as the host for project landscape (WIP), see https://github.com/finos/finos-landscape

Maybe something like project-discussions or project-commons, or something along those lines.

@mindthegab
Copy link
Member Author

@maoo Agreed on not duplicating finos.

Given this repo scope could be for:

  • Governance discussions
  • Just general discussions
  • Issues that the community might have raise (at a certain point we could move out of help @ Jira in favor of github)
  • host the landscape and common resources (we could move branding and project logos here as well)
  • a place to publicly add/interact/collaborate with at least all the project leads (force add) and more contributors (opt-in)

How about we call it "community-lounge"? So we give it also a bit lighter feeling and we multi-purpose it?

@toshaellison @brooklynrob @mcleo-d @maoo

@mindthegab mindthegab changed the title Rename this repo to "finos-projects" Rename this repo to "community-lounge" May 21, 2020
@mindthegab
Copy link
Member Author

@mcleo-d @brooklynrob @toshaellison before I move on with this change, I wanted to quickly chat with you, so I'll bring it up at the next Tech leadership meeting.

To be clear, this is something different than the "labs" idea from @mcleo-d, in case anyone had doubts.

What I'm envisioning is that, incrementally, not big bang, we could move into this new repo:

  • Governance / RFC discussions / Just general discussions with the Community
  • Issues that the community might have raised (at a certain point we could move out of help @ Jira in favor of github)
  • host the landscape and common resources (we could move branding and project logos here as well)
  • a place to publicly add/interact/collaborate on governancewith at least all the project leads (force add) and more contributors (opt-in)
  • potentially even the "governance" related wiki itself, into a microsite community.finos.org

So maybe the right name for this repo is simply "community". Let's discuss at tech leadership.

mindthegab added a commit that referenced this issue Jun 4, 2020
Per #36 start focusing this space on Community and Project Leads collaboration.
@mindthegab
Copy link
Member Author

Per this conversation, I have renamed this space to "Community" and I think it should be considered a good place to start consolidating Project Leads level collaboration, Community RFC, our pan-project governance (/cc @copiesofcopies especially if we want to continue moving out of wiki), even community discussions (/cc @maoo @mcleo-d e.g. if we want to enable github discussions). I'll bring it up at tech leadership.

/cc @toshaellison all backlinks should work as github handles redirect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants