Many thanks to those of you who replied to this. Matt -- I might well be interested in some web scraping; not for the next few weeks though, as I'm in the middle of a markingocalypse.
A quick bug report - on this page: http://software-carpentry.org/lessons.html the link to the "site" version of "controlling a quadcopter with your mind" is broken. In terms of the GitHub search tool, I'm a little disappointed to find out that it doesn't have some obvious features, like being able to filter out a regexp or respecting globbing. So, that immediately makes life a little harder for anyone trying to find all the lessons from GH. In terms of repos that don't seem to match the convention, I found these: web-app-python https://github.com/swcarpentry/web-app-python web-data-python https://github.com/swcarpentry/web-data-python make-condensed-reproduce-paper https://github.com/swcarpentry/make-condensed-reproduce-paper modern-scientific-authoring https://github.com/swcarpentry/modern-scientific-authoring and I think that's it, except for the *-extras and capstone-* repositories, which I guess are intentional, although I notice that the capstone-novice-spreadsheet-biblio repo /does/ match the convention. The four repos above do not appear on the lessons.html page, so perhaps they are just no longer used? Thanks, Sarah On Fri, Apr 17, 2015 at 6:41 PM, Matt Davis <[email protected]> wrote: > Forwarding a message I sent directly to Sarah: > > Hi Sarah, > > We do have a naming scheme, but there may be lessons to which it has not > been applied. The scheme is topic-level-disambiguation. For example there's > python-novice-inflammation and python-novice-turtle. To find all the shell > related repositories you can search for "shell" at > https://github.com/swcarpentry, or to find all the novice lessons you can > search for "novice". I'm not sure what's up with the > modern-scientific-authoring repo, but definitely all of our commonly used > workshop lessons should follow the naming scheme. Let me know of any others > that don't. > > On a related topic, I've been interested in building a way to index our > lessons by scraping information from the repos using Python. Is that > something you'd be interested in working on? > > Best, > Matt > > On Fri, Apr 17, 2015 at 5:05 AM Sarah Mount <[email protected]> wrote: > >> Hi Matt, >> >> Just looking through the repositories, I notice that it isn't necessarily >> clear which repositories contain lessons. Some are titles .*novice.* and >> similar, but things like "modern-scientific-authoring" have nothing in the >> title to say "this is a lesson". Since there are many repos that are not >> lessons, it would be nice to be able to say to GitHub "give me all the >> lesson repos" or "give me all the workshops" or similar via the search >> tool. >> >> Are there any plans to impose a consistent naming scheme? >> >> Regards, >> >> Sarah >> >> On Tue, Apr 14, 2015 at 7:26 PM, Matt Davis <[email protected]> wrote: >> >>> Hi everyone, >>> >>> I made the intended changes to the Software Carpentry GitHub >>> organization's teams [1] this morning. Maintainers have been added to small >>> teams with specific access to the repos they maintain. Hopefully this will >>> reduce the amount of unnecessary email going out to people from GitHub. If >>> you're currently receiving more GitHub email than you'd like you may find >>> our blog post on managing GitHub notifications useful: >>> http://software-carpentry.org/blog/2015/02/managing-github-notifications-2015-02-19.html >>> . >>> >>> If you find anything amiss after this reshuffle please don't hesitate to >>> let me know. >>> >>> Best, >>> Matt >>> >>> [1]: https://github.com/orgs/swcarpentry/teams >>> >>> On Mon, Apr 13, 2015 at 11:45 AM Matt Davis <[email protected]> wrote: >>> >>>> Hi everyone, >>>> >>>> Over the next couple days Gabriel Devenyi and I will be reorganizing >>>> the teams [1] within the Software Carpentry organization on GitHub. Our >>>> goal is make it so that members are not automatically signed up for >>>> notifications for every new repo within the organization. (Anyone will >>>> still be able to sign up for notifications on a public repo by going to the >>>> repo page and "watching" it [2].) >>>> >>>> We'll be creating teams specifically for topic maintainers so they can >>>> be assigned to their respective repos. All SWC members will be part of a >>>> large team with read-only access. This is mostly symbolic since everyone >>>> already has read access to our public repos, but we want the SWC logo to >>>> show up on your profiles. :) >>>> >>>> If everything goes according to plan you shouldn't notice much, though >>>> GitHub may send you an email or two, especially if you're a topic >>>> maintainer. >>>> >>>> If you notice anything amiss that you think may be related to this >>>> reorganization, please don't hesitate to get in touch with me and Gabriel. >>>> >>>> Best, >>>> Matt >>>> >>>> [1]: https://github.com/orgs/swcarpentry/teams >>>> [2]: https://help.github.com/articles/watching-repositories/ >>>> >>> >>> _______________________________________________ >>> Discuss mailing list >>> [email protected] >>> >>> http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org >>> >> >> >> >> -- >> Dr. Sarah Mount, Senior Lecturer, University of Wolverhampton >> website: http://www.snim2.org/ >> twitter: @snim2 >> > -- Dr. Sarah Mount, Senior Lecturer, University of Wolverhampton website: http://www.snim2.org/ twitter: @snim2
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
