Learn more about these different git repos.
Other Git URLs
The last status check was on NA by NA.
A summary of number of tickets by the interest tags:
What do we think?
Can I e-mail all these people in bcc, and set the reply to: the mailing list to ping them again, in case they're not seeing their pagure notifications?
I think that we should engage a discussion here. It is not a simple topic, you know. This is not a scientific analysis, but these are my observations: - people would like to contribute. But what "to contribute" means? People don't like a definition of "contribution" different from "coding" and "sysadmin". Or people is not aware of that. - people would like to contribute mainly by "coding"/"developing software", but we know, we don't develop software (or at least not the software this people is aware of), and again, contributing to, let's say to pagure, for a newcomer that most of the times is the first time she/he contribute to an open source project, well, it is not easy. - people often think that we are here to assign tasks to them, and again, we are not employers, and it is not easy, everyone should find something the like to do.
Well, it is not simple...
+1, I totally agree.
So, what activities can people do that will help them meet the people of Fedora before they jump in to tasks? Should we organise "meet and greets", for example?
Additionally, in the long term, to improve people's understanding of Fedora, how does this sound: - we need to talk more to people outside the community about what Fedora really does (and does not do) - we need to talk more to people outside the community about how Fedora works (no bosses/no managers---all colleagues, self assigning tasks, peer-review)
In addition, my feeling is that if you advice to hang around, to read documents, subscribe to mailing lists, to follow the various discussions, blogs, and so on, people doesn't seem interested.
In many other cases it seems that: hey I want to contribute. Then the day after people disappears.
Hrm, so they sort of want to "contribute" without learning the necessary skills. We can help improve the path to the learning, but we cannot remove the required learning completely :thought_balloon:
That's fine. We take the positive view and hope that they'll remain active, but if someone is not ready to put in the time (for whatever reason), we can't help them. We can only help them help themselves. These tickets will get removed using our process.
This is a common behavior in all group, people fight for a membership, when they see the reality or after that they think I'm doing all of this wasting time/efforts without payment and forget it:
+1 for this METRIC
Regards.,
This is a common behavior in all group, people fight for a membership, when they see the reality or after that they think I'm doing all of this wasting time/efforts without payment and forget it: Needs free time to collaborate Needs commitment Needs to be Pro-active
Needs free time to collaborate Needs commitment Needs to be Pro-active
Is there a way we can collect the average amount of time required by volunteers for each team perhaps? That'll help us tell newcomers how much time they need so they have some information about what they're getting into? (It could also perhaps be added to wcidff?).
Should we speak to commops or mindshare about this?
This is not about collecting memberships As you said we are not employers we are facilitators Why don't get money for this task, some people don't accept this +1 for this METRIC Regards.,
This is not about collecting memberships As you said we are not employers we are facilitators Why don't get money for this task, some people don't accept this
+1 for this METRIC Regards.,
Yes, the "volunteering" bit takes people time to learn. They'll only learn if they spend some time in the community, though. So, we've got to find a way of encouraging that first.
@hhlp @alciregi @sash713 @alishapapun : could one of you please ping folks and review the tickets this week?
When you do so, please close this ticket and open a new one.
You can use the new script @sash713 wrote for us to get some preliminary information, but it'll still require going over the tickets manually to respond to people. (Takes about 35 minutes)
@sash713 made a script, that will help with this Metric ->
https://pagure.io/fedora-join/Fedora-Join/blob/master/f/scripts/GetTicketInfo
Total running metrics:
* Total newcomers in queue (open tickets) * New Fedora community members (successfully on-boarded newcomers) * Inactive tickets (tickets closed without successful on-boarding)
Provide also
* Summary of interests, A summary of number of tickets by the interest tags:
and a review for each ticket:
@hhlp @alciregi @sash713 @alishapapun : could one of you please ping folks and review the tickets this week? When you do so, please close this ticket and open a new one. You can use the new script @sash713 wrote for us to get some preliminary information, but it'll still require going over the tickets manually to respond to people. (Takes about 35 minutes)
@ankursinha I'll take care of it tomorrow....
I've already finish to accomplish this task:
Metadata Update from @hhlp: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.