As the Diversity Team begins to move forward with reaching our goals, having the right tooling for meeting our needs and being available to the greater community will be important. We also need ways to keep track of items on our agenda for our meetings and other important tasks.
In the past few hours, a few things have been created to help us get started. These include:
Normally, a Trac would make more sense, but in light of all Trac instances being retired in 2017, it makes more sense for us to use Pagure for this purpose as this is what the project is moving to. If we can build the tool we need here, it will save us from having to worry about migration farther down the line.
To make these tools work for us, we'll need to answer some questions:
This would be a good topic for one of our meetings. We can discuss more about this in our next meeting tomorrow. More input will definitely be needed on this.
Discussed in 2016-08-09 meeting.
The FAS group will be most useful for keeping track of active members of the Diversity Team. In order for this to work well, we will need to have a clear onboarding process that makes it easy to understand how to get involved. Ideally, at the end of the onboarding steps, the end result would be getting sponsored into the diversity-team FAS group.
diversity-team
This will be filed as its own new ticket shortly.
We agreed on using Pagure for tracking issues, agenda items, and tasks in a ticket-like fashion. Since Trac is going away soon and Infrastructure is recommending those needing new Trac instances to use Pagure, it will make more sense for us to spend time customizing / adjusting to using Pagure so we don't have to worry about uprooting our "main base" of operations later on.
To begin using this most effectively, Diversity Team members have been advised to log into Pagure so they can be added to this repository. There will also be more tickets added in shortly to cover other items discussed in today's meeting.
I think that right now, the original needs for this ticket have been covered and taken care of. There are more specific issues for some of the items in this ticket, like #3 and #6. Closing ticket as fixed.
@jflory7 changed the status to Fixed
Fixed
I'm going to revive this ticket for the benefit of the FAD so we can visit our tooling tomorrow on Sunday.
@jflory7 changed the status to Open
Open
We verified that the tools we want to use later are set up correctly. For now, going to close this again.
Metadata Update from @jflory7: - Issue priority set to: None (was: 10)
Metadata Update from @jflory7: - Issue close_status updated to: Complete - Issue priority set to: 30 - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.