Profile cover photo
Profile photo
Jeff Mitchell
454 followers
454 followers
About
Jeff's interests
View all
Jeff's posts

Post has shared content

Post has attachment
They wouldn't let me pick both B and D...
Photo

Post has shared content

Post has attachment
The below text is copied more or less verbatim, but basically: if you are interested in Docker and want to attend a code-a-thon (for some good causes), or if you are interested in mentoring those that attend (with Git, FOSS generally, and especially Go!) then you may want to take a look.

One can assume that mentors will get cake, too.

==================

During the week of March 23rd, the Docker community will be hosting over a dozen open-source-a-thon parties around the world. At these parties the Docker core team and expert developers from the broader open source community will teach and guide participants on how to contribute to open source. 

Contributions to the project at these events and in the weeks following will count toward Docker’s donation to the Oceanic Society and its mission to conserve the habitat of Moby Dock and blue whales across the planet.

Contributors can:
  * Learn how to contribute to open source
  * Learn Go
  * Contribute regardless of their technical experience

Contributors will:
  * Get an awesome "Contributor" T-Shirt (while supplies last)
  * Help marine wildlife (a donation will be made for every contributor) 
  * Have a great time
  * Enjoy cake, food and drinks
  * Make a difference in the world

The event in Boston will be on March 25th.
You can find more details and RSVP at http://www.meetup.com/Docker-Boston/events/220936081/

Mentors will:
  * Help people with how to contribute to open source
  * Help with git
  * Mentor with code contributions
  * Get an awesome "Mentor" T-Shirt (while supplies last)
  * Help marine wildlife (a donation will be made for every mentor) 

If you are interested in mentoring then please RSVP on the meetup page and sign up to be a mentor at http://goo.gl/forms/TAFVpnh3K8

There will also be an online event the following week in the event that you are not able to participate in person or would like to help mentor online as well. 

More information will be available at http://docker.party in the upcoming days.

As you're probably aware, pictures taken in Hangouts have :nopm: in it, which causes them to fail syncing to ownCloud.

Here's the thing: having FolderSync rename them in transit was described as being "problematic from a sync consistency standpoint". I disagree with this. If I the user can create a filter that says (unlike now where a filter can simply prevent a file from syncing at all) "apply this transformation to files before upload", the sync will always be consistent when the filter is consistently applied.

If I the user change the application of that filter, I have changed the sync parameters, and should not expect consistency on the next sync.

The problem is when an application applies such transformations without user input, at a risk of (for example) overwriting files that already exist in the destination due to automatic renaming rules. This is probably why the ownCloud client on Android itself doesn't do any such thing, instead failing to upload such files (that and/or it's just one of the very many features that it lacks).

But FolderSync can (and should!) be better, because such transformations would be driven by the user. This means that a consistently applied filter would not only result in consistent syncs, but result in behavior that user expects. That makes it a feature, not a problem!

I saw an earlier suggestion about filtering those out and using a Tasker task to rename the files. I've poked at Tasker a bit but I'm a dummy and/or Tasker is just a beast and I can't figure out how to do it. I'm a programmer, but Tasker programming is a world of its own with weird variable behavior and not great ways to debug and show output, and your average FolderSync user is not going to be able to make it work.

Post has attachment
Us Jeffs gotta stick together. #marlboro  
Photo

As you're aware, pictures taken in Hangouts have :nopm: in it, which causes them to fail syncing to ownCloud.

Here's the thing: having FolderSync rename them in transit was described as being "problematic from a sync consistency standpoint". I disagree with this. If I the user can create a filter that says (unlike now where a filter can simply prevent a file from syncing at all) "apply this transformation to files before upload", the sync will always be consistent when the filter is consistently applied.

If I the user change the application of that filter, I have changed the sync parameters, and should not expect consistency on the next sync.

The problem is when an application applies such transformations without user input, at a risk of (for example) overwriting files that already exist in the destination due to automatic renaming rules. This is probably why the ownCloud client on Android itself doesn't do any such thing, instead failing to upload such files (that and/or it's just one of the very many features that it lacks).

But FolderSync can (and should!) be better, because such transformations would be driven by the user. This means that a consistently applied filter would not only result in consistent syncs, but result in behavior that user expects. That makes it a feature, not a problem!

I saw an earlier suggestion about filtering those out and using a Tasker task to rename the files. I've poked at Tasker a bit but I'm a dummy and/or Tasker is just a beast and I can't figure out how to do it. I'm a programmer, but Tasker programming is a world of its own with weird variable behavior and not great ways to debug and show output, and your average FolderSync user is not going to be able to make it work.

The next meetup will be on the 19th at Brightcove. Please check it out and RSVP over at Meetup (http://www.meetup.com/Boston-Go-lang-User-Group/events/219177031/)

An update about what's going on here. A separate meetup group was started over at Meetup (www.meetup.com/Boston-Go-lang-User-Group/) and after discussion with the founders there we've agreed to merge. We're going to:

* Keep the Boston Golang name
* Keep @BostonGolang on Twitter
* Keep the bostongolang GitHub organization (https://github.com/orgs/bostongolang)
* Keep http://bostongolang.org as a landing page
* Schedule meetups through the Meetup interface
* Host discussions, job postings, etc. here on the G+ community

Please welcome +Jai Singh  and Travis Johnson (link not working right for some reason) as organizers!

Thanks!

Post has attachment
14 votes
-
votes visible to Public
43%
Yes
57%
No
Wait while more posts are being loaded