New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mozilla Global Sprint 2017, 1-2 June 2017 #23

Closed
drjwbaker opened this Issue Mar 13, 2017 · 22 comments

Comments

Projects
None yet
6 participants
@drjwbaker

drjwbaker commented Mar 13, 2017

SUPERCEDED AT #23 (comment)

Issue to setup inital organisation of Library Carpentry activities at Mozilla Global Sprint 2017 https://science.mozilla.org/programs/events/global-sprint-2017

Initial proposed work:

Etherpad to be used for coordinating.

James and Belinda to coordinate.

@weaverbel

This comment has been minimized.

Show comment
Hide comment
@weaverbel

weaverbel Mar 13, 2017

Collaborator

Hi @drjwbaker I have created the etherpad and tweeted it. If someone could re-tweet from LibCarpentry that would be good too. I'll talk to MSL - project calls are not open yet but we have everything we need to register since we created all the right stuff last time. Happy to sort that. We should try to get this message out to archivists too as some seem keen to contribute (see the chatroom) http://pad.software-carpentry.org/lc2017

Collaborator

weaverbel commented Mar 13, 2017

Hi @drjwbaker I have created the etherpad and tweeted it. If someone could re-tweet from LibCarpentry that would be good too. I'll talk to MSL - project calls are not open yet but we have everything we need to register since we created all the right stuff last time. Happy to sort that. We should try to get this message out to archivists too as some seem keen to contribute (see the chatroom) http://pad.software-carpentry.org/lc2017

@jezcope

This comment has been minimized.

Show comment
Hide comment
@jezcope

jezcope Mar 28, 2017

Collaborator

More possible work to be done from various discussions:

  • Revamp the Python lesson to be more realistic for the audience (maybe split into multiple lessons?)
  • Free workshop data from the shackles of Google Sheets
    • Rendered on the website
    • Downloadable in machine-readable form e.g. JSON
  • Develop material for archivists (and improve comms to non-librarian information professionals)
Collaborator

jezcope commented Mar 28, 2017

More possible work to be done from various discussions:

  • Revamp the Python lesson to be more realistic for the audience (maybe split into multiple lessons?)
  • Free workshop data from the shackles of Google Sheets
    • Rendered on the website
    • Downloadable in machine-readable form e.g. JSON
  • Develop material for archivists (and improve comms to non-librarian information professionals)
@weaverbel

This comment has been minimized.

Show comment
Hide comment
@weaverbel

weaverbel Mar 28, 2017

Collaborator

@drjwbaker @jezcope I think we need to start drafting a plan of work for the sprint - tell people exactly what we want to get done, e.g. bug fixes like typos, errors; melding all the SQL lessons into one; badging up Tom's web scraping lesson for LC; maybe also badging Brenda's Beautiful Soup Python web scraping lesson as an alternative web scraping lesson; @ostephens 's XSLT lesson dev if that is happening; and also fixing the Python lesson - we will have more intel about that once we have had our meetup. Shall I start a Google Doc for the sprint - we could use markdown formatting so we can post it on GitHub nearer the time. Or shall I just start the document on GitHub? If so, which will be the repo people go to to find out about the sprint work? Is it github.com/LibraryCarpentry? Happy to get going on that - I could paste these ideas in for a start and then we can start to flesh out proper instructions - i.e. forking, keeping PRs small (one or two changes at a time), raising issues, using the chatroom.

Collaborator

weaverbel commented Mar 28, 2017

@drjwbaker @jezcope I think we need to start drafting a plan of work for the sprint - tell people exactly what we want to get done, e.g. bug fixes like typos, errors; melding all the SQL lessons into one; badging up Tom's web scraping lesson for LC; maybe also badging Brenda's Beautiful Soup Python web scraping lesson as an alternative web scraping lesson; @ostephens 's XSLT lesson dev if that is happening; and also fixing the Python lesson - we will have more intel about that once we have had our meetup. Shall I start a Google Doc for the sprint - we could use markdown formatting so we can post it on GitHub nearer the time. Or shall I just start the document on GitHub? If so, which will be the repo people go to to find out about the sprint work? Is it github.com/LibraryCarpentry? Happy to get going on that - I could paste these ideas in for a start and then we can start to flesh out proper instructions - i.e. forking, keeping PRs small (one or two changes at a time), raising issues, using the chatroom.

@ostephens

This comment has been minimized.

Show comment
Hide comment
@ostephens

ostephens Mar 29, 2017

I'm not sure I intended to put my hand up for XSLT lesson dev!

I'd like to see the 'Archive Carpentry' idea on the list and I'd be interested in working on either that, or on getting a web scraping lesson done.

I think getting a public document for the sprint is a good idea. Google Docs works for me, and might let us source ideas from a wider range of people than doing it straight into GitHub. Etherpad could also work

ostephens commented Mar 29, 2017

I'm not sure I intended to put my hand up for XSLT lesson dev!

I'd like to see the 'Archive Carpentry' idea on the list and I'd be interested in working on either that, or on getting a web scraping lesson done.

I think getting a public document for the sprint is a good idea. Google Docs works for me, and might let us source ideas from a wider range of people than doing it straight into GitHub. Etherpad could also work

@ostephens

This comment has been minimized.

Show comment
Hide comment
@ostephens

ostephens Mar 29, 2017

Digging out some previous discussion about XSLT/XPath from the Gitter chat, I think we boiled down to two use cases - quote myself:

@drjwbaker So I think from @timtomch we have the web scraping/HTML parsing use case
@drjwbaker and from Nora we have the TEI processing /Digital Humanities use case

Potentially I'd add to these:

  • Using XSLT/XPath with EAD
  • Using XSLT/XPath with MODS

ostephens commented Mar 29, 2017

Digging out some previous discussion about XSLT/XPath from the Gitter chat, I think we boiled down to two use cases - quote myself:

@drjwbaker So I think from @timtomch we have the web scraping/HTML parsing use case
@drjwbaker and from Nora we have the TEI processing /Digital Humanities use case

Potentially I'd add to these:

  • Using XSLT/XPath with EAD
  • Using XSLT/XPath with MODS
@weaverbel

This comment has been minimized.

Show comment
Hide comment
@weaverbel

weaverbel Mar 29, 2017

Collaborator

Sorry @ostephens I didn't mean to dob you in - I just vaguely recalled XSLT being raised. I think we should concentrate on the other stuff but didn't want to discourage people from cracking on with new stuff if that is what floats their boat. Happy to go with a Google Doc - we can lodge it in GitHub once the outline has been firmed up.

Collaborator

weaverbel commented Mar 29, 2017

Sorry @ostephens I didn't mean to dob you in - I just vaguely recalled XSLT being raised. I think we should concentrate on the other stuff but didn't want to discourage people from cracking on with new stuff if that is what floats their boat. Happy to go with a Google Doc - we can lodge it in GitHub once the outline has been firmed up.

@drjwbaker

This comment has been minimized.

Show comment
Hide comment
@drjwbaker

drjwbaker Mar 29, 2017

Thus far we have:

lessons

admin

drjwbaker commented Mar 29, 2017

Thus far we have:

lessons

admin

@timtomch

This comment has been minimized.

Show comment
Hide comment
@timtomch

timtomch Mar 29, 2017

I'm unfortunately not able to participate in the sprint but I will endeavour to cleanup the webscraping lesson before that. Also the XPath section of that lesson was mainly written by @kimpham54 who might be interested in doing more XPath/XSLT stuff.

timtomch commented Mar 29, 2017

I'm unfortunately not able to participate in the sprint but I will endeavour to cleanup the webscraping lesson before that. Also the XPath section of that lesson was mainly written by @kimpham54 who might be interested in doing more XPath/XSLT stuff.

@jezcope

This comment has been minimized.

Show comment
Hide comment
@jezcope

jezcope Mar 29, 2017

Collaborator

@weaverbel 👍 to Google Doc, unless you want to try one of the options listed here (shameless plug): Tools for collaborative markdown editing

Collaborator

jezcope commented Mar 29, 2017

@weaverbel 👍 to Google Doc, unless you want to try one of the options listed here (shameless plug): Tools for collaborative markdown editing

@ccronje

This comment has been minimized.

Show comment
Hide comment
@ccronje

ccronje Mar 29, 2017

Collaborator

If you want to get from Google Docs to markdown post-sprint, the Export as Markdown add-on is pretty neat (nice way of liberating Word docs too via Google Docs upload).

Collaborator

ccronje commented Mar 29, 2017

If you want to get from Google Docs to markdown post-sprint, the Export as Markdown add-on is pretty neat (nice way of liberating Word docs too via Google Docs upload).

@weaverbel

This comment has been minimized.

Show comment
Hide comment
@weaverbel

weaverbel Mar 30, 2017

Collaborator

@ostephens @drjwbaker @ccronje I've just been invited to do a one-day LC workshop at an archivists' conference in Australia in September. All the more reason to get some archivist input to the sprint to help inform that workshop. I was thinking of creating a short Google form to ask archivists what they would like to see in our lessons to make them more relevant to their needs. We could all tweet that form link and maybe get some input that might translate into workable sprint ideas (and maybe attract some keen people to be part of the sprint). Thoughts?

Collaborator

weaverbel commented Mar 30, 2017

@ostephens @drjwbaker @ccronje I've just been invited to do a one-day LC workshop at an archivists' conference in Australia in September. All the more reason to get some archivist input to the sprint to help inform that workshop. I was thinking of creating a short Google form to ask archivists what they would like to see in our lessons to make them more relevant to their needs. We could all tweet that form link and maybe get some input that might translate into workable sprint ideas (and maybe attract some keen people to be part of the sprint). Thoughts?

@timtomch

This comment has been minimized.

Show comment
Hide comment
@timtomch

timtomch Mar 30, 2017

@weaverbel that echoes some of the comments heard this spring at code4lib in LA. I have a couple of archivists friends that I know would be eager to contribute their thoughts. Google form is a good idea.

timtomch commented Mar 30, 2017

@weaverbel that echoes some of the comments heard this spring at code4lib in LA. I have a couple of archivists friends that I know would be eager to contribute their thoughts. Google form is a good idea.

@weaverbel

This comment has been minimized.

Show comment
Hide comment
@weaverbel

weaverbel Mar 30, 2017

Collaborator

Thanks @timtomch I might draft a form and post it to the chat room for comment before I make it live.

Collaborator

weaverbel commented Mar 30, 2017

Thanks @timtomch I might draft a form and post it to the chat room for comment before I make it live.

@weaverbel

This comment has been minimized.

Show comment
Hide comment
@weaverbel

weaverbel Mar 31, 2017

Collaborator

OK, @ostephens @timtomch @drjwbaker @jezcope @ccronje I have drafted a form for archivists - big enthusiasm here to get this out to archivists - what do people think of the questions? Happy to tweak. https://docs.google.com/forms/d/e/1FAIpQLSdc9RHNmgffnt9UtLfgIhS_MGUzh0wh-HQNX24wBz5c4mcf1g/viewform

Collaborator

weaverbel commented Mar 31, 2017

OK, @ostephens @timtomch @drjwbaker @jezcope @ccronje I have drafted a form for archivists - big enthusiasm here to get this out to archivists - what do people think of the questions? Happy to tweak. https://docs.google.com/forms/d/e/1FAIpQLSdc9RHNmgffnt9UtLfgIhS_MGUzh0wh-HQNX24wBz5c4mcf1g/viewform

@drjwbaker

This comment has been minimized.

Show comment
Hide comment
@drjwbaker

drjwbaker Mar 31, 2017

I like it. I also approve of the use of 'town' rather than 'city' :)

drjwbaker commented Mar 31, 2017

I like it. I also approve of the use of 'town' rather than 'city' :)

@ostephens

This comment has been minimized.

Show comment
Hide comment
@ostephens

ostephens Mar 31, 2017

+1

Possibly more direct question about whether they would be willing/able to participate in the sprint?

ostephens commented Mar 31, 2017

+1

Possibly more direct question about whether they would be willing/able to participate in the sprint?

@weaverbel

This comment has been minimized.

Show comment
Hide comment
@weaverbel

weaverbel Mar 31, 2017

Collaborator

Ok @ostephens - done

Collaborator

weaverbel commented Mar 31, 2017

Ok @ostephens - done

@ccronje

This comment has been minimized.

Show comment
Hide comment
@ccronje

ccronje Apr 4, 2017

Collaborator

I'd like to work on OpenRefine for the Sprint. I could start with the issues on making episodes more granular. There is a bigger discussion to be had though, about adding new examples and the length of workshop. OpenRefine is a good candidate for an Intro/Advanced workshop split. Advanced could explore more GREL and API examples (parsing JSON etc). @ostephens also mentioned XPath wrt Jython on GItter. We could shift the current advanced episode over and expand with examples. Too much to resolve in a Sprint? ;-) Happy to chip away on the smaller things.

Collaborator

ccronje commented Apr 4, 2017

I'd like to work on OpenRefine for the Sprint. I could start with the issues on making episodes more granular. There is a bigger discussion to be had though, about adding new examples and the length of workshop. OpenRefine is a good candidate for an Intro/Advanced workshop split. Advanced could explore more GREL and API examples (parsing JSON etc). @ostephens also mentioned XPath wrt Jython on GItter. We could shift the current advanced episode over and expand with examples. Too much to resolve in a Sprint? ;-) Happy to chip away on the smaller things.

@drjwbaker

This comment has been minimized.

Show comment
Hide comment
@drjwbaker

drjwbaker Apr 4, 2017

@ccronje Given how much chatter we've had around the Refine lesson, it strikes me that it would be sensible to use the sprint to resolve (or at set out a plan for resolving) these nagging issues. I'll leave you as OR maintainers to decide how/what.

drjwbaker commented Apr 4, 2017

@ccronje Given how much chatter we've had around the Refine lesson, it strikes me that it would be sensible to use the sprint to resolve (or at set out a plan for resolving) these nagging issues. I'll leave you as OR maintainers to decide how/what.

@weaverbel

This comment has been minimized.

Show comment
Hide comment
@weaverbel

weaverbel Apr 18, 2017

Collaborator

Should we try to adapt this Contributor guide from Data Carpentry to describe the work for our sprint ?
https://github.com/datacarpentry/lesson-release/blob/master/how-to-contribute.md

Collaborator

weaverbel commented Apr 18, 2017

Should we try to adapt this Contributor guide from Data Carpentry to describe the work for our sprint ?
https://github.com/datacarpentry/lesson-release/blob/master/how-to-contribute.md

@ccronje

This comment has been minimized.

Show comment
Hide comment
@ccronje
Collaborator

ccronje commented Apr 18, 2017

@weaverbel

This comment has been minimized.

Show comment
Hide comment
@weaverbel

weaverbel Apr 18, 2017

Collaborator

No @ccronje I hadn't seen that but it looks good ! We probably need a sprint to work out how to write the CONTRIBUTING.md for the sprint ;-)

Collaborator

weaverbel commented Apr 18, 2017

No @ccronje I hadn't seen that but it looks good ! We probably need a sprint to work out how to write the CONTRIBUTING.md for the sprint ;-)

@weaverbel weaverbel referenced this issue Apr 18, 2017

Closed

Extending Library Carpentry #35

9 of 9 tasks complete

@drjwbaker drjwbaker closed this Jun 6, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment