Skip to content

Improved project structure proposal #5

Description

@WillTheDeveloper

I think the project needs improved management and structure. Developers all have different ideas and varying scopes which can and will cause conflicts between development processes and functionality that is being implemented.

There is obviously different ways to approach this so I am open to tweaks and adjustments but as we have all learnt with past projects, if there is no structure then it just falls apart and everyone does there own thing.

Some of the points I think should be addressed include:

  • Everyone should not have admin rights to the repository. The evidence to support this is on the actual rect lang repository where not everyone has it and changes are done is a structured way through PRs hence why that project has done well and actually got things done properly.
  • Should create an outline scope for the entire project and use projects or something to assign tasks accordingly along with target version numbers.
  • Have dedicated people for certain things, even if this is just one person or the owner to review or be the one who does the PR flow.
  • Require reviews for pull requests if we take the PR route for future changes.
  • Suggest features like any other repository would do, using a issue or PR.

This project just needs some structure if its going to go anywhere. Like, lets actually put our heads together and make something pretty cool, otherwise just f*ck off :)

Please state your thoughts and stuff below using comments. Lets use github the developer way and stop crying on each others shoulders in discord.

<3

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

questionFurther information is requested

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions