[fedora-commops] Issue #83: replace/improve etherpad working space
by Justin W. Flory
jflory7 added a new comment to an issue you are following:
``
## Ticket closed
Given that we haven't had a [hack session](https://fedoraproject.org/wiki/Hack_session) in a fair amount of time, that was a lot of the original motivation behind this ticket. I did some ticket triaging with @bee2502 and we agreed that if we resume the hack sessions or other collaborative sessions outside of meetings, deliberate focus would be needed to convey the info about whatever we accomplish off the Etherpad. This would either be ticket comments or blog posts, or some other form of external reporting.
Since we aren't actively using Etherpads for storing current information like we were before, I'm going to close this ticket. We can always revisit it later if it crops up again.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-commops/issue/83
6 years, 11 months
[fedora-commops] Issue #54: [Onboarding Series] EPEL
by Bhagyashree Padalkar
bee2502 added a new comment to an issue you are following:
``
The next steps for this ticket would be :
* Send an email to the EPEL team’s mailing list about Onboarding process, how having a defined onboarding process is important for newcomers interested in the team, and how CommOps can assist them in creating one and if they would like it. [You can find an example mail on Python SIG ML for their Onboarding]
* Start a discussion with the EPEL team members about what some example tasks for newcomers could be and if they already have a brief example for this on their wiki page via Mailing lists, IRC and attending their meetings.
* Comment the updates/ progress for team in this CommOps Pagure issue and let others know about the progress in weekly CommOps meetings.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-commops/issue/54
6 years, 11 months