From paul.logston at gmail.com Sun May 1 22:43:30 2016 From: paul.logston at gmail.com (Paul Logston) Date: Sun, 1 May 2016 22:43:30 -0400 Subject: [pyvideo-data] this week: markdown -> reST converter, schemas In-Reply-To: References: <1461765215.186944.591175665.318DC482@webmail.messagingengine.com> Message-ID: Hey Anand, Great to hear your willing to help. All the credit for pyvideo-data goes to Will and Sheila. As for a static site, I've been working on one called http://pytube.org/. Right now I've stopped work until pyvideo-data is converted to reST, but once that is done I plan to make the site more user friendly. I'll have a TODO list or file in the pytube.org repo and any help would be greatly appreciated. P On Thu, Apr 28, 2016 at 1:19 AM, Anand Reddy Pandikunta < anand21nanda at gmail.com> wrote: > Hi, > > I have been using PyVideo for about a year. I was surprised to know > that it might shutdown this year. So I joined ML to see if I can help. > > I will be interested in creating/maintaining static website. If anyone is > interested, we can start working on it. > > Thanks to Will, Paul & Sheila for building pyvideo-data > . > > > ------------------------- > Chillar Anand > www.avilpage.com > > > On Wed, Apr 27, 2016 at 7:23 PM, will kahn-greene > wrote: > >> Hi! >> >> I've noticed a bunch of new people subscribed to the list, but it's >> still intensely quiet. I'd love to know what's compelled people to join >> the list. Do you want to help with curating data? Do you have projects >> in mind to use the data for? Are you looking for people to work with on >> things that are important to you? Sheila and I would love to know so >> that we have a better feel for who's interested in what. I think the >> list is small enough that people could reply to the list. If you want to >> send to me directly, that's fine, too. willkg at bluesock.org >> >> Last month we decided to switch from Markdown to Restructured Text. Paul >> put together a PR with a script to convert the existing summaries and >> descriptions. The PR is here: >> >> https://github.com/pyvideo/pyvideo-data/pull/30 >> >> After that lands, we can convert summaries and descriptions and then >> move forward with that settled. Thank you, Paul! >> >> I've been thinking about how to get clive out of the pyvideo-data >> repository and turn it into a separate project. One of the things I'm >> grappling with is that we've defined the schema for the data in the >> clive code. So then I think we need to move the schema definition into >> the pyvideo-data repository and change clive so that it knows where to >> find it. I haven't figured out a way to do that which makes me happy. >> >> On a related note, I've been thinking more about switching from my >> schema representation to json-schema--something Paul suggested. >> >> Does anyone have experience with json-schema on this list? If you do, >> I'd love to talk with you about the format as well as the tools >> available. >> >> I think that's everything that's happened in the last month. >> >> Thank you everyone! >> >> /will >> _______________________________________________ >> 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: From lozinski at blogory.org Mon May 2 03:51:06 2016 From: lozinski at blogory.org (lozinski at blogory.org) Date: Mon, 02 May 2016 09:51:06 +0200 Subject: [pyvideo-data] My Strategy In-Reply-To: References: <1461765215.186944.591175665.318DC482@webmail.messagingengine.com> Message-ID: <68c273f7773b420b01eb67441e89de23@blogory.org> I run blogory.org/python, the world's largest Python directory. Over 1000 pages. Here are my thoughts on cataloguing Python Videos. I thought this would be a good group to discuss it. Let me know what you think. For context, Blogory.org is organized as a tree of categories. I want to import the data, organized by conference, then crowdsource the sorting of videos, just click on a tree form field to move the video to the appropriate subject category. There are so many Python videos out there. Really multiple ones per topic. Too many really. I think that users just want to see the best videos, organized by subject. I also think that people would prefer the newer videos, Maybe on any given topic, they want to see the newest python 2 video, and the newest Python 3 videos. The best presentations are probably the global PyCon conference videos, maybe also EuroPython, and Asia Python presentations. So I am thinking of just using the YouTube Api's, just from the PyCon and EuroPython conferences and grabbing those videos and crowd source sorting them. Then add in any old video on an extreme topic, say managing bees with Python, should also be included. Although realistically I will never get to that, they can then search on Google for any niche topic. What do you think of this approach? What is wrong with it? What are the advantages of going with the full Py Video Data? Chris From willkg at bluesock.org Mon May 2 09:29:56 2016 From: willkg at bluesock.org (will kahn-greene) Date: Mon, 02 May 2016 09:29:56 -0400 Subject: [pyvideo-data] My Strategy In-Reply-To: <68c273f7773b420b01eb67441e89de23@blogory.org> References: <1461765215.186944.591175665.318DC482@webmail.messagingengine.com> <68c273f7773b420b01eb67441e89de23@blogory.org> Message-ID: <1462195796.1452209.595560593.7D72551E@webmail.messagingengine.com> I think it'll be tough finding the the best videos for a subject. What's the granularity of "a subject"? Is it a big grain like "Django"? Is it a small grain like "Building a REST API using Django"? Is every Python package considered a subject? Sheila and I also thought that boosting the scores of search results that were more recent was a good idea. We worked on that a bit, but never implemented it, so I don't have any empirical or anecdotal data to share. Sheila and I also thought that having curated playlists was really important because it empowers everyone to build a list of videos in a specific order that they thought was important. This lends itself to education-related use cases. I threw together a rough implementation last year to see how people would use it and whether it'd gain traction or not. It did get used a lot, but it seems like it only got used by people building queues of videos to watch on pyvideo. I wrote about this a bit here: http://bluesock.org/~willkg/blog/pyvideo/status_20150409.html Anyhow, if all the videos are on YouTube and people have a YouTube account, they can do the playlist thing there. I don't know offhand if that's done much. Sheila and I thought about this a lot, but we didn't get very far with implementation of anything. Looking back, I wish I wrote more about what we were thinking and why in regards to browsing, searching and navigation of the data. None of this is set in stone. It's just things we were thinking and working on. Hope that helps! On Mon, May 2, 2016, at 03:51 AM, lozinski at blogory.org wrote: > I run blogory.org/python, the world's largest Python directory. Over > 1000 pages. > Here are my thoughts on cataloguing Python Videos. I thought this would > be a good group to discuss it. Let me know what you think. > > For context, Blogory.org is organized as a tree of categories. I want > to import the data, organized by conference, then crowdsource the > sorting of videos, just click on a tree form field to move the video to > the appropriate subject category. > > There are so many Python videos out there. Really multiple ones per > topic. > Too many really. > > I think that users just want to see the best videos, organized by > subject. > > I also think that people would prefer the newer videos, Maybe on any > given topic, they want to see the newest python 2 video, and the newest > Python 3 videos. > > The best presentations are probably the global PyCon conference videos, > maybe also EuroPython, and Asia Python presentations. > > So I am thinking of just using the YouTube Api's, just from the PyCon > and EuroPython conferences and grabbing those videos and crowd source > sorting them. > > Then add in any old video on an extreme topic, say managing bees with > Python, should also be included. Although realistically I will never > get to that, they can then search on Google for any niche topic. > > What do you think of this approach? What is wrong with it? What are > the advantages of going with the full Py Video Data? > > Chris From lozinski at blogory.org Mon May 2 10:09:06 2016 From: lozinski at blogory.org (lozinski at blogory.org) Date: Mon, 02 May 2016 16:09:06 +0200 Subject: [pyvideo-data] My Strategy In-Reply-To: <1462195796.1452209.595560593.7D72551E@webmail.messagingengine.com> References: <1461765215.186944.591175665.318DC482@webmail.messagingengine.com> <68c273f7773b420b01eb67441e89de23@blogory.org> <1462195796.1452209.595560593.7D72551E@webmail.messagingengine.com> Message-ID: Great letter. I just received links for 4 videos this morning. http://blogory.org/zerodb-videos ZeroDB is a persistent python database, blogory.org/persistent-python where all the encryption and decryption is done on the client, the server knows literally nothing. Based on ZODB. And of course 2 of the videos were on Vimeo, two were on YouTube. Lesson learned. On 2016-05-02 15:29, will kahn-greene wrote: > What's > the granularity of "a subject"? Is it a big grain like "Django"? Is it > a > small grain like "Building a REST API using Django"? Is every Python > package considered a subject? The granularity of a subject is that size which contains about seven items. People's brains are flexible. They can grok this. ANy more than that, it is confusing. Any less than that, it adds needless complexity. When a category gets too big, I split it in half. 7 items makes it easy for them to people to understand. Here is one example of hierarchy. I am sure all developers get it. Introduction / Python / Python Libraries / Python Database Libraries / Persistent Python / ZeroDB Database / ZeroDB Articles Of course hierarchy makes the most sense when you are browsing in it. It puts things in context of each other. > I think it'll be tough finding the the best videos for a subject. That is a very good point. First of all who defines best? Shortest? Most technical content? Easiest to understand" I believe YouTube offers stars. That is simple. I will be inviting people to review videos. Anyone want to review any of the 4 zerodb videos listed above? The zerodb guys would be very grateful if you did so, and you could learn about zerodb in the process. Just register on blogory.org, tell me which video you want to review, and I will give you permission to edit their descriptions. I love your idea of playlists/queues. I should extend my YouTube object to use The Youtube playlists and queues. And the same for the Vimeo class I need to create. Regards Chris From shekay at pobox.com Mon May 2 10:31:24 2016 From: shekay at pobox.com (sheila miguez) Date: Mon, 2 May 2016 09:31:24 -0500 Subject: [pyvideo-data] this week: markdown -> reST converter, schemas In-Reply-To: References: <1461765215.186944.591175665.318DC482@webmail.messagingengine.com> Message-ID: Hi all, Don't forget to help Paul get back to work on pytube would be to spend time reviewing his pull request so that it can get merged. Many hands make light work. https://github.com/pyvideo/pyvideo-data/pull/30 On Sun, May 1, 2016 at 9:43 PM, Paul Logston wrote: > Hey Anand, > > Great to hear your willing to help. All the credit for pyvideo-data goes > to Will and Sheila. As for a static site, I've been working on one called > http://pytube.org/. Right now I've stopped work until pyvideo-data is > converted to reST, but once that is done I plan to make the site more user > friendly. I'll have a TODO list or file in the pytube.org repo and any > help would be greatly appreciated. > > P > > On Thu, Apr 28, 2016 at 1:19 AM, Anand Reddy Pandikunta < > anand21nanda at gmail.com> wrote: > >> Hi, >> >> I have been using PyVideo for about a year. I was surprised to know >> that it might shutdown this year. So I joined ML to see if I can help. >> >> I will be interested in creating/maintaining static website. If anyone is >> interested, we can start working on it. >> >> Thanks to Will, Paul & Sheila for building pyvideo-data >> . >> >> >> ------------------------- >> Chillar Anand >> www.avilpage.com >> >> >> On Wed, Apr 27, 2016 at 7:23 PM, will kahn-greene >> wrote: >> >>> Hi! >>> >>> I've noticed a bunch of new people subscribed to the list, but it's >>> still intensely quiet. I'd love to know what's compelled people to join >>> the list. Do you want to help with curating data? Do you have projects >>> in mind to use the data for? Are you looking for people to work with on >>> things that are important to you? Sheila and I would love to know so >>> that we have a better feel for who's interested in what. I think the >>> list is small enough that people could reply to the list. If you want to >>> send to me directly, that's fine, too. willkg at bluesock.org >>> >>> Last month we decided to switch from Markdown to Restructured Text. Paul >>> put together a PR with a script to convert the existing summaries and >>> descriptions. The PR is here: >>> >>> https://github.com/pyvideo/pyvideo-data/pull/30 >>> >>> After that lands, we can convert summaries and descriptions and then >>> move forward with that settled. Thank you, Paul! >>> >>> I've been thinking about how to get clive out of the pyvideo-data >>> repository and turn it into a separate project. One of the things I'm >>> grappling with is that we've defined the schema for the data in the >>> clive code. So then I think we need to move the schema definition into >>> the pyvideo-data repository and change clive so that it knows where to >>> find it. I haven't figured out a way to do that which makes me happy. >>> >>> On a related note, I've been thinking more about switching from my >>> schema representation to json-schema--something Paul suggested. >>> >>> Does anyone have experience with json-schema on this list? If you do, >>> I'd love to talk with you about the format as well as the tools >>> available. >>> >>> I think that's everything that's happened in the last month. >>> >>> Thank you everyone! >>> >>> /will >>> _______________________________________________ >>> 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: From lozinski at blogory.org Tue May 3 00:49:27 2016 From: lozinski at blogory.org (lozinski at blogory.org) Date: Tue, 03 May 2016 06:49:27 +0200 Subject: [pyvideo-data] Video Features Message-ID: Thank you for engaging in this discussion. It helps me think more clearly about the issues. There are a couple of different things that these videos need. A two paragraph introduction. One paragraph describes what is in the video. The other paragraph describes the quality of the speaker, the graphics, and the organization. Maybe describes the target audience. A hierarchical index position. Quality ratings. Youtube does up and down ratings. That makes sense in the general case. For technical presentations it would be nice to have two ratings, one on content, one on quality. Search. So that nothing related to snakes or Monty Python is returned. Google search can give you all the videos. This should just give you the "best" videos on any topic. Playlists. A list of recommendations for others. Queues. Videos to watch. Do you agree with that list? Am I missing anything? Maybe you would prefer keywords to hierarchy. And once you have what needs to be done, it is possilbe to prioritize the list. I am doing a talk on Blogory today. http://blogory.org/about/presentation.pdf/index#page=21 Although I may add a few more slides which would make the recommended start page move down a few pages. Regards Chris From shekay at pobox.com Tue May 3 11:17:08 2016 From: shekay at pobox.com (sheila miguez) Date: Tue, 3 May 2016 10:17:08 -0500 Subject: [pyvideo-data] Video Features In-Reply-To: References: Message-ID: Hi all, On Mon, May 2, 2016 at 11:49 PM, wrote: > Thank you for engaging in this discussion. It helps me think more clearly > about the issues. > There are a couple of different things that these videos need. > Is blogory an FLOSS project? People have been asking if there are open source projects out there which will use pyvideo-data. A two paragraph introduction. One paragraph describes what is in the video. > The other paragraph describes the quality of the speaker, the graphics, > and the organization. > Maybe describes the target audience. > I will give you my perspective as someone who worked with conference data. For the most part, I did not write descriptions for talks. I relied on data provided by conference organizers and speakers. Audio/Sound quality notes were added when people informed us of problems, or if we noticed them when adding videos. We didn't provide ratings of content and speakers. (I'm not interested in adding that to the pyvideo-data schema). I obtained descriptions of content programmatically if possible by writing simple clients for conference management systems or by scraping youtube. I used the youtube api at first, but the python youtube-dl library is simpler to work with from the point of view of user-friendliness. Asking everyone to get API keys to use our code is not friendly. I found that working with people who run a conference, or handle the recordings, resulted in good quality data. That takes a lot of labor. I helped run the SciPy 2014 conference management system (symposion)*. A couple of people (NextDayVideo) used the pyvideo API in their data pipeline. This doesn't scale. Not everyone knows everyone else or has time to volunteer for conferences and so on. * The SciPy speakers provide really nice talk descriptions and abstract. You can see examples here in some of the talks. http://pyvideo.org/category/51/scipy-2014 As you discovered, being tied to one provider (youtube) isn't the best. This is worth a separate post. A hierarchical index position. > I am not interested in this approach, so I don't have feedback for you. I'm more interested in tags, but I want the tags to be done sensibly. So, I am hoping that a small group of volunteers who are exports in taxonomies can give advice on the best way to do this. I met someone at PyOhio who mentioned the possibility of using pyvideo data for library science practicums (I hope they correct me if I got that wrong!). One of my friends told me about code4lib, and maybe we could ask for advice from that community as well. > Quality ratings. Youtube does up and down ratings. That makes sense in > the general case. > For technical presentations it would be nice to have two ratings, one on > content, one on quality. > > Search. So that nothing related to snakes or Monty Python is returned. > Google search can give you > all the videos. This should just give you the "best" videos on any topic. > > Playlists. A list of recommendations for others. > > Queues. Videos to watch. > Will did a good job explaining our thoughts on these. > And once you have what needs to be done, it is possilbe to prioritize the > list. > Priorities for FLOSS projects depend on what people choose to work on. It takes a lot of work to communicate/manage a community to encourage people to be organize. We didn't have a community manager. My advice is to be very flexible and make plans that account for a project being worked on by volunteers. Volunteers are interested in so many things, and will pick what to work on accordingly. Not everyone's interests and goals overlap. It's good to be flexible. -- shekay at pobox.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.logston at gmail.com Tue May 3 11:26:18 2016 From: paul.logston at gmail.com (Paul Logston) Date: Tue, 3 May 2016 11:26:18 -0400 Subject: [pyvideo-data] this week: markdown -> reST converter, schemas In-Reply-To: References: <1461765215.186944.591175665.318DC482@webmail.messagingengine.com>

Message-ID: Thanks Sheila. Also, I'll try and chop this into several small PRs to make the work lighter. Probably can chop this up on Thursday night. On Monday, May 2, 2016, sheila miguez wrote: > Hi all, > > Don't forget to help Paul get back to work on pytube would be to spend > time reviewing his pull request so that it can get merged. Many hands make > light work. > > https://github.com/pyvideo/pyvideo-data/pull/30 > > On Sun, May 1, 2016 at 9:43 PM, Paul Logston > wrote: > >> Hey Anand, >> >> Great to hear your willing to help. All the credit for pyvideo-data goes >> to Will and Sheila. As for a static site, I've been working on one called >> http://pytube.org/. Right now I've stopped work until pyvideo-data is >> converted to reST, but once that is done I plan to make the site more user >> friendly. I'll have a TODO list or file in the pytube.org repo and any >> help would be greatly appreciated. >> >> P >> >> On Thu, Apr 28, 2016 at 1:19 AM, Anand Reddy Pandikunta < >> anand21nanda at gmail.com >> > wrote: >> >>> Hi, >>> >>> I have been using PyVideo for about a year. I was surprised to know >>> that it might shutdown this year. So I joined ML to see if I can help. >>> >>> I will be interested in creating/maintaining static website. If anyone is >>> interested, we can start working on it. >>> >>> Thanks to Will, Paul & Sheila for building pyvideo-data >>> . >>> >>> >>> ------------------------- >>> Chillar Anand >>> www.avilpage.com >>> >>> >>> On Wed, Apr 27, 2016 at 7:23 PM, will kahn-greene >> > wrote: >>> >>>> Hi! >>>> >>>> I've noticed a bunch of new people subscribed to the list, but it's >>>> still intensely quiet. I'd love to know what's compelled people to join >>>> the list. Do you want to help with curating data? Do you have projects >>>> in mind to use the data for? Are you looking for people to work with on >>>> things that are important to you? Sheila and I would love to know so >>>> that we have a better feel for who's interested in what. I think the >>>> list is small enough that people could reply to the list. If you want to >>>> send to me directly, that's fine, too. willkg at bluesock.org >>>> >>>> >>>> Last month we decided to switch from Markdown to Restructured Text. Paul >>>> put together a PR with a script to convert the existing summaries and >>>> descriptions. The PR is here: >>>> >>>> https://github.com/pyvideo/pyvideo-data/pull/30 >>>> >>>> After that lands, we can convert summaries and descriptions and then >>>> move forward with that settled. Thank you, Paul! >>>> >>>> I've been thinking about how to get clive out of the pyvideo-data >>>> repository and turn it into a separate project. One of the things I'm >>>> grappling with is that we've defined the schema for the data in the >>>> clive code. So then I think we need to move the schema definition into >>>> the pyvideo-data repository and change clive so that it knows where to >>>> find it. I haven't figured out a way to do that which makes me happy. >>>> >>>> On a related note, I've been thinking more about switching from my >>>> schema representation to json-schema--something Paul suggested. >>>> >>>> Does anyone have experience with json-schema on this list? If you do, >>>> I'd love to talk with you about the format as well as the tools >>>> available. >>>> >>>> I think that's everything that's happened in the last month. >>>> >>>> Thank you everyone! >>>> >>>> /will >>>> _______________________________________________ >>>> 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 > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: From wickes1 at illinois.edu Tue May 3 15:17:46 2016 From: wickes1 at illinois.edu (Wickes, Elizabeth) Date: Tue, 3 May 2016 19:17:46 +0000 Subject: [pyvideo-data] Video Features In-Reply-To: References: Message-ID: The PyOhio person was me! Agreed about the tagging systems vs hierarchical. Content is rarely ever neat, and tags (when well designed) can be used to help wrangle the ?many? side of the classification relationship. Plus, at the end of the day, the groupings are designed to aid in discovery and not scientific classification. For example, if I give a tech talk on how I used a combination of Python, R, and Xpath to do a data science project, where would that live in a hierarchy? Hierarchies can create false silos of content. Tagging systems need to have good controlled vocabulary lists, but allow for flexibly adding labels to aid in discovery. Still happy to help find a practicum student to help develop taxonomies. There are also classes on developing and discussing taxonomies, so perhaps we can make the pitch about this as a class assignment. There are several library world mailing lists where people can provide feedback, but not necessarily to recruit volunteers. The library world is also pretty large on twitter, so you may be able to find some help there as well. I?ll save additional thoughts for when the taxonomy discussion comes up again. Elizabeth From: pyvideo-data > on behalf of sheila miguez > Date: Tuesday, May 3, 2016 at 10:17 AM To: "pyvideo-data at python.org" > Subject: Re: [pyvideo-data] Video Features Hi all, On Mon, May 2, 2016 at 11:49 PM, > wrote: Thank you for engaging in this discussion. It helps me think more clearly about the issues. There are a couple of different things that these videos need. Is blogory an FLOSS project? People have been asking if there are open source projects out there which will use pyvideo-data. A two paragraph introduction. One paragraph describes what is in the video. The other paragraph describes the quality of the speaker, the graphics, and the organization. Maybe describes the target audience. I will give you my perspective as someone who worked with conference data. For the most part, I did not write descriptions for talks. I relied on data provided by conference organizers and speakers. Audio/Sound quality notes were added when people informed us of problems, or if we noticed them when adding videos. We didn't provide ratings of content and speakers. (I'm not interested in adding that to the pyvideo-data schema). I obtained descriptions of content programmatically if possible by writing simple clients for conference management systems or by scraping youtube. I used the youtube api at first, but the python youtube-dl library is simpler to work with from the point of view of user-friendliness. Asking everyone to get API keys to use our code is not friendly. I found that working with people who run a conference, or handle the recordings, resulted in good quality data. That takes a lot of labor. I helped run the SciPy 2014 conference management system (symposion)*. A couple of people (NextDayVideo) used the pyvideo API in their data pipeline. This doesn't scale. Not everyone knows everyone else or has time to volunteer for conferences and so on. * The SciPy speakers provide really nice talk descriptions and abstract. You can see examples here in some of the talks. http://pyvideo.org/category/51/scipy-2014 As you discovered, being tied to one provider (youtube) isn't the best. This is worth a separate post. A hierarchical index position. I am not interested in this approach, so I don't have feedback for you. I'm more interested in tags, but I want the tags to be done sensibly. So, I am hoping that a small group of volunteers who are exports in taxonomies can give advice on the best way to do this. I met someone at PyOhio who mentioned the possibility of using pyvideo data for library science practicums (I hope they correct me if I got that wrong!). One of my friends told me about code4lib, and maybe we could ask for advice from that community as well. Quality ratings. Youtube does up and down ratings. That makes sense in the general case. For technical presentations it would be nice to have two ratings, one on content, one on quality. Search. So that nothing related to snakes or Monty Python is returned. Google search can give you all the videos. This should just give you the "best" videos on any topic. Playlists. A list of recommendations for others. Queues. Videos to watch. Will did a good job explaining our thoughts on these. And once you have what needs to be done, it is possilbe to prioritize the list. Priorities for FLOSS projects depend on what people choose to work on. It takes a lot of work to communicate/manage a community to encourage people to be organize. We didn't have a community manager. My advice is to be very flexible and make plans that account for a project being worked on by volunteers. Volunteers are interested in so many things, and will pick what to work on accordingly. Not everyone's interests and goals overlap. It's good to be flexible. -- shekay at pobox.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From lozinski at blogory.org Wed May 4 11:26:27 2016 From: lozinski at blogory.org (lozinski at blogory.org) Date: Wed, 04 May 2016 17:26:27 +0200 Subject: [pyvideo-data] Video Features In-Reply-To: References: Message-ID: <176a3d8349bbf8674a32beaed9c2b292@blogory.org> > Is blogory an FLOSS project? In the near future I want to release blogory as a docker container under a modified Mozilla license. That way installation is trivial, people can start entering content Through The Web, change the look and feel through the web, and modify the source code if they have to. That way everyone can run their own private blogory. I want to see lots of blogories out there. The traditional blogging tools are organized chronologically which makes less sense in software than organizing by subject. >> A hierarchical index position. > > I am not interested in this approach, so I don't have feedback for > you. > > I'm more interested in tags, A hierarchical index gives you a unique set of tags for every video. Edit the tags for any node, and the tags for a leaf node are updated accordingly. It is really the same concept. Chris From lozinski at blogory.org Wed May 4 11:40:20 2016 From: lozinski at blogory.org (lozinski at blogory.org) Date: Wed, 04 May 2016 17:40:20 +0200 Subject: [pyvideo-data] Video Features In-Reply-To: References: Message-ID: For example, if I give a tech talk on how > I used a combination of Python, R, and Xpath to do a data science > project, where would that live in a hierarchy? Excellent question. I talk about ontology and hierarchy, but really knowledge is a graph. Both the underlying persistent python database, and the javascript fancytree library support graphs of objects. So your talk on 4 topics would get listed in all 4 branches of the hierarchy(read graph). Blogory uses graphs internally, but I have not yet implemented knowledge graphs for content types, so for starters I would just do two links from the Python branch of the tree, one wherever R lives, the other wherever xpath lives. Eventually a single content item will be able to have multiple parents. Perhaps they would share the detailed content, but each have a separate short description. Yahoo directory used to have cross links between sections. That is also doable with current tools. So the current tools would look fine for an end user, but would not be as maintainable as having a shared content type. > > Still happy to help find a practicum student to help develop > taxonomies. There are also classes on developing and discussing > taxonomies, so perhaps we can make the pitch about this as a class > assignment. I would love to get help. Chris From code at logston.me Thu May 5 23:49:19 2016 From: code at logston.me (Paul Logston) Date: Thu, 5 May 2016 23:49:19 -0400 Subject: [pyvideo-data] Iceberg PR broken up Message-ID: Hey everybody, I've broken up the massive PR I issued earlier ( https://github.com/pyvideo/pyvideo-data/pull/30) with a bunch of smaller ones; 73 smaller ones to be exact. One PR for each category (ie. pycon-de-2011 or pygotham-2015). Hopefully this makes it easier to review. I've also created a script that will pump the descriptions and summaries for a given category out files in a tmp dir. This way, you don't have to scan the description and summary lines while they are still in the JSON file. https://gist.github.com/logston/51ab7fbe5edfb8fdf97fb088d09e03a0 Usage flow: 1. Save gist to local pyvideo-data repo (let's assume you save it to `json_to_rst.py`) 2. Check out given branch by category name (eg. `git checkout pycon-de-2011`) 3. Run script to populate tmp/ dir with files (eg. `python json_to_rst.py pycon-de-2011`) 4. Check the files in the new tmp/ dir found in the pyvideo-data repo. Ensure they contain valid reST. 5. Delete the tmp/ dir. You'd need to re-run steps 2 - 5 for each category you wanted to check. In case you just want to visually check the rendered reST rather than the source, here's the first google result for an online renderer: http://rst.ninjs.org/ All you would need to do is copy a file's contents into the editor section and make sure it looks okay in the preview section. Thanks for any and all help!! P -- Paul Logston plog.paullogston.com github.com/logston -------------- next part -------------- An HTML attachment was scrubbed... URL: From willkg at bluesock.org Fri May 6 20:40:16 2016 From: willkg at bluesock.org (will kahn-greene) Date: Fri, 06 May 2016 20:40:16 -0400 Subject: [pyvideo-data] Iceberg PR broken up In-Reply-To: References: Message-ID: <1462581616.695179.600592985.16D432B8@webmail.messagingengine.com> Easiest way to grab one to review is to comment in the PR saying something like, "I got this!" Then review it in your leisure and add comments for any issues you see. I'll keep tabs on things. Some comments we can spin off into separate issues. Some we might want to tackle in that PR. Sheila and I can merge any that are good to go. There's a lot of people on this list. If everyone took one PR, we'd get through the bulk of them pretty quickly. I've done two so far to see what reviewing them is like. Each took me about ten minutes. Thank you in advance! On Thu, May 5, 2016, at 11:49 PM, Paul Logston wrote: > Hey everybody, > > I've broken up the massive PR I issued earlier > (https://github.com/pyvideo/pyvideo-data/pull/30) with a bunch of > smaller ones; 73 smaller ones to be exact. One PR for each category > (ie.?pycon-de-2011 or pygotham-2015). Hopefully this makes it easier > to review. > > I've also created a script that will pump the descriptions and > summaries for a given category out files in a tmp dir. This way, you > don't have to scan the description and summary lines while they are > still in the JSON file. > > https://gist.github.com/logston/51ab7fbe5edfb8fdf97fb088d09e03a0 > > Usage flow: > > 1. Save gist to local pyvideo-data repo (let's assume you save it to > `json_to_rst.py`) > 2. Check out given branch by category name (eg. `git checkout?pycon-de- > 2011`) > 3. Run script to populate tmp/ dir with files (eg. `python > json_to_rst.py?pycon-de-2011`) > 4. Check the files in the new tmp/ dir found in the pyvideo-data repo. > Ensure they contain valid reST. > 5. Delete the tmp/ dir. > > You'd need to re-run steps 2 - 5 for each category you wanted > to check. > > In case you just want to visually check the rendered reST rather than > the source, here's the first google result for an online renderer: > http://rst.ninjs.org/ All you would need to do is copy a file's > contents into the editor section and make sure it looks okay in the > preview section. > > Thanks for any and all help!! > P > > > -- > Paul Logston > plog.paullogston.com[1] > github.com/logston > _________________________________________________ > pyvideo-data mailing list > pyvideo-data at python.org > https://mail.python.org/mailman/listinfo/pyvideo-data Links: 1. http://plog.paullogston.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From anand21nanda at gmail.com Mon May 9 04:26:55 2016 From: anand21nanda at gmail.com (Anand Reddy Pandikunta) Date: Mon, 9 May 2016 13:56:55 +0530 Subject: [pyvideo-data] Iceberg PR broken up In-Reply-To: <1462581616.695179.600592985.16D432B8@webmail.messagingengine.com> References: <1462581616.695179.600592985.16D432B8@webmail.messagingengine.com> Message-ID: Hi, I wrote a script to locally fetch all PR's checkout each branch validate data for that particular conference. Most of the data is fine. There are 39 files from 14 conferences which has some invalid data. Here is the log file which includes conference name, json file name, section name, content and name of error. I guess we can merge all PR's excluding these 14 conferences. chipy,djangocon-2012,djangocon-2013,europython-2011,europython-2014, kiwi-pycon-2014,pycon-au-2013,pycon-au-2015,pycon-us-2011,pycon-za-2015, pytexas-2011,pytexas-2015,scipy-2013,scipy-2014. Regards, Chillar Anand www.avilpage.com On Sat, May 7, 2016 at 6:10 AM, will kahn-greene wrote: > Easiest way to grab one to review is to comment in the PR saying something > like, "I got this!" Then review it in your leisure and add comments for any > issues you see. I'll keep tabs on things. Some comments we can spin off > into separate issues. Some we might want to tackle in that PR. Sheila and I > can merge any that are good to go. > > There's a lot of people on this list. If everyone took one PR, we'd get > through the bulk of them pretty quickly. I've done two so far to see what > reviewing them is like. Each took me about ten minutes. > > Thank you in advance! > > > On Thu, May 5, 2016, at 11:49 PM, Paul Logston wrote: > > Hey everybody, > > I've broken up the massive PR I issued earlier ( > https://github.com/pyvideo/pyvideo-data/pull/30) with a bunch of smaller > ones; 73 smaller ones to be exact. One PR for each category > (ie. pycon-de-2011 or pygotham-2015). Hopefully this makes it easier to > review. > > I've also created a script that will pump the descriptions and summaries > for a given category out files in a tmp dir. This way, you don't have to > scan the description and summary lines while they are still in the JSON > file. > > https://gist.github.com/logston/51ab7fbe5edfb8fdf97fb088d09e03a0 > > Usage flow: > > 1. Save gist to local pyvideo-data repo (let's assume you save it to > `json_to_rst.py`) > 2. Check out given branch by category name (eg. `git > checkout pycon-de-2011`) > 3. Run script to populate tmp/ dir with files (eg. `python > json_to_rst.py pycon-de-2011`) > 4. Check the files in the new tmp/ dir found in the pyvideo-data repo. > Ensure they contain valid reST. > 5. Delete the tmp/ dir. > > You'd need to re-run steps 2 - 5 for each category you wanted to check. > > In case you just want to visually check the rendered reST rather than the > source, here's the first google result for an online renderer: > http://rst.ninjs.org/ All you would need to do is copy a file's contents > into the editor section and make sure it looks okay in the preview section. > > Thanks for any and all help!! > P > > > -- > Paul Logston > 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willkg at bluesock.org Mon May 9 08:17:36 2016 From: willkg at bluesock.org (will kahn-greene) Date: Mon, 09 May 2016 08:17:36 -0400 Subject: [pyvideo-data] Iceberg PR broken up In-Reply-To: References: <1462581616.695179.600592985.16D432B8@webmail.messagingengine.com> Message-ID: <1462796256.1292908.602230497.2651F355@webmail.messagingengine.com> Awesome! Scripting this is a great idea! Can you post the script somewhere so that we can see it? I want to see what it's doing and see if that jives with what I've seen so far by merging the PyCon US conference changes. Thank you! /will On Mon, May 9, 2016, at 04:26 AM, Anand Reddy Pandikunta wrote: > Hi, > > I wrote a script to > locally fetch all PR's > checkout each branch > validate data for that particular conference. > > Most of the data is fine. > > There are 39 files from 14 conferences which has some invalid data. > > Here is the log file[1] which includes conference name, json file > name, section name, content and name of error. > > I guess we can merge all PR's excluding these 14 conferences. > > chipy,djangocon-2012,djangocon-2013,europython-2011,europython-2014, > kiwi-pycon-2014,pycon-au-2013,pycon-au-2015,pycon-us-2011,pycon- > za-2015, > pytexas-2011,pytexas-2015,scipy-2013,scipy-2014. > > > Regards, > Chillar Anand > www.avilpage.com > > > On Sat, May 7, 2016 at 6:10 AM, will kahn-greene > wrote: >> __ >> Easiest way to grab one to review is to comment in the PR saying >> something like, "I got this!" Then review it in your leisure and add >> comments for any issues you see. I'll keep tabs on things. Some >> comments we can spin off into separate issues. Some we might want to >> tackle in that PR. Sheila and I can merge any that are good to go. >> >> There's a lot of people on this list. If everyone took one PR, we'd >> get through the bulk of them pretty quickly. I've done two so far to >> see what reviewing them is like. Each took me about ten minutes. >> >> Thank you in advance! >> >> >> On Thu, May 5, 2016, at 11:49 PM, Paul Logston wrote: >>> Hey everybody, >>> >>> I've broken up the massive PR I issued earlier >>> (https://github.com/pyvideo/pyvideo-data/pull/30) with a bunch of >>> smaller ones; 73 smaller ones to be exact. One PR for each category >>> (ie.?pycon-de-2011 or pygotham-2015). Hopefully this makes it easier >>> to review. >>> >>> I've also created a script that will pump the descriptions and >>> summaries for a given category out files in a tmp dir. This way, you >>> don't have to scan the description and summary lines while they are >>> still in the JSON file. >>> >>> https://gist.github.com/logston/51ab7fbe5edfb8fdf97fb088d09e03a0 >>> >>> Usage flow: >>> >>> 1. Save gist to local pyvideo-data repo (let's assume you save it to >>> `json_to_rst.py`) >>> 2. Check out given branch by category name (eg. `git checkout?pycon-de- >>> 2011`) >>> 3. Run script to populate tmp/ dir with files (eg. `python >>> json_to_rst.py?pycon-de-2011`) >>> 4. Check the files in the new tmp/ dir found in the pyvideo-data >>> repo. Ensure they contain valid reST. >>> 5. Delete the tmp/ dir. >>> >>> You'd need to re-run steps 2 - 5 for each category you wanted to >>> check. >>> >>> In case you just want to visually check the rendered reST rather >>> than the source, here's the first google result for an online >>> renderer:?http://rst.ninjs.org/ All you would need to do is copy a >>> file's contents into the editor section and make sure it looks okay >>> in the preview section. >>> >>> Thanks for any and all help!! >>> P >>> >>> >>> >>> -- >>> Paul Logston >>> plog.paullogston.com[2] >>> 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 >> Links: 1. https://gist.github.com/ChillarAnand/f1e6a20d0c38999ec693f971765a9227 2. http://plog.paullogston.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From anand21nanda at gmail.com Mon May 9 09:45:54 2016 From: anand21nanda at gmail.com (Anand Reddy Pandikunta) Date: Mon, 9 May 2016 19:15:54 +0530 Subject: [pyvideo-data] Iceberg PR broken up In-Reply-To: <1462796256.1292908.602230497.2651F355@webmail.messagingengine.com> References: <1462581616.695179.600592985.16D432B8@webmail.messagingengine.com> <1462796256.1292908.602230497.2651F355@webmail.messagingengine.com> Message-ID: Hi Will, I have updated gist with the script . Try it out and see if it is working as expected. I also sent a PR to pyvideo repo for the same. Regards, Chillar Anand www.avilpage.com On Mon, May 9, 2016 at 5:47 PM, will kahn-greene wrote: > Awesome! Scripting this is a great idea! > > Can you post the script somewhere so that we can see it? I want to see > what it's doing and see if that jives with what I've seen so far by merging > the PyCon US conference changes. > > Thank you! > > /will > > > On Mon, May 9, 2016, at 04:26 AM, Anand Reddy Pandikunta wrote: > > Hi, > > I wrote a script to > locally fetch all PR's > checkout each branch > validate data for that particular conference. > > Most of the data is fine. > > There are 39 files from 14 conferences which has some invalid data. > > Here is the log file > which > includes conference name, json file name, section name, content and name of > error. > > I guess we can merge all PR's excluding these 14 conferences. > > chipy,djangocon-2012,djangocon-2013,europython-2011,europython-2014, > kiwi-pycon-2014,pycon-au-2013,pycon-au-2015,pycon-us-2011,pycon-za-2015, > pytexas-2011,pytexas-2015,scipy-2013,scipy-2014. > > > Regards, > Chillar Anand > www.avilpage.com > > > On Sat, May 7, 2016 at 6:10 AM, will kahn-greene > wrote: > > > Easiest way to grab one to review is to comment in the PR saying something > like, "I got this!" Then review it in your leisure and add comments for any > issues you see. I'll keep tabs on things. Some comments we can spin off > into separate issues. Some we might want to tackle in that PR. Sheila and I > can merge any that are good to go. > > There's a lot of people on this list. If everyone took one PR, we'd get > through the bulk of them pretty quickly. I've done two so far to see what > reviewing them is like. Each took me about ten minutes. > > Thank you in advance! > > > On Thu, May 5, 2016, at 11:49 PM, Paul Logston wrote: > > Hey everybody, > > I've broken up the massive PR I issued earlier ( > https://github.com/pyvideo/pyvideo-data/pull/30) with a bunch of smaller > ones; 73 smaller ones to be exact. One PR for each category > (ie. pycon-de-2011 or pygotham-2015). Hopefully this makes it easier to > review. > > I've also created a script that will pump the descriptions and summaries > for a given category out files in a tmp dir. This way, you don't have to > scan the description and summary lines while they are still in the JSON > file. > > https://gist.github.com/logston/51ab7fbe5edfb8fdf97fb088d09e03a0 > > Usage flow: > > 1. Save gist to local pyvideo-data repo (let's assume you save it to > `json_to_rst.py`) > 2. Check out given branch by category name (eg. `git > checkout pycon-de-2011`) > 3. Run script to populate tmp/ dir with files (eg. `python > json_to_rst.py pycon-de-2011`) > 4. Check the files in the new tmp/ dir found in the pyvideo-data repo. > Ensure they contain valid reST. > 5. Delete the tmp/ dir. > > You'd need to re-run steps 2 - 5 for each category you wanted to check. > > In case you just want to visually check the rendered reST rather than the > source, here's the first google result for an online renderer: > http://rst.ninjs.org/ All you would need to do is copy a file's contents > into the editor section and make sure it looks okay in the preview section. > > Thanks for any and all help!! > P > > > > -- > Paul Logston > 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 > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shekay at pobox.com Thu May 12 10:34:07 2016 From: shekay at pobox.com (sheila miguez) Date: Thu, 12 May 2016 09:34:07 -0500 Subject: [pyvideo-data] related_urls and the upcoming PyCon US Message-ID: I've opened an issue to recapture missing related_urls. They are available from api calls to pyvideo.org, but missing from the data dump. This can be recovered with scripting. I have details in the issue. We can gather consensus but I wouldn't let that block anyone from picking up the issue and trying it out. https://github.com/pyvideo/pyvideo-data/issues/111 In conjunction with this, I've posted on the pycon-av list to ask for volunteers who are already involved in running the av side of pycon. They are collecting transcripts and captions for the conference and I'd like to see those show up in related_links. Brandon Rhodes (yay! he's the conference chair) replied and said he would join. Once the pycon conferences posts videos, I expect he or another volunteer will open a pull request for it. They might need help getting the data all linked together. So, Heads up people! I suggest coordinating with Brandon so that we don't have duplicated effort. -- shekay at pobox.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.logston at gmail.com Mon May 16 00:56:33 2016 From: paul.logston at gmail.com (Paul Logston) Date: Mon, 16 May 2016 00:56:33 -0400 Subject: [pyvideo-data] More reST errors Message-ID: Hey everybody, I've been building some tools to render pyvideo data in to rst files that Pelican can turn into a static site. I've run into some reST validation errors and thought I'd share. https://github.com/pytube/pytube/blob/update-article-maker/errors.txt Most of those errors are actually "No date provided" errors. Feel free to ignore those as those are just for PyTube/Pelican. The rest of the errors (grep rst errors.txt) are reST parsing errors and I'll be whittling away at those over the next few weeks. Maybe done by PyCon! Let me know if you want to help correct some of these errors. We can divy up the work to avoid duplication of work. I plan on doing most edits by hand. Best, 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: From paul.logston at gmail.com Mon May 16 01:58:58 2016 From: paul.logston at gmail.com (Paul Logston) Date: Mon, 16 May 2016 01:58:58 -0400 Subject: [pyvideo-data] More reST errors In-Reply-To: References: Message-ID: Ps. I made a small script to open the reST portion of *.json files for easy editing: https://github.com/pytube/pytube/blob/update-article-maker/bin/edit.py Usage: python edit.py P On Mon, May 16, 2016 at 12:56 AM, Paul Logston wrote: > Hey everybody, > > I've been building some tools to render pyvideo data in to rst files that > Pelican can turn into a static site. I've run into some reST validation > errors and thought I'd share. > > https://github.com/pytube/pytube/blob/update-article-maker/errors.txt > > Most of those errors are actually "No date provided" errors. Feel free to > ignore those as those are just for PyTube/Pelican. The rest of the errors > (grep rst errors.txt) are reST parsing errors and I'll be whittling away at > those over the next few weeks. Maybe done by PyCon! > > Let me know if you want to help correct some of these errors. We can divy > up the work to avoid duplication of work. I plan on doing most edits by > hand. > > Best, > P > > -- > Paul Logston > (510) 755 - 4474 > paul.logston at gmail.com > plog.paullogston.com > github.com/logston > -- Paul Logston (510) 755 - 4474 paul.logston at gmail.com plog.paullogston.com github.com/logston -------------- next part -------------- An HTML attachment was scrubbed... URL: From shekay at pobox.com Mon May 16 12:40:37 2016 From: shekay at pobox.com (sheila miguez) Date: Mon, 16 May 2016 11:40:37 -0500 Subject: [pyvideo-data] Merge request for a new event! Message-ID: I am excited because someone made a PR with pyconca 2015 data! Brand new data! If someone hops on it, please leave a comment so that we know not to duplicate effort. -- shekay at pobox.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From willkg at bluesock.org Mon May 23 10:26:47 2016 From: willkg at bluesock.org (will kahn-greene) Date: Mon, 23 May 2016 10:26:47 -0400 Subject: [pyvideo-data] status: may 23rd, 2016; pycon us 2016; reST; help needed Message-ID: <1464013607.553077.616031481.2100E7AD@webmail.messagingengine.com> Hi! Status and reST ================= With a ton of help from Paul Logston and Paul Tremberth, we've switched all the summaries and descriptions for all the video data from Markdown to reStructuredText. There are a few things to be aware of: 1. it's not the case that everything parses perfectly 2. there are still issues with the formatting for some videos 3. we haven't added reST validation to the validator, so changes don't currently get tested when you submit pull requests Still, getting there! Thank you Paul and Paul! PyCon US 2016 =================== PyCon US 2016 is next week. We're still bootstrapping this project and there's a ton of stuff to do between getting the infrastructure to support the project to a better place and improving the data. Given that PyCon US is next week, I'm trying to figure out what the small list of things to focus on that have the highest impact for any work that people might be doing with pyvideo-data at PyCon. If you're planning to be at PyCon US 2016 and thinking about doing things with the data (sprint on adding new data?, sprint on fixing existing data?, sprint on building a static website?, sprint on improving an existing static website?, ...), I'd love two things from you: 1. what do you plan on doing at PyCon US 2016? 2. what changes can I and other people make that would make your PyCon US 2016 work better? Let us know soon. Perhaps today. The sooner the better. Help needed! =================== I need help with the following things: 1. Figuring out what to do with lightning talks. I started a discussion in issue #108. Following along and adding to that would be very helpful: https://github.com/pyvideo/pyvideo-data/issues/108 2. Sending out periodic status reports to the mailing list. A bunch of us are doing stuff. That's great. I want to send out status reports like this one probably more often than once-a-month but less often than once-a-week. They should highlight what's been done, who did the work and what we need help with. In this way, we all stay on the same page even if we're not paying attention to all the activity in GitHub and on IRC. I think a decent status report would take 10 minutes to throw together. Maybe skim GitHub and mailing list activity for the last couple of weeks and summarize it? Would you like to own this for the next month? If you were doing status reports every two weeks, that'd be 2 reports. If you want to work on it longer, that's cool. I think a month would help us a lot and help get the ball rolling. If you're interested, please let Sheila or me know. That's it for this installment! /will From paul.logston at gmail.com Tue May 24 11:04:50 2016 From: paul.logston at gmail.com (Paul Logston) Date: Tue, 24 May 2016 11:04:50 -0400 Subject: [pyvideo-data] status: may 23rd, 2016; pycon us 2016; reST; help needed In-Reply-To: <1464013607.553077.616031481.2100E7AD@webmail.messagingengine.com> References: <1464013607.553077.616031481.2100E7AD@webmail.messagingengine.com> Message-ID: Hey Will, I'll be at PyCon. 1. what do you plan on doing at PyCon US 2016? Not sure yet, but I'll be around for a day or two of sprints. 2. what changes can I and other people make that would make your PyCon US 2016 work better? Some descriptions and summaries are still not parseable. Would love to get that data cleaned up. Looking forward to meeting you all in person. Thanks for writing this all up. P On Mon, May 23, 2016 at 10:26 AM, will kahn-greene wrote: > Hi! > > Status and reST > ================= > > With a ton of help from Paul Logston and Paul Tremberth, we've switched > all the summaries and descriptions for all the video data from Markdown > to reStructuredText. > > There are a few things to be aware of: > > 1. it's not the case that everything parses perfectly > 2. there are still issues with the formatting for some videos > 3. we haven't added reST validation to the validator, so changes don't > currently get tested when you submit pull requests > > Still, getting there! Thank you Paul and Paul! > > > PyCon US 2016 > =================== > > PyCon US 2016 is next week. We're still bootstrapping this project and > there's a ton of stuff to do between getting the infrastructure to > support the project to a better place and improving the data. Given that > PyCon US is next week, I'm trying to figure out what the small list of > things to focus on that have the highest impact for any work that people > might be doing with pyvideo-data at PyCon. > > If you're planning to be at PyCon US 2016 and thinking about doing > things with the data (sprint on adding new data?, sprint on fixing > existing data?, sprint on building a static website?, sprint on > improving an existing static website?, ...), I'd love two things from > you: > > 1. what do you plan on doing at PyCon US 2016? > 2. what changes can I and other people make that would make your PyCon > US 2016 work better? > > Let us know soon. Perhaps today. The sooner the better. > > > Help needed! > =================== > > I need help with the following things: > > 1. Figuring out what to do with lightning talks. I started a discussion > in issue #108. Following along and adding to that would be very helpful: > https://github.com/pyvideo/pyvideo-data/issues/108 > > 2. Sending out periodic status reports to the mailing list. A bunch of > us are doing stuff. That's great. I want to send out status reports like > this one probably more often than once-a-month but less often than > once-a-week. They should highlight what's been done, who did the work > and what we need help with. In this way, we all stay on the same page > even if we're not paying attention to all the activity in GitHub and on > IRC. > > I think a decent status report would take 10 minutes to throw together. > Maybe skim GitHub and mailing list activity for the last couple of weeks > and summarize it? > > Would you like to own this for the next month? If you were doing status > reports every two weeks, that'd be 2 reports. If you want to work on it > longer, that's cool. I think a month would help us a lot and help get > the ball rolling. If you're interested, please let Sheila or me know. > > > That's it for this installment! > > /will > _______________________________________________ > 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: From shekay at pobox.com Tue May 24 13:12:04 2016 From: shekay at pobox.com (sheila miguez) Date: Tue, 24 May 2016 12:12:04 -0500 Subject: [pyvideo-data] status: may 23rd, 2016; pycon us 2016; reST; help needed In-Reply-To: References: <1464013607.553077.616031481.2100E7AD@webmail.messagingengine.com> Message-ID: On Tue, May 24, 2016 at 10:04 AM, Paul Logston wrote: > > Looking forward to meeting you all in person. Thanks for writing this all > up. > > I won't be there in person, but I will maintain a presence in irc. (if anyone is planning on pyohio this year, I often go there). -- shekay at pobox.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.logston at gmail.com Tue May 24 19:57:02 2016 From: paul.logston at gmail.com (Paul Logston) Date: Tue, 24 May 2016 19:57:02 -0400 Subject: [pyvideo-data] status: may 23rd, 2016; pycon us 2016; reST; help needed In-Reply-To: References: <1464013607.553077.616031481.2100E7AD@webmail.messagingengine.com>

Message-ID: Got it. I'll see if I can make it out this year. On Tue, May 24, 2016 at 1:12 PM, sheila miguez wrote: > > > On Tue, May 24, 2016 at 10:04 AM, Paul Logston > wrote: > >> >> Looking forward to meeting you all in person. Thanks for writing this all >> up. >> >> > I won't be there in person, but I will maintain a presence in irc. > > (if anyone is planning on pyohio this year, I often go there). > > > -- > 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: From shekay at pobox.com Thu May 26 11:08:32 2016 From: shekay at pobox.com (sheila miguez) Date: Thu, 26 May 2016 10:08:32 -0500 Subject: [pyvideo-data] Keeping up with conference activity Message-ID: Hi all, I don't remember if I've shared this before: https://twitter.com/PyvideoOrg/lists/python-conferences There's no one authoritative source for discovering when conferences are happening and posting videos, and I kept a list like the above to try and follow all the conference twitter accounts. I figure some of you may like to follow it to see if a conference you'd like to add is posting anything. cheers -- shekay at pobox.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From willkg at bluesock.org Thu May 26 11:14:02 2016 From: willkg at bluesock.org (will kahn-greene) Date: Thu, 26 May 2016 11:14:02 -0400 Subject: [pyvideo-data] Keeping up with conference activity In-Reply-To: References: Message-ID: <1464275642.390085.619597729.2566E3CB@webmail.messagingengine.com> Oo--I didn't even know about that. That's super handy. Thank you, Sheila! On Thu, May 26, 2016, at 11:08 AM, sheila miguez wrote: > Hi all, > I don't remember if I've shared this before: > > https://twitter.com/PyvideoOrg/lists/python-conferences > > There's no one authoritative source for discovering when conferences > are happening and posting videos, and I kept a list like the above to > try and follow all the conference twitter accounts. > > I figure some of you may like to follow it to see if a conference > you'd like to add is posting anything. > > cheers > > -- > shekay at pobox.com > _________________________________________________ > 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: From kevin.horn at gmail.com Thu May 26 11:34:59 2016 From: kevin.horn at gmail.com (Kevin Horn) Date: Thu, 26 May 2016 10:34:59 -0500 Subject: [pyvideo-data] Keeping up with conference activity In-Reply-To: <1464275642.390085.619597729.2566E3CB@webmail.messagingengine.com> References: <1464275642.390085.619597729.2566E3CB@webmail.messagingengine.com> Message-ID: This is very cool. FYI, PyTexas (@pytexas) appears to be missing from the list. On Thu, May 26, 2016 at 10:14 AM, will kahn-greene wrote: > Oo--I didn't even know about that. That's super handy. Thank you, Sheila! > > > On Thu, May 26, 2016, at 11:08 AM, sheila miguez wrote: > > Hi all, > I don't remember if I've shared this before: > > https://twitter.com/PyvideoOrg/lists/python-conferences > > There's no one authoritative source for discovering when conferences are > happening and posting videos, and I kept a list like the above to try and > follow all the conference twitter accounts. > > I figure some of you may like to follow it to see if a conference you'd > like to add is posting anything. > > cheers > > -- > shekay at pobox.com > *_______________________________________________* > 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 > > -- -- Kevin Horn -------------- next part -------------- An HTML attachment was scrubbed... URL: From willkg at bluesock.org Fri May 27 16:49:07 2016 From: willkg at bluesock.org (will kahn-greene) Date: Fri, 27 May 2016 16:49:07 -0400 Subject: [pyvideo-data] clive fixes; reST validation Message-ID: <1464382147.210213.620940337.1CF9FF05@webmail.messagingengine.com> Hi! I just landed a bunch of fixes to clive: 1. schema version support 2. fixes ordering when saving json files so that it's always stable 3. errors and warnings in validation 4. restructured text validation Of those, item 4 is helpful because there's a lot of text that doesn't validate currently. Per Sheila's recommendation, pull requests won't fail if there's invalid restructured text, but we now have a tool to identify issues. Item 2 is also really helpful because it means if you use load_json_files() and save_json_files() in clive, it'll maintain the ordering. That'll radically reduce the number of spurious changes in pull requests that have no real substance. I hope these help with anyone's PyCon US 2016 plans and plans for any other kind of data adding/changing! /will From paul.logston at gmail.com Mon May 30 21:08:12 2016 From: paul.logston at gmail.com (Paul Logston) Date: Mon, 30 May 2016 18:08:12 -0700 Subject: [pyvideo-data] PyCon BoF Message-ID: 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From cameron at pinkhatbeard.com Mon May 30 22:59:45 2016 From: cameron at pinkhatbeard.com (Cameron Dershem) Date: Mon, 30 May 2016 22:59:45 -0400 Subject: [pyvideo-data] PyCon BoF In-Reply-To: References: Message-ID: <15504c0b45e.be8d718c22160.8553763280266271263@pinkhatbeard.com> 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 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.logston at gmail.com Mon May 30 23:59:47 2016 From: paul.logston at gmail.com (Paul Logston) Date: Mon, 30 May 2016 20:59:47 -0700 Subject: [pyvideo-data] PyCon BoF In-Reply-To: <15504c0b45e.be8d718c22160.8553763280266271263@pinkhatbeard.com> References: <15504c0b45e.be8d718c22160.8553763280266271263@pinkhatbeard.com> Message-ID: Cool cool. I'll look out for that instead. On Mon, May 30, 2016 at 7:59 PM, Cameron Dershem 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 > * 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 > > -- Paul Logston (510) 755 - 4474 paul.logston at gmail.com plog.paullogston.com github.com/logston -------------- next part -------------- An HTML attachment was scrubbed... URL: From shekay at pobox.com Tue May 31 10:47:47 2016 From: shekay at pobox.com (sheila miguez) Date: Tue, 31 May 2016 09:47:47 -0500 Subject: [pyvideo-data] PyCon BoF In-Reply-To: <15504c0b45e.be8d718c22160.8553763280266271263@pinkhatbeard.com> References: <15504c0b45e.be8d718c22160.8553763280266271263@pinkhatbeard.com> Message-ID: Is the lightning talk online yet? On Mon, May 30, 2016 at 9:59 PM, Cameron Dershem 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 > * 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: From shekay at pobox.com Tue May 31 10:53:55 2016 From: shekay at pobox.com (sheila miguez) Date: Tue, 31 May 2016 09:53:55 -0500 Subject: [pyvideo-data] PyCon data collection (hi anyone doing sprints?) Message-ID: Hi all, This is the type of data I'd like to see made possible via our dataset, for all conferences. Not all conferences provide easily accessible schedule data with speaker names. One pyvideo-data goal is be able to scrape this data. So, those of you at pycon who want to work on pyvideo-data. Consider this use-case and how to make it easy to do with pyvideo-data, e.g. * how to make legitimate peripheral participation easy and meaningful. * how to make it easy for people to provide data. provide ways for people of all levels of experience to provide data, but don't try and do everything all at once. * how to make it easy for people to analyse data. e.g. have some jupyter notebooks to demonstrate how to do an analysis similar to the one in Jessica's tweet. https://twitter.com/jessicamckellar/status/737299461563502595 Hello from your @*PyCon* Diversity Chair. % PyCon talks by women: (2011: 1%), (2012: 7%), (2013: 15%), (2014/15: 33%), (2016: 40%). #*pycon2016* -- shekay at pobox.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.logston at gmail.com Tue May 31 17:35:32 2016 From: paul.logston at gmail.com (Paul Logston) Date: Tue, 31 May 2016 14:35:32 -0700 Subject: [pyvideo-data] PyCon data collection (hi anyone doing sprints?) In-Reply-To: References: Message-ID: ? On Tue, May 31, 2016 at 7:53 AM, sheila miguez wrote: > Hi all, > > This is the type of data I'd like to see made possible via our dataset, > for all conferences. Not all conferences provide easily accessible schedule > data with speaker names. One pyvideo-data goal is be able to scrape this > data. > > So, those of you at pycon who want to work on pyvideo-data. Consider this > use-case and how to make it easy to do with pyvideo-data, e.g. > > * how to make legitimate peripheral participation easy and meaningful. > * how to make it easy for people to provide data. provide ways for people > of all levels of experience to provide data, but don't try and do > everything all at once. > * how to make it easy for people to analyse data. e.g. have some jupyter > notebooks to demonstrate how to do an analysis similar to the one in > Jessica's tweet. > > https://twitter.com/jessicamckellar/status/737299461563502595 > Hello from your @*PyCon* Diversity Chair. % > PyCon talks by women: (2011: 1%), (2012: 7%), (2013: 15%), (2014/15: 33%), > (2016: 40%). #*pycon2016* > > -- > shekay at pobox.com > > _______________________________________________ > 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: