From shekay at pobox.com  Thu Jun  2 11:24:45 2016
From: shekay at pobox.com (sheila miguez)
Date: Thu, 2 Jun 2016 10:24:45 -0500
Subject: [pyvideo-data] Pycon coordination
Message-ID: <CAHCs_rY9MnazJsGzziAYBFc39s+zO6LxoORVbhZ057rkJhGWUA@mail.gmail.com>

Hi everyone,

Those of you who are still in pycon mode, don't forget to talk to each
other about making a PR with pycon data.

Will pointed out in a PR with one talk that a PR with an entire event is
easier to manage. I concur, and to explain:

The normal procedures is to run a command to scrape a youtube channel to
get all of the talks in to files. There will be merge conflicts, duplicate
data, and so on if there are multiple branches with partial data or data
generated some other way.

Talk to each other so that there is no cookie looking and so that the
resulting PR is easy to review.

-- 
shekay at pobox.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyvideo-data/attachments/20160602/1a295e87/attachment.html>

From shekay at pobox.com  Thu Jun  2 20:46:50 2016
From: shekay at pobox.com (sheila miguez)
Date: Thu, 2 Jun 2016 19:46:50 -0500
Subject: [pyvideo-data] PyCon related links/resources Fwd: [PyCon-AV] PyCon
 Captions uploading
Message-ID: <CAHCs_rZ9dGcdYLCUBCQeSmzYNd_fZGkbO8F0yrGfWvxKrj38ig@mail.gmail.com>

Hi all,

Int he pyvideo api we had a field called related_links, see
https://github.com/pyvideo/pyvideo-data/issues/111 for fixing the missing
data from pyvideo-data.

I'd like for the transcripts/captions for each talk to be linked to the
data, if possible. Here's where they are placing data. Once 111 is worked
out, links to transcripts could be in the list of related things.

---------- Forwarded message ----------
From: David Wolever <wolever at pycon.ca>
Date: Thu, Jun 2, 2016 at 7:00 PM
Subject: [PyCon-AV] PyCon Captions uploading
To: mediacaptions at stradagize.com, Pycon Lists <pycon-av at python.org>


Hey all,

I?ve got the Google Drive folder we?ll use for collaborating on captions
setup and ready to go:
https://drive.google.com/open?id=0B3GLBsUBOoqsZ01uN3IyQ2xpSm8

There?s a spreadsheet in there which we?ll use to keep track of the caption
status for each talk, folders for the caption files, and a short doc
describing how to upload the captions (idk if this is totally necessary?
But thought I?d stick it in anyway).

I?ve chatted with Jonathan and he?s already started to get the spreadsheet
filled out.

Finally, I?m planning on sharing the folder link (read-only) with anyone
who asks about the status of captioning, so we shouldn?t put any
potentially confidential information there.

David


-- 
https://twitter.com/wolever
(416) 906-0403
Founder, PyCon Canada
Head of Session Staff, PyCon US

_______________________________________________
PyCon-AV mailing list
PyCon-AV at python.org
https://mail.python.org/mailman/listinfo/pycon-av




-- 
shekay at pobox.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyvideo-data/attachments/20160602/ef0526d3/attachment.html>

From paul.logston at gmail.com  Fri Jun  3 19:59:17 2016
From: paul.logston at gmail.com (Paul Logston)
Date: Fri, 3 Jun 2016 16:59:17 -0700
Subject: [pyvideo-data] Pytube using pytube/pyvideo-data
Message-ID: <CAJPJM9JHyRLJbAOUnQL9eWYiBZ_MvdGXOZCTBdb+95TeB73T5w@mail.gmail.com>

Hey Will and Sheila,

Wanted to keep you updated with the latest status of things. Since there's
a lot of people who are interested in making some changes to the
pyvideo-data repo while here at the sprints, I've made PyTube.org pull from
the pytube fork of pyvideo-data. I've made you both admins for the repo.
Let me know if you need anything regarding permissions for the data repo.

P


-- 
Paul Logston
(510) 755 - 4474
paul.logston at gmail.com
plog.paullogston.com
github.com/logston
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyvideo-data/attachments/20160603/e5aa9ed8/attachment.html>

From willkg at bluesock.org  Fri Jun  3 20:16:10 2016
From: willkg at bluesock.org (will kahn-greene)
Date: Fri, 03 Jun 2016 20:16:10 -0400
Subject: [pyvideo-data] Pytube using pytube/pyvideo-data
In-Reply-To: <CAJPJM9JHyRLJbAOUnQL9eWYiBZ_MvdGXOZCTBdb+95TeB73T5w@mail.gmail.com>
References: <CAJPJM9JHyRLJbAOUnQL9eWYiBZ_MvdGXOZCTBdb+95TeB73T5w@mail.gmail.com>
Message-ID: <1464999370.134443.627504337.17261B7F@webmail.messagingengine.com>

I don't really understand this plus it's the first I've heard about it,
so I'm puzzled.
 
I have a couple questions:
 
Why have people make changes to the pytube fork instead of the pyvideo-
data proper repo?
 
Are you planning to take the lead on upstreaming the changes in the
pytube fork? If not, then it seems like we end up with two divergent
versions of the data.
 
 
On Fri, Jun 3, 2016, at 07:59 PM, Paul Logston wrote:
> Hey Will and Sheila,
>
> Wanted to keep you updated with the latest status of things. Since
> there's a lot of people who are interested in making some changes to
> the pyvideo-data repo while here at the sprints, I've made PyTube.org
> pull from the pytube fork of pyvideo-data. I've made you both admins
> for the repo. Let me know if you need anything regarding permissions
> for the data repo.
>
> P
>
>
> --
> Paul Logston
> (510) 755 - 4474
> paul.logston at gmail.com
> plog.paullogston.com
> github.com/logston
> _________________________________________________
> pyvideo-data mailing list
> pyvideo-data at python.org
> https://mail.python.org/mailman/listinfo/pyvideo-data
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyvideo-data/attachments/20160603/2aba03ee/attachment.html>

From paul.logston at gmail.com  Fri Jun  3 20:31:31 2016
From: paul.logston at gmail.com (Paul Logston)
Date: Fri, 3 Jun 2016 17:31:31 -0700
Subject: [pyvideo-data] Pytube using pytube/pyvideo-data
In-Reply-To: <1464999370.134443.627504337.17261B7F@webmail.messagingengine.com>
References: <CAJPJM9JHyRLJbAOUnQL9eWYiBZ_MvdGXOZCTBdb+95TeB73T5w@mail.gmail.com>
 <1464999370.134443.627504337.17261B7F@webmail.messagingengine.com>
Message-ID: <CAJPJM9Lg_K8cEQ6T5rKSAmV-7UQPMrf4ppPmuUrFxA4WZdRTZA@mail.gmail.com>

Gotcha. Let me clarify. None of us at PyCon, who are sprinting on a
replacement for pyvideo.org and building the associated tooling for it,
have merge permissions for pyvideo/pyvideo-data. In order to move forward
more quickly with all of the changes coming down the pipe, we've forked the
repo and started to commit to it.

I'm not planning on taking the lead to upstream the changes. If a PR is
possible, I'd be happy to open one against the pyvideo-data repo. However,
since there's a lot more people with merge/admin permissions for pytube's
fork (9 people), it might make more sense to make the pytube fork the main
data repo. This would take the burden of you to have to review all PRs
coming through the gates. What do you think?




On Fri, Jun 3, 2016 at 5:16 PM, will kahn-greene <willkg at bluesock.org>
wrote:

> I don't really understand this plus it's the first I've heard about it, so
> I'm puzzled.
>
> I have a couple questions:
>
> Why have people make changes to the pytube fork instead of the
> pyvideo-data proper repo?
>
> Are you planning to take the lead on upstreaming the changes in the pytube
> fork? If not, then it seems like we end up with two divergent versions of
> the data.
>
>
> On Fri, Jun 3, 2016, at 07:59 PM, Paul Logston wrote:
>
> Hey Will and Sheila,
>
> Wanted to keep you updated with the latest status of things. Since there's
> a lot of people who are interested in making some changes to the
> pyvideo-data repo while here at the sprints, I've made PyTube.org pull from
> the pytube fork of pyvideo-data. I've made you both admins for the repo.
> Let me know if you need anything regarding permissions for the data repo.
>
> P
>
>
> --
> Paul Logston
> (510) 755 - 4474
> paul.logston at gmail.com
> plog.paullogston.com
> github.com/logston
> *_______________________________________________*
> pyvideo-data mailing list
> pyvideo-data at python.org
> https://mail.python.org/mailman/listinfo/pyvideo-data
>
>
>
> _______________________________________________
> pyvideo-data mailing list
> pyvideo-data at python.org
> https://mail.python.org/mailman/listinfo/pyvideo-data
>
>


-- 
Paul Logston
(510) 755 - 4474
paul.logston at gmail.com
plog.paullogston.com
github.com/logston
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyvideo-data/attachments/20160603/97a517e4/attachment.html>

From willkg at bluesock.org  Fri Jun  3 20:57:22 2016
From: willkg at bluesock.org (will kahn-greene)
Date: Fri, 03 Jun 2016 20:57:22 -0400
Subject: [pyvideo-data] Pytube using pytube/pyvideo-data
In-Reply-To: <CAJPJM9Lg_K8cEQ6T5rKSAmV-7UQPMrf4ppPmuUrFxA4WZdRTZA@mail.gmail.com>
References: <CAJPJM9JHyRLJbAOUnQL9eWYiBZ_MvdGXOZCTBdb+95TeB73T5w@mail.gmail.com>
 <1464999370.134443.627504337.17261B7F@webmail.messagingengine.com>
 <CAJPJM9Lg_K8cEQ6T5rKSAmV-7UQPMrf4ppPmuUrFxA4WZdRTZA@mail.gmail.com>
Message-ID: <1465001842.143997.627515665.7E89E1BA@webmail.messagingengine.com>

Oh noes! Sheila and I offered several times to help out with any work
being done at PyCon and never heard anything from anyone. Fixing
permissions issues is not hard, but no one mentioned the need to me.
Sheila had set up groups earlier this week, but I hadn't done anything
about it because there was no indication anyone would be interested on
this mailing list, in the IRC channel or in the github issue tracker.
 
I don't think it makes sense to have two master repositories around.
Given that you're going forward with yours, I'm inclined to throw in the
towel. Over the last few months, I tried pretty hard to bootstrap pyvideo-
data with the intention of passing it off to people who were involved.
It's been a disappointing journey. We've got a ton of people on this
mailing list, but it's pretty quiet. The IRC channel is quiet, too. The
github issue tracker is quiet.
 
After I ended pyvideo, I continued to spend time on pyvideo-data to
bootstrap it was because I think it's an important project. The data
is valuable for research on historical trends like diversity at
Python conferences. It's the only data set that's Python-centric and
makes it easier to find Python videos without requiring everyone to
post their videos on YouTube. I think it's important to build a site
on top of this data that makes the video accessible to people who are
otherwise disenfranchised using subtitles/captioning, downloadable
files, other formats (mp3 was a popular ask). I hope pytube  succeeds
in those things.
 
I'll catch up with Sheila at some point in the next few days, but I
think it makes sense to end pyvideo-data. If there's anything you need
me to do to finish things off or hand things over, let me know.
 
Good luck with the sprints!
 
/will
 
 
On Fri, Jun 3, 2016, at 08:31 PM, Paul Logston wrote:
> Gotcha. Let me clarify. None of us at PyCon, who are sprinting on a
> replacement for pyvideo.org and building the associated tooling for
> it, have merge permissions for pyvideo/pyvideo-data. In order to move
> forward more quickly with all of the changes coming down the pipe,
> we've forked the repo and started to commit to it.
>
> I'm not planning on taking the lead to upstream the changes. If a PR
> is possible, I'd be happy to open one against the pyvideo-data repo.
> However, since there's a lot more people with merge/admin permissions
> for pytube's fork (9 people), it might make more sense to make the
> pytube fork the main data repo. This would take the burden of you to
> have to review all PRs coming through the gates. What do you think?
>
>
>
>
> On Fri, Jun 3, 2016 at 5:16 PM, will kahn-greene
> <willkg at bluesock.org> wrote:
>> __
>> I don't really understand this plus it's the first I've heard about
>> it, so I'm puzzled.
>>
>> I have a couple questions:
>>
>> Why have people make changes to the pytube fork instead of the pyvideo-
>> data proper repo?
>>
>> Are you planning to take the lead on upstreaming the changes in the
>> pytube fork? If not, then it seems like we end up with two divergent
>> versions of the data.
>>
>>
>> On Fri, Jun 3, 2016, at 07:59 PM, Paul Logston wrote:
>>> Hey Will and Sheila,
>>>
>>> Wanted to keep you updated with the latest status of things. Since
>>> there's a lot of people who are interested in making some changes to
>>> the pyvideo-data repo while here at the sprints, I've made
>>> PyTube.org pull from the pytube fork of pyvideo-data. I've made you
>>> both admins for the repo. Let me know if you need anything regarding
>>> permissions for the data repo.
>>>
>>> P
>>>
>>>
>>> --
>>> Paul Logston
>>> (510) 755 - 4474[1]
>>> paul.logston at gmail.com
>>> plog.paullogston.com
>>> github.com/logston
>>> _________________________________________________
>>> pyvideo-data mailing list
>>> pyvideo-data at python.org
>>> https://mail.python.org/mailman/listinfo/pyvideo-data
>>
>>
>> _______________________________________________
>>  pyvideo-data mailing list
>> pyvideo-data at python.org
>> https://mail.python.org/mailman/listinfo/pyvideo-data
>>
>
>
>
> --
> Paul Logston
> (510) 755 - 4474
> paul.logston at gmail.com
> plog.paullogston.com
> github.com/logston
 

Links:

  1. tel:%28510%29%20755%20-%204474
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyvideo-data/attachments/20160603/7b72b27e/attachment-0001.html>

From lozinski at blogory.org  Sat Jun  4 00:00:29 2016
From: lozinski at blogory.org (Christopher Lozinski)
Date: Sat, 4 Jun 2016 06:00:29 +0200
Subject: [pyvideo-data] Pytube using pytube/pyvideo-data
In-Reply-To: <1465001842.143997.627515665.7E89E1BA@webmail.messagingengine.com>
References: <CAJPJM9JHyRLJbAOUnQL9eWYiBZ_MvdGXOZCTBdb+95TeB73T5w@mail.gmail.com>
 <1464999370.134443.627504337.17261B7F@webmail.messagingengine.com>
 <CAJPJM9Lg_K8cEQ6T5rKSAmV-7UQPMrf4ppPmuUrFxA4WZdRTZA@mail.gmail.com>
 <1465001842.143997.627515665.7E89E1BA@webmail.messagingengine.com>
Message-ID: <fa944715-18d1-c4f3-50ee-1dd4ca3d8ea7@blogory.org>

Here are my thoughts on the matter.

Maybe it would be a good idea if PyCon managed all the PyCon videos
under 1 repository, and all the other videos stayed under the PyVideo
repository. 

I am still planning on importing the PyVideo Data to blogory.org/python 
And allowing people to sort it by category.

Chris


From paul.logston at gmail.com  Sat Jun  4 01:23:57 2016
From: paul.logston at gmail.com (Paul Logston)
Date: Fri, 3 Jun 2016 22:23:57 -0700
Subject: [pyvideo-data] Pytube using pytube/pyvideo-data
In-Reply-To: <fa944715-18d1-c4f3-50ee-1dd4ca3d8ea7@blogory.org>
References: <CAJPJM9JHyRLJbAOUnQL9eWYiBZ_MvdGXOZCTBdb+95TeB73T5w@mail.gmail.com>
 <1464999370.134443.627504337.17261B7F@webmail.messagingengine.com>
 <CAJPJM9Lg_K8cEQ6T5rKSAmV-7UQPMrf4ppPmuUrFxA4WZdRTZA@mail.gmail.com>
 <1465001842.143997.627515665.7E89E1BA@webmail.messagingengine.com>
 <fa944715-18d1-c4f3-50ee-1dd4ca3d8ea7@blogory.org>
Message-ID: <CAJPJM9LZQG-YqTYi5P_9Tb4GeVuS-ScdVZbRPMMMLdPLA8a7xw@mail.gmail.com>

Hey Will,

Sounds like there was a miscommunication along the way. I agree that this
is a very important project and the care and leadership you and Sheila put
in is invaluable.

To your point, "I think it's important to build a site on top of this data
that makes the video accessible to people who are otherwise disenfranchised
using subtitles/captioning, downloadable files, other formats (mp3 was a
popular ask)", I completely agree. Check out our Development Philosophy
wiki page [0] and About page [1] for details. Also, I'd like to note that
we have Jeremy Bowman working on accessibility tests. PyTube is headed in a
very positive direction. A direction that will enable the Python community
to benefit from the work you and Sheila have done for years to come.

As for handing things off, transferring the pyvideo.org domain would really
help us maintain the integrity of the links that are already out there in
the wild. Would we be able to get that from you? Both Cameron and I have
been speaking with the PSF about hosting the pytube site. However, since
that could take a while, we'd really appreciate it if you transferred it to
the register used for pytube.org; gandi.net. If that transfer is okay with
you, feel free to contact me with a transfer authorization code. I'm happy
to reimburse you for any registration fees that you've already covered
going forward. Just let me know how much. I'm working on a grant proposal
to have the PSF reimburse pytube for the domain until it is transferred to
them.

Thanks again, Will and Sheila, for taking care of and growing this
incredible community resource.

Best,
Paul

[0] https://github.com/pytube/pytube/wiki/Development-Philosophy
[1] http://pytube.org/pages/about.html



On Fri, Jun 3, 2016 at 9:00 PM, Christopher Lozinski <lozinski at blogory.org>
wrote:

> Here are my thoughts on the matter.
>
> Maybe it would be a good idea if PyCon managed all the PyCon videos
> under 1 repository, and all the other videos stayed under the PyVideo
> repository.
>
> I am still planning on importing the PyVideo Data to blogory.org/python
> And allowing people to sort it by category.
>
> Chris
>
>


-- 
Paul Logston
(510) 755 - 4474
paul.logston at gmail.com
plog.paullogston.com
github.com/logston
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyvideo-data/attachments/20160603/2a23f304/attachment.html>

From shekay at pobox.com  Sat Jun  4 14:48:01 2016
From: shekay at pobox.com (sheila miguez)
Date: Sat, 4 Jun 2016 13:48:01 -0500
Subject: [pyvideo-data] Pytube using pytube/pyvideo-data
In-Reply-To: <1465001842.143997.627515665.7E89E1BA@webmail.messagingengine.com>
References: <CAJPJM9JHyRLJbAOUnQL9eWYiBZ_MvdGXOZCTBdb+95TeB73T5w@mail.gmail.com>
 <1464999370.134443.627504337.17261B7F@webmail.messagingengine.com>
 <CAJPJM9Lg_K8cEQ6T5rKSAmV-7UQPMrf4ppPmuUrFxA4WZdRTZA@mail.gmail.com>
 <1465001842.143997.627515665.7E89E1BA@webmail.messagingengine.com>
Message-ID: <CAHCs_rbRyZ99=ScMCe3wtCbj_+CnnfvjJDrEWxfZGUM6N_nq_w@mail.gmail.com>

Hey all,

Due to the lack of conversation on the mailing list, I didn't realize how
interested people were in working on things. I've been happy to see
activity on github. And now I've been cheered by the enthusiasm of people
in the pytube group and what I can see on pytube.org coming out of the
pycon sprint.

Paul has done well getting people involved. My intuition is that I think it
makes sense to sunset the pyvideo/pyvideo-data repo/mailing list and point
people over to the pytube repo since that where people are contributing the
most.

Re pytube philosophy.

I do like the About page and Development Philosophy. I've been following
the repo too.

Re pyvideo.org

I've been pondering what ground rules, if any, I'd like to see for passing
on the ownership of pyvideo.org. I'd like for it to be in the hands of the
PSF, with an understanding that it is in the hands of people who follow the
ideals of community and open culture. This is something Will and I have
have been talking about, and I've also talked to a couple of people on the
PSF board. It's a lot for me to think through and I haven't processed it
enough to have a conversation with everyone about it yet. Please be patient
with me as I do that. I don't mean to slight anyone in anyway by not
already discussing this.

In closing, I'm grateful to all of you who are working on this, and also
continue to be grateful for all the work Will does.


On Fri, Jun 3, 2016 at 7:57 PM, will kahn-greene <willkg at bluesock.org>
wrote:

> Oh noes! Sheila and I offered several times to help out with any work
> being done at PyCon and never heard anything from anyone. Fixing
> permissions issues is not hard, but no one mentioned the need to me. Sheila
> had set up groups earlier this week, but I hadn't done anything about it
> because there was no indication anyone would be interested on this mailing
> list, in the IRC channel or in the github issue tracker.
>
> I don't think it makes sense to have two master repositories around. Given
> that you're going forward with yours, I'm inclined to throw in the towel.
> Over the last few months, I tried pretty hard to bootstrap pyvideo-data
> with the intention of passing it off to people who were involved. It's been
> a disappointing journey. We've got a ton of people on this mailing list,
> but it's pretty quiet. The IRC channel is quiet, too. The github issue
> tracker is quiet.
>
> After I ended pyvideo, I continued to spend time on pyvideo-data to
> bootstrap it was because I think it's an important project. The data is
> valuable for research on historical trends like diversity at Python
> conferences. It's the only data set that's Python-centric and makes it
> easier to find Python videos without requiring everyone to post their
> videos on YouTube. I think it's important to build a site on top of this
> data that makes the video accessible to people who are otherwise
> disenfranchised using subtitles/captioning, downloadable files, other
> formats (mp3 was a popular ask). I hope pytube succeeds in those things.
>
> I'll catch up with Sheila at some point in the next few days, but I think
> it makes sense to end pyvideo-data. If there's anything you need me to do
> to finish things off or hand things over, let me know.
>
> Good luck with the sprints!
>
> /will
>
>
> On Fri, Jun 3, 2016, at 08:31 PM, Paul Logston wrote:
>
> Gotcha. Let me clarify. None of us at PyCon, who are sprinting on a
> replacement for pyvideo.org and building the associated tooling for it,
> have merge permissions for pyvideo/pyvideo-data. In order to move forward
> more quickly with all of the changes coming down the pipe, we've forked the
> repo and started to commit to it.
>
> I'm not planning on taking the lead to upstream the changes. If a PR is
> possible, I'd be happy to open one against the pyvideo-data repo. However,
> since there's a lot more people with merge/admin permissions for pytube's
> fork (9 people), it might make more sense to make the pytube fork the main
> data repo. This would take the burden of you to have to review all PRs
> coming through the gates. What do you think?
>
>
>
>
> On Fri, Jun 3, 2016 at 5:16 PM, will kahn-greene <willkg at bluesock.org>
> wrote:
>
>
> I don't really understand this plus it's the first I've heard about it, so
> I'm puzzled.
>
> I have a couple questions:
>
> Why have people make changes to the pytube fork instead of the
> pyvideo-data proper repo?
>
> Are you planning to take the lead on upstreaming the changes in the pytube
> fork? If not, then it seems like we end up with two divergent versions of
> the data.
>
>
> On Fri, Jun 3, 2016, at 07:59 PM, Paul Logston wrote:
>
> Hey Will and Sheila,
>
> Wanted to keep you updated with the latest status of things. Since there's
> a lot of people who are interested in making some changes to the
> pyvideo-data repo while here at the sprints, I've made PyTube.org pull from
> the pytube fork of pyvideo-data. I've made you both admins for the repo.
> Let me know if you need anything regarding permissions for the data repo.
>
> P
>
>
> --
> Paul Logston
> (510) 755 - 4474
> paul.logston at gmail.com
> plog.paullogston.com
> github.com/logston
> *_______________________________________________*
> pyvideo-data mailing list
> pyvideo-data at python.org
> https://mail.python.org/mailman/listinfo/pyvideo-data
>
>
>
> _______________________________________________
> pyvideo-data mailing list
> pyvideo-data at python.org
> https://mail.python.org/mailman/listinfo/pyvideo-data
>
>
>
>
>
> --
> Paul Logston
> (510) 755 - 4474
> paul.logston at gmail.com
> plog.paullogston.com
> github.com/logston
>
>
>
> _______________________________________________
> pyvideo-data mailing list
> pyvideo-data at python.org
> https://mail.python.org/mailman/listinfo/pyvideo-data
>
>


-- 
shekay at pobox.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyvideo-data/attachments/20160604/74e4ba02/attachment.html>

From paul.logston at gmail.com  Sat Jun  4 16:24:11 2016
From: paul.logston at gmail.com (Paul Logston)
Date: Sat, 4 Jun 2016 16:24:11 -0400
Subject: [pyvideo-data] Pytube using pytube/pyvideo-data
In-Reply-To: <CAHCs_rbRyZ99=ScMCe3wtCbj_+CnnfvjJDrEWxfZGUM6N_nq_w@mail.gmail.com>
References: <CAJPJM9JHyRLJbAOUnQL9eWYiBZ_MvdGXOZCTBdb+95TeB73T5w@mail.gmail.com>
 <1464999370.134443.627504337.17261B7F@webmail.messagingengine.com>
 <CAJPJM9Lg_K8cEQ6T5rKSAmV-7UQPMrf4ppPmuUrFxA4WZdRTZA@mail.gmail.com>
 <1465001842.143997.627515665.7E89E1BA@webmail.messagingengine.com>
 <CAHCs_rbRyZ99=ScMCe3wtCbj_+CnnfvjJDrEWxfZGUM6N_nq_w@mail.gmail.com>
Message-ID: <CAJPJM9LCvZFF10ZuC_paGyZLXwJ2O-Bh199aoa1iLpLUJwVewA@mail.gmail.com>

Hey Sheila,

Thanks for the update. FTR, no slight is taken here at the PyTube team. We
completely understand that its a big change and a fast moving one. Thanks
for all your work.

Best,
P

On Sat, Jun 4, 2016 at 2:48 PM, sheila miguez <shekay at pobox.com> wrote:

> Hey all,
>
> Due to the lack of conversation on the mailing list, I didn't realize how
> interested people were in working on things. I've been happy to see
> activity on github. And now I've been cheered by the enthusiasm of people
> in the pytube group and what I can see on pytube.org coming out of the
> pycon sprint.
>
> Paul has done well getting people involved. My intuition is that I think
> it makes sense to sunset the pyvideo/pyvideo-data repo/mailing list and
> point people over to the pytube repo since that where people are
> contributing the most.
>
> Re pytube philosophy.
>
> I do like the About page and Development Philosophy. I've been following
> the repo too.
>
> Re pyvideo.org
>
> I've been pondering what ground rules, if any, I'd like to see for passing
> on the ownership of pyvideo.org. I'd like for it to be in the hands of
> the PSF, with an understanding that it is in the hands of people who follow
> the ideals of community and open culture. This is something Will and I have
> have been talking about, and I've also talked to a couple of people on the
> PSF board. It's a lot for me to think through and I haven't processed it
> enough to have a conversation with everyone about it yet. Please be patient
> with me as I do that. I don't mean to slight anyone in anyway by not
> already discussing this.
>
> In closing, I'm grateful to all of you who are working on this, and also
> continue to be grateful for all the work Will does.
>
>
> On Fri, Jun 3, 2016 at 7:57 PM, will kahn-greene <willkg at bluesock.org>
> wrote:
>
>> Oh noes! Sheila and I offered several times to help out with any work
>> being done at PyCon and never heard anything from anyone. Fixing
>> permissions issues is not hard, but no one mentioned the need to me. Sheila
>> had set up groups earlier this week, but I hadn't done anything about it
>> because there was no indication anyone would be interested on this mailing
>> list, in the IRC channel or in the github issue tracker.
>>
>> I don't think it makes sense to have two master repositories around.
>> Given that you're going forward with yours, I'm inclined to throw in the
>> towel. Over the last few months, I tried pretty hard to bootstrap
>> pyvideo-data with the intention of passing it off to people who were
>> involved. It's been a disappointing journey. We've got a ton of people on
>> this mailing list, but it's pretty quiet. The IRC channel is quiet, too.
>> The github issue tracker is quiet.
>>
>> After I ended pyvideo, I continued to spend time on pyvideo-data to
>> bootstrap it was because I think it's an important project. The data is
>> valuable for research on historical trends like diversity at Python
>> conferences. It's the only data set that's Python-centric and makes it
>> easier to find Python videos without requiring everyone to post their
>> videos on YouTube. I think it's important to build a site on top of this
>> data that makes the video accessible to people who are otherwise
>> disenfranchised using subtitles/captioning, downloadable files, other
>> formats (mp3 was a popular ask). I hope pytube succeeds in those things.
>>
>> I'll catch up with Sheila at some point in the next few days, but I think
>> it makes sense to end pyvideo-data. If there's anything you need me to do
>> to finish things off or hand things over, let me know.
>>
>> Good luck with the sprints!
>>
>> /will
>>
>>
>> On Fri, Jun 3, 2016, at 08:31 PM, Paul Logston wrote:
>>
>> Gotcha. Let me clarify. None of us at PyCon, who are sprinting on a
>> replacement for pyvideo.org and building the associated tooling for it,
>> have merge permissions for pyvideo/pyvideo-data. In order to move forward
>> more quickly with all of the changes coming down the pipe, we've forked the
>> repo and started to commit to it.
>>
>> I'm not planning on taking the lead to upstream the changes. If a PR is
>> possible, I'd be happy to open one against the pyvideo-data repo. However,
>> since there's a lot more people with merge/admin permissions for pytube's
>> fork (9 people), it might make more sense to make the pytube fork the main
>> data repo. This would take the burden of you to have to review all PRs
>> coming through the gates. What do you think?
>>
>>
>>
>>
>> On Fri, Jun 3, 2016 at 5:16 PM, will kahn-greene <willkg at bluesock.org>
>> wrote:
>>
>>
>> I don't really understand this plus it's the first I've heard about it,
>> so I'm puzzled.
>>
>> I have a couple questions:
>>
>> Why have people make changes to the pytube fork instead of the
>> pyvideo-data proper repo?
>>
>> Are you planning to take the lead on upstreaming the changes in the
>> pytube fork? If not, then it seems like we end up with two divergent
>> versions of the data.
>>
>>
>> On Fri, Jun 3, 2016, at 07:59 PM, Paul Logston wrote:
>>
>> Hey Will and Sheila,
>>
>> Wanted to keep you updated with the latest status of things. Since
>> there's a lot of people who are interested in making some changes to the
>> pyvideo-data repo while here at the sprints, I've made PyTube.org pull from
>> the pytube fork of pyvideo-data. I've made you both admins for the repo.
>> Let me know if you need anything regarding permissions for the data repo.
>>
>> P
>>
>>
>> --
>> Paul Logston
>> (510) 755 - 4474
>> paul.logston at gmail.com
>> plog.paullogston.com
>> github.com/logston
>> *_______________________________________________*
>> pyvideo-data mailing list
>> pyvideo-data at python.org
>> https://mail.python.org/mailman/listinfo/pyvideo-data
>>
>>
>>
>> _______________________________________________
>> pyvideo-data mailing list
>> pyvideo-data at python.org
>> https://mail.python.org/mailman/listinfo/pyvideo-data
>>
>>
>>
>>
>>
>> --
>> Paul Logston
>> (510) 755 - 4474
>> paul.logston at gmail.com
>> plog.paullogston.com
>> github.com/logston
>>
>>
>>
>> _______________________________________________
>> pyvideo-data mailing list
>> pyvideo-data at python.org
>> https://mail.python.org/mailman/listinfo/pyvideo-data
>>
>>
>
>
> --
> shekay at pobox.com
>



-- 
Paul Logston
(510) 755 - 4474
paul.logston at gmail.com
plog.paullogston.com
github.com/logston
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyvideo-data/attachments/20160604/6d6af6c3/attachment-0001.html>

From shekay at pobox.com  Mon Jun  6 10:32:18 2016
From: shekay at pobox.com (sheila miguez)
Date: Mon, 6 Jun 2016 09:32:18 -0500
Subject: [pyvideo-data] Closing down pyvideo-data
Message-ID: <CAHCs_rb=2jdRfvRdjjAc4cbz1x7-9jqr7New5E1YJyy46oVFcA@mail.gmail.com>

Hi all,

We have an issue for closing down pyvideo-data.

https://github.com/pyvideo/pyvideo-data/issues/139

-- 
shekay at pobox.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyvideo-data/attachments/20160606/95030759/attachment.html>

From shekay at pobox.com  Tue Jun  7 17:15:56 2016
From: shekay at pobox.com (sheila miguez)
Date: Tue, 7 Jun 2016 16:15:56 -0500
Subject: [pyvideo-data] PyCon BoF
In-Reply-To: <CAHCs_rbbEScm9C9VnZ15yEUdiqrJxwJxhY+OsFhKWN6bPpZRwg@mail.gmail.com>
References: <CAJPJM9+bWW4Vy+W72kyhm-MXwSDyk7L+aLJK+nejfjTKACxv6Q@mail.gmail.com>
 <15504c0b45e.be8d718c22160.8553763280266271263@pinkhatbeard.com>
 <CAHCs_rbbEScm9C9VnZ15yEUdiqrJxwJxhY+OsFhKWN6bPpZRwg@mail.gmail.com>
Message-ID: <CAHCs_rYLXb-M+tMPSxgMp2f8L2vCFukfum9oeq0rEiHbuARoaA@mail.gmail.com>

Hey, here's the lightning talk.
https://youtu.be/yC9m2GInXqU?t=28m47s

I feel a little at a loss. I know we said we were shutting down pyvideo.org,
but we followed up to guide people here to work on data and do curation
tasks.

I managed to discover Paul when I was navigating around on github, looking
at forks.

I didn't discover the work Cameron did. If you emailed or tweeted me, I'm
sorry if I lost track of any conversations.

I did not mean to overlook anyone. I'm sad that people overlooked us.




On Tue, May 31, 2016 at 9:47 AM, sheila miguez <shekay at pobox.com> wrote:

> Is the lightning talk online yet?
>
>
>
> On Mon, May 30, 2016 at 9:59 PM, Cameron Dershem <cameron at pinkhatbeard.com
> > wrote:
>
>> I have no preference on a time, but wanted to say I'm hosting a sprint on
>> Thursday and Friday to hack on pyvideo.org. I did a lightning talk today
>> and have a lot of people who want to help out. I'd also be very interested
>> in helping with the data project.
>>
>> - Cameron Dershem
>>   Developer
>>   Indianapolis
>>   pinkhatbeard.com
>>   cameron at pinkhatbeard.com
>>   312.361.0322
>>
>>
>> ---- On Mon, 30 May 2016 21:08:12 -0400 * paul.logston at gmail.com
>> <paul.logston at gmail.com> * wrote ----
>>
>> Hey everybody,
>>
>> I'm thinking of signing up for a pyvideo-data BoF room at PyCon. Anybody
>> got a preference for when it happens?
>>
>> P
>>
>>
>>
>> --
>> Sent from Gmail Mobile
>> _______________________________________________
>> pyvideo-data mailing list
>> pyvideo-data at python.org
>> https://mail.python.org/mailman/listinfo/pyvideo-data
>>
>>
>> _______________________________________________
>> pyvideo-data mailing list
>> pyvideo-data at python.org
>> https://mail.python.org/mailman/listinfo/pyvideo-data
>>
>>
>
>
> --
> shekay at pobox.com
>



-- 
shekay at pobox.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyvideo-data/attachments/20160607/94863a5c/attachment.html>