We need to organize: about tgame

[calebjpicker]

Yeah. I'm thinking that we each have our own separate develop branches that we merge into a main develop branch or simply just merge into a master branch.

[calebjpicker]

1. Have our own separate branches that we then merge to a main branch (probably master).
2. Each issue should be an actionable item that moves us closer toward achieving a milestone. I personally think we should also take the time to think about what milestones are needed to achieve a project. That way we will have a structure within which to easily add and organize new issues.
3. One solution is to have a Project Manager (like Jordan). The Project Manager is in charge of organizing, assigning tasks, and ensuring that we make steady progress.
4. I'm not quite sure what you mean by interface. If you mean the GUI we use, then we seem to be using a combination of the Project Template and just opening issues as they come to mind. I think this will be easier if we have clearly defined milestones for each project.
5. This could be the Project Manager.
6. We need to decide on and create a proper folder structure within git. If there are some standards, we could look into that.
7. The Project Manager could do this.

We can each manage some of the Projects we've defined in the Project tab. So I might take 2-3 and you might take 2-3.

[MElemental]

#23 (comment)

[MElemental]

* [ ]  how we make modifications

This is our discussion on branches and pull requests

* [ ]  how come up with issues

Maybe we should make issues based on main issues with checklists this, with an issues for each item that ends up being bigger, we also have to decide when it's more appropriate for a project board.
Perhaps this point can be it's own issue, and we can close this issue, perhaps I should have kept this as a note, then made an issue for each topic.

* [ ]  how we assign tasks

This one I think its simple, or comes later down the road.

* [ ]  the interface we use for workflow

I wonder if this is just this issue said differently, maybe we should remove it.

* [ ]  how we assign people to milestones or modules

let's group this with the other assignment issue.

* [ ]  how we upload files

I have a few methods in mind, but perhaps we should get our file structure down first.

* [ ]  how often we go through github and organize it.

I think daily is a bit much for us right now. Let's do our monday plan and possibly our wednesday plan.

[calebjpicker]

For the future, I think a lot of these to do items already exist in other issues. And for those that don't, we should create separate issues. Otherwise, it will be difficult to track.

[MElemental]

I think we should link issues to a note in the projects or we could reference sub issues in an issue that lists things like this. Then we pin the big issues.

[calebjpicker]

I think we should link issues to a note in the projects or we could reference sub issues in an issue that lists things like this. Then we pin the big issues.

As I stated up there, I think it would be better to create milestones that are each associated with a project. Then, assign the issues to those milestones so they are all linked together.

[MElemental]

Good point,
I probably has some trouble imagining if we had a similar structure in place.

[MElemental]

I mostly converted a note you put on the Repository workflow board.

[calebjpicker]

Can we close this issue, given that these issues are mostly captured by other issues in the Repository Workflow project?

[MElemental]

yeah