Rasterio: Rasterio Sprint at PyCon

[sgillies]

This ticket is for organizing the Rasterio/geospatial sprint at PyCon. I'm going to maintain a list of resources and instructions at https://github.com/mapbox/rasterio/wiki/2016-PyCon-Sprint and https://github.com/Toblerity/Fiona/wiki/2016-PyCon-Sprint (content coming soon) so that we're all more or less on the same page and so that new contributors can hit the ground running.

In comments below I'll try to get a tally of in-person and remote participants. Participation in the sprints is free, you don't even need to be signed up for the conference. It's paid for by sponsors – like Mapbox. :smile: :raised_hands:

Damon Burgett (@dnomadb) and I will be at the sprints June 2-4 (leaving late on that Saturday night).

From the sprints page, here is our agenda:

Goals for the sprint include a Rasterio 1.0 release and solid support for the latest and greatest version of GDAL in each project (Rasterio and Fiona). We're also interested in helping developers of other projects learn to use Rasterio and Fiona. See the issue trackers of Rasterio and Fiona for sprint plans.

Suggestions for the agenda are welcome in comments below.

[sgillies]

in-person participants

Make a positive reaction to this comment if you are planning to participate in person.

[sgillies]

remote participants

Make a positive reaction to this comment if you would like to participate remotely via IRC or some other channel.

[eseglem]

TBD, if our travel money comes through, and I can be there, I will. Otherwise I will try and hang out remotely.

[robintw]

I'd be keen to be involved remotely, although I'll have to be a bit limited in how much time I can spend on it as I'm also meant to be working on my 'proper job'. Do we have a list of major tasks yet?

[sgillies]

@robintw I've been roughly categorizing issues by their level of effort and expertise needed: https://github.com/mapbox/rasterio/wiki/2016-PyCon-Sprint#open-issues. I think "beginner" issues could be good for someone who is time limited, like you. We're going to let people work on the stuff that is interesting to them, scratch their own itches so to speak. I hope to write some code, but my main duty is to help sprinters find the right tasks and succeed at them. We'll have a channel (IRC or Slack) set up by the middle of next week where I can help remote sprinters, I'll post the link here and in the wiki.

[robintw]

That sounds great, thanks.

What is the status with hosting the docs properly? The issue (#592) hasn't been categorised for the sprint, but I think it's something really important (I was certainly 'turned off' by the lack of easily browsable docs). Is this something that could be worked on at the sprint? I'd be happy to help with that - and it really would scratch one of my itches!

I see some of the other issues categorised for the sprint are to improve/update docs in various ways - it'd be a shame if people did that but the docs weren't actually hosted anywhere!

[grovduck]

I'll probably be lurking as time allows - I'd be happy to help with some of the easier tasks.

[brendan-ward]

For those of you at PyCon, we're aiming to start at 8:30 AM on Thursday; check the board outside the Portland Ballroom. For those of you remote, jump on the Slack channel in #734 and we'll hopefully show up there about the same time.

[geowurster]

I'll be in and out most of the day but will be available once I leave work (EST) but will leave Slack open. Time allowing, I should be able to review some small to mid-size PR's during the day. Feel free to throw stuff my way and I will decline if necessary.

[sgillies]

@geowurster Great! We'll count on you for some review.

[ghost]

I'll be around today and some of tomorrow. I'd like to help as much as I can remotely. Unfortunately I don't have a slack account but I'll email @perrygeo now.

[perrygeo]

🎉 Great sprint everyone!