What is a collaborators role in your project?

[ghost]

As a collaborator, I am happy to join development of this exciting project.

As a collaborator, what is expected of me? How can I chip in without being an annoyance?

For me specifically, I would be interested in any of the 4 following activities:

• Reviewing commits, flagging potential issues
  • Performance
  • Maintainability
  • Readability
  • Bad practices
  • Risks feeling nagged?
• Cleaning up, make code read like a prose
  • Provide practical reason
  • Small pull requests
  • Avoid merge conflicts
  • Risks feeling pointless effort?
• Work toward completing open issues
  • Implement a simple solution to any issue
  • Submit pull request
  • Avoid merge conflicts
  • Risks feeling lost ownership?
• Unit and integration tests (Unity Test Tools)
  • Explore testing for games
  • Past experience: Inherently hard
  • What causes it to be hard?
  • How to make it easier?
  • What practical value gained from it?
  • Start with high risk areas
  • Basis for bug-fixes
  • Screen wrapping?
  • Could start in separate branch to test waters
  • Risks feeling slogged down?
  • Risks feeling too much information?
  • Risks feeling too much for small project?

What do you feel? If you feel any of the points above is redundant, let's drop them. The secondary bullet points are examples of things to consider - not hard rules. The point is to get something going which we both feel provide some value for the time spent. Also, no hard feelings if you want to try something out, later find out it's a nightmare to collab and want to cancel it. I want you to always feel you are in control, so please speak your frank mind.

Do you have other suggestions? What would you feel would be fun to do together?

[antfarmar]

How can I chip in without being an annoyance?

Don't worry about this. Feel free to speak your mind when and where you want. I'm easy.

You clearly have more experience with Unity\design\C# than I do, so I appreciate your feedback. This project just started out as a little experiment with no real expectations or firm end goal, so I'm figuring it out as I go along too. I'm just trying to document it all as it progresses.

But as I've said before, my original intention was to get a base playable game (with no real design), then constantly refactor it into different branches, each strictly focused on a specific design pattern (e.g. UnityEvents messaging). So ultimately there would be the exact same game on different branches, but each would be implemented differently, as it uses a different pattern implementation.

We'll see.