Vega-strike-engine-source: Community Structure

Created on 4 Apr 2020  路  10Comments  路  Source: vegastrike/Vega-Strike-Engine-Source

From https://github.com/vegastrike/Vega-Strike-Engine-Source/pull/33#issuecomment-609089044:

Please do that. Also, please ask @Loki1950 to add you as a contributor. I don't know your background but you seem to know your stuff. I'm going to open two issues: 1. Project History 2. Current team status. From my talk with Loki, the older generation of programmers has moved on. Loki's been around for ages but he's not a C++ dev. It might be a good idea to start talking about where we want to take this project and how we want to do it. My vote is for Loki to be the project leader/mediator.

There has been a large turn over of the devs. We need to decide who makes the decisions, who gets what authority, etc to help progress things forward.

Most helpful comment

We need to decide who makes the decisions, who gets what authority, etc to help progress things forward.

I reckon it's pretty straight forward: whoever is around and takes up a task will have the authority to participate in decisions and move things forward (as in 'the true spirit of responsible open community'). Have fun at that ;-)

All 10 comments

I am presently helping to manage the stuff in Github at least from a project management view with the Project Board, issues, etc.

I've got a long history of software development in Python and C/C++ too; but relatively new to the game dev space. Willing to help out however needed.

Created the @vegastrike/core-reviewers team. I'm on it at least for now since I set it up. Feel free to remove me or say I'm official.

We need to decide who makes the decisions, who gets what authority, etc to help progress things forward.

I reckon it's pretty straight forward: whoever is around and takes up a task will have the authority to participate in decisions and move things forward (as in 'the true spirit of responsible open community'). Have fun at that ;-)

I agree with @pyramid3d's statement.
Additionally, following @danielrh's decision and @Loki1950's announcement:

  • Loki is the Project Lead
  • @BenjamenMeyer is the Lead Developer

With that, I think we can close this issue

@nabaco before we close this we need to update permissions in the org to reflect the decision.

I think @Loki1950 can help with that

Help with the github web interface would be appreciated it can be a bit tedious

@BenjamenMeyer We have figured it out with @Loki1950. You should have full access now.
If any further changes are needed, you can do them by yourself.

I guess we can close this issue now

permissions confirmed. Closing

Was this page helpful?
0 / 5 - 0 ratings

Related issues

nabaco picture nabaco  路  4Comments

LifWirser picture LifWirser  路  6Comments

nabaco picture nabaco  路  4Comments

viktorradnai picture viktorradnai  路  3Comments

stephengtuggy picture stephengtuggy  路  5Comments