On 8/20/19 6:46 PM, Griselda Cuevas wrote:
On Tue, Aug 20, 2019, 9:30 AM Daniel Gruno <[email protected]> wrote:
On 8/20/19 6:17 PM, Gris Cuevas wrote:
Hi Folks,
I wanted to let you know that I've completed the vendor vetting process
[1] to find someone to work with for our contributor survey and user
experience research. The company we've selected is Bitergia, and they have
submitted a Statement of Work that I will refine with them before starting
work.
I'd like to invite anyone in the committee interested in being part of
this project to join us, Ideally, we would have one volunteer to lead work
around the contributor survey, so I can focus on the user experience
research, which will connect with our Outreachy internships.
In addition to the survey and the user experience research, they will
also do an analysis of data coming from our platforms measuring contributor
experience such as GitHub, Jira, etc. This part need refinement since we
need to work with our infra team and our V.P. of data privacy. I'd love to
also get a volunteer to help us with this.
What does "contributor experience" mean in this context, and how/why
would infra need be involved?
I made a mistake, what I meant was contributor activity, not contributor
experience.
The need for infra to be involved is an assumption at the moment. We still
don't have all the details of what data is available, what would be
interesting to analyze and how we should/could access it. These are
questions we need to articulate to seek answers, and those answers will
refine the statement of work.
I can say that in general, all infra services can be scanned at will, as
long as the rate limiting is respected (if you over-use one of our
services, it will start returning a 429 Rate Limited HTTP code meant to
slow down your requests - if a service respects this (such as how Kibble
does it), there shouldn't be any need to involve infra.
On the face of it, it just sounds like
scanning our repos and ticket trackers for data, which we have plenty of
services doing already - I wouldn't want us to re-invent the wheel here
if we can avoid it.
I agree 100%, and I'd love to get your help to ensure we don't do this. I
know you, Sharan and others have done excellent work with Apache Kibble,
and perhaps this project provides plenty of data already, so it could be
what serves as our data source.
Would you be available to help us navigate this so we scope a string and
meaningful deliverable?
Perhaps, but it might also be considered a conflict of interest, as I
work for a direct competitor in the field of FOSS analytics :) I think
it's best to leave to others to decide on that.
