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

[Adam Shannon]

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 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 focus:
> - Make Perkeep usable by typical users
> - Fulfill the 100 year promise, via economic and organizational changes.
> - Develop protocols and standards that enable archiving by default for
> major services and obsolete importers.
>
> On Sun, Jan 7, 2018 at 12:14 PM Mathieu Lonjaret <
> mathieu.lonja...@gmail.com> wrote:
>
>> 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 reliable CI (builds and
>> tests) setup overall
>>
>> And of course I would love for LFNW to happen again.
>>
>>
>>
>> On 7 January 2018 at 18:58, Brad Fitzpatrick  wrote:
>> > 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 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, especially more docs
>> >> -- fix the Google Photos importer
>> >> (https://github.com/perkeep/perkeep/issues/987)
>> >> -- focus on importers in general, and make Perkeep more user-friendly
>> by
>> >> making importers work out of the box
>> >> (https://github.com/perkeep/perkeep/issues/1005)
>> >> -- migrate away from SHA-1 (https://github.com/perkeep/
>> perkeep/issues/537)
>> >> -- triage the bug tracker more aggresively
>> >> -- help new contributors ramped up
>> >>
>> >> On Fri, Jan 5, 2018 at 5:24 PM, Eric Drechsel  wrote:
>> >>>
>> >>> Many open source projects have a tradition to kick off a new dev cycle
>> >>> with a thread where contributors list tasks/issues they are planning
>> to work
>> >>> on in the coming months.
>> >>>
>> >>> It seems like PerKeep has been building some momentum over the Winter,
>> >>> and I'm really curious to hear what people have on their personal
>> roadmaps,
>> >>> both core commiters and new/sometime contribs.
>> >>>
>> >>> I'll kick it off :D While I haven't been very involved in the past
>> year,
>> >>> I am interested to make more contributions. Here are the things I'm
>> keen to
>> >>> work on:
>> >>>
>> >>> Update this old change list exposing permanode IDs as a FUSE xattr
>> [1].
>> >>> Have build infrastructure produce Synology packages, or figure out
>> best
>> >>> practices for deploying to Synology using Docker etc [2].
>> >>> Write a client side example app/guide using the GopherJS data access
>> >>> layer but without using GopherJS for the app code.
>> >>>
>> >>> If this isn't currently possible I would like to work on making sure
>> the
>> >>> GopherJS blob exports a nice data access API to JS.
>> >>>
>> >>> Write additional content importers:
>> >>>
>> >>> Git repository fetcher
>> >>> Website crawler
>> >>>
>> >>> Work on maintainence/new features in the Web UI
>> >>>
>> >>>  [1] https://camlistore-review.googlesource.com/c/camlistore/+/2869
>> >>>  [2] https://github.com/camlistore/camlistore/issues/986
>> >>>
>> >>> Of course I'd be happy if anyone else wants to work on any of these
>> >>> features too :D
>> >>>
>> >>> Also, are there any PerKeep meetups/hack sessions planned? LinuxFestNW
>> >>> CFP is open till the end of the month... :)
>> >>>
>> >>> --
>> >>> best, Eric
>> >>> eric.pdxhub.org
>> >>>
>> >>> --
>> >>> You received this message because you are subscribed to the Google
>> Groups
>> >>> "Camlistore" group.
>> >>> To unsubscribe from this group and stop receiving emails from it,
>> send an
>> >>> email to camlistore+unsubscr...@googlegroups.com.
>> >>> For more options, visit https://groups.google.com/d/optout.
>> >>
>> >>
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> Groups
>> > "Camlistore" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> an
>> > email to camlistore+unsubscr...@googlegroups.com.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Camlistore" group.
>> To unsubscribe 

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

[Adam Shannon]

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 7:24 PM, Eric Drechsel  wrote:

> Many open source projects have a tradition to kick off a new dev cycle
> with a thread where contributors list tasks/issues they are planning to
> work on in the coming months.
>
> It seems like PerKeep has been building some momentum over the Winter, and
> I'm really curious to hear what people have on their personal roadmaps,
> both core commiters and new/sometime contribs.
>
> I'll kick it off :D While I haven't been very involved in the past year, I
> am interested to make more contributions. Here are the things I'm keen to
> work on:
>
>- Update this old change list exposing permanode IDs as a FUSE xattr
>[1].
>- Have build infrastructure produce Synology packages, or figure out
>best practices for deploying to Synology using Docker etc [2].
>- Write a client side example app/guide using the GopherJS data access
>layer but without using GopherJS for the app code.
>   - If this isn't currently possible I would like to work on making
>   sure the GopherJS blob exports a nice data access API to JS.
>- Write additional content importers:
>   - Git repository fetcher
>   - Website crawler
>- Work on maintainence/new features in the Web UI
>
>  [1] https://camlistore-review.googlesource.com/c/camlistore/+/2869
>  [2] https://github.com/camlistore/camlistore/issues/986
>
> Of course I'd be happy if anyone else wants to work on any of these
> features too :D
>
> Also, are there any PerKeep meetups/hack sessions planned? LinuxFestNW CFP
> is open till the end of the month... :)
>
> --
> best, Eric
> eric.pdxhub.org 
>
> --
> You received this message because you are subscribed to the Google Groups
> "Camlistore" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to camlistore+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Camlistore" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to camlistore+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.