Hello guys,
Pete and me were discussing about the need to have a fedora-join in the ticketing system.
Benefits:
1) follow the correct workflow 2) wiki gardening/renew 3) audit onboarding process for each SIG (many tickets) 4) developing some plan to help new folks 5) get copy about the join sig into the FAS web ui and the FAS todo list 6) seeking people from other groups that would take care of a tutoring service
Disadvantage: 1) use only for startup, then a few-days-per-year use.
Did I forget anything? Suggestions?
Gabri (mailga)
On Apr 3, 2015 9:27 AM, "Gabriele Trombini" g.trombini@gmail.com wrote:
Hello guys,
Pete and me were discussing about the need to have a fedora-join in the ticketing system.
Benefits:
- follow the correct workflow
- wiki gardening/renew
- audit onboarding process for each SIG (many tickets)
- developing some plan to help new folks
- get copy about the join sig into the FAS web ui and the FAS todo list
- seeking people from other groups that would take care of a tutoring
service
Disadvantage:
- use only for startup, then a few-days-per-year use.
Did I forget anything? Suggestions?
Gabri (mailga)
I think that even if this gets used for only a handful of tickets for each year, it will still provide a useful place to reference the things we have accomplished. It also allows join SIG members a space to develop their efforts apart from the mailing list; the list then could focus more on direct help of new folks with less distracting internal activity.
--Pete
In data venerdì 3 aprile 2015 11:48:36, Pete Travis ha scritto:
I think that even if this gets used for only a handful of tickets for
each
year, it will still provide a useful place to reference the things we
have
accomplished. It also allows join SIG members a space to develop
their
efforts apart from the mailing list; the list then could focus more on direct help of new folks with less distracting internal activity.
--Pete
I agree and just for that I think we should have. Working on mailing list means getting lost in several discontinuous mails, often forgotten, in different days unlike the track where, for each ticket, we can follow a linear discussion.
So +1 for having a join-SIG trac.
Gabri
On Fri, 2015-04-03 at 20:09 +0200, Gabriele Trombini wrote:
So +1 for having a join-SIG trac.
+1 - a trac instance would be really helpful. Gabri, since you started the thread, would you please open a ticket with infra and get us one? :)
To start with, randomuser, you, and I could be trac admins. I manage the freemedia trac and have some experience with the configuration and things.
Hi Gabriele,
El 03/04/2015 9:27 am, Gabriele Trombini escribió:
Hello guys,
Pete and me were discussing about the need to have a fedora-join in the ticketing system.
Great idea!
Benefits:
- follow the correct workflow
- wiki gardening/renew
- audit onboarding process for each SIG (many tickets)
- developing some plan to help new folks
- get copy about the join sig into the FAS web ui and the FAS todo
list 6) seeking people from other groups that would take care of a tutoring service
The workflow to follow can be to encourage every newcomer who feels that needs help to open a new ticket so that a mentor is able to pick up it. What do you think?
We can have these types of tickets: * mentoring request; this can use keywords for different teams (docs, packaging, etc). * contributing opportunity; we create these according to teams needs. Similar to easyfix but including non-coding tasks in the scope. * internal Join SIG tasks.
Eduardo
In data venerdì 3 aprile 2015 21:31:06, Eduardo Mayorga Téllez ha scritto:
Hi Gabriele,
El 03/04/2015 9:27 am, Gabriele Trombini escribió:
Hello guys,
Pete and me were discussing about the need to have a fedora-
join in
the ticketing system.
Great idea!
Done!
Now we have to setup the trac. I think a meeting is needful for deciding how it has to work.
Thanks.
Gabri
On Sat, 2015-04-04 at 12:02 +0200, Gabriele Trombini wrote:
I think a meeting is needful for deciding how it has to work.
+1 A meeting would be nice to first get a good idea of the activities we'll carry out and how the trac should be set up to aid us in these. :D
fedora-join@lists.fedoraproject.org