Re: Per-contributor focuses for next major release, hack sessions

Rather than explicitly track generations, I'd just do consistent hashing, where each disk has a weight proportional to its size (by default) or explicit configuration. On read, try its ideal location. If you miss, search N shards in parallel looking for it. Optionally enqueue a migration task. On

Re: Per-contributor focuses for next major release, hack sessions

I saw some activity on my ancient sharding merge request. I've been dusting that off and am actually trying to tackle the problem I've been stalled on all this time, which I'll describe here. The naive sharding approach in the current MR assumes the same shards will always exist. This sounds

Re: Per-contributor focuses for next major release, hack sessions

I'm going to look at building a web based rss reader ontop of perkeep. Maybe something that reminds me of Google reader. On Jan 9, 2018 3:44 PM, "Paul Lindner" wrote: > Okay, here goes short term: > - modernize our dependencies so it's easier to work well with other > related

Re: Per-contributor focuses for next major release, hack sessions

Okay, here goes short term: - modernize our dependencies so it's easier to work well with other related projects and infrastructure. - learn the block/kv backends, possibly implement for ethereum swarm and IPFS. - Promote, promote, promote; organize, organize, organize And of course my Long term

Re: Per-contributor focuses for next major release, hack sessions

On 8 January 2018 at 05:11, Will Norris wrote: > +1 to another meetup at LFNW... I'd be up for that. > > Things I'm hoping to accomplish: > - update site markup and css, both for some minor general cleanup but also > to make it render a bit better on mobile (I've been doing

Re: Per-contributor focuses for next major release, hack sessions

+1 to another meetup at LFNW... I'd be up for that. Things I'm hoping to accomplish: - update site markup and css, both for some minor general cleanup but also to make it render a bit better on mobile (I've been doing a lot of re-reading of the docs and code on my phone with a baby in arm in the

Re: Per-contributor focuses for next major release, hack sessions

What i will actually end up doing, and what I would love to land are of course only weakly correlated, but here are my most personal wishes anyway: -keep on making the sharing story better -add a Google Drive importer (after Google Photos is done) -fix all the flaky tests, and have a more

Re: Per-contributor focuses for next major release, hack sessions

Also, just doing lots of cleanups, fixing ancient & embarrassing things in the code. :) On Sun, Jan 7, 2018 at 9:45 AM, Brad Fitzpatrick wrote: > Good idea! > > First off, let's agree on the case of the new name: Perkeep, without a > capital 'K'. :-) > > My priorities in the

Re: Per-contributor focuses for next major release, hack sessions

Good idea! First off, let's agree on the case of the new name: Perkeep, without a capital 'K'. :-) My priorities in the short term: -- finish the project rename -- be more aggressive at unblocking people and reviewing code, or fixing it up when it's stalled but close -- work on the website,

Re: Per-contributor focuses for next major release, hack sessions

I'd like to help out. To get familiar with the code I've been fixing low hanging doc related fruit. I've seen some things as label:"Help Wanted", but I'm open to trying anything. https://github.com/perkeep/perkeep/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22 On Fri, Jan 5, 2018 at

Re: Per-contributor focuses for next major release, hack sessions

PerKeep perfect... Linuxfest Northwest 2018: "Message In A Bottle" LinuxFest is celebrating 19 years of service to the Free and Open Source community and we want you to be a part of it! Please join us by being a presenter at one of the largest, technically diverse, educational, and fun open