search

RITlug / tasks

Real-life issue tracker for tasks, goals, and objectives for RITlug
https://ritlug.com
Creative Commons Attribution Share Alike 4.0 International
6 stars 1 forks source link

Look at moving all infrastructure-related issues to RITlug/Infrastructure #94

Closed Tjzabel closed 5 years ago

Tjzabel commented 5 years ago

It may be a good idea to look at consolidating all issues related to the RITlug infrastructure to the RITlug Infrastructure repository.

That way, we can get good use out of the repo, and all infra-related issues can be hosted in one central location.

jrtechs commented 5 years ago

@Tjzabel Do you want to migrate all current infrastructure related issues out of tasks and into the infrastructure repository?

jwflory commented 5 years ago

Tickets that do not require the direct participation of eboard members (e.g. things more about day-to-day operations, scheduling DC visits, etc.) make sense to split out into their own repo. We should discern the infrastructure tickets that do require full eboard engagement and participation from the ones that don't.

This way, eboard can focus on the tasks that demand our shared attention, and the infrastructure-related tasks can keep plugging along at their own pace. This also encourages more participation by club members in our infrastructure, especially if the idea of an infrastructure SIG comes together.

For example, a ticket like "Run a NextCloud server for club members" is a good example of an eboard task, while "Configure default user settings for NextCloud" is a better example of an infrastructure task.

Tjzabel commented 5 years ago

@jrtechs I agree with what @jwflory said. Infra-specific tasks would be great to migrate over. Tasks that involve eboard participation should stay in the tasks repo.

This would allow infra-related issues to move at their own pace, and gives them a place to be congregated.

ct-martin commented 5 years ago

If you move tickets I would appreciate if you copied over the history as I've left notes in some of the issues. Otherwise, do as you wish I guess. Please tag me on any issues I should be tagged on in the new repo so I get the emails

Tjzabel commented 5 years ago

@ct-martin this isn't a "do as you wish" sort of thing. The Infrastructure repo will host other things not related to current infra tickets as well. If you would like, we can move future infrastructure tickets to the repo if you would like to keep the current history.

jwflory commented 5 years ago

On a side note, if we do want to migrate existing tickets later, this feature was introduced a month or two back if you noticed it in the sidebar of issues:

Transfer a GitHub issue to another repository

I've transferred issues across repos elsewhere and it worked well for a beta feature. This bridge can be crossed once it arrives. :slightly_smiling_face:

ct-martin commented 5 years ago

I transferred a bunch of issues to the infra repo and re-added the meta-issues on the ops project board.

Note for future reference: if you transfer issues, the labels, project boards, milestones, & references to the issue (such as #xx) get broken.