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

[Will Norris]

+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 wee
hours of the night, so would love to make this a slightly better
experience).  Also, some minor doc cleanup that I've run across along the
way.
 - work on a chrome os filesystem provider (#1017
).  I've been using a
chromebook as my primary machine for close to a year now, so would love to
be able to access files from the native Files app.  This may end up being
more ambitious than I have time to commit to it right now, but I'd like to
see how far I can get.

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/pe
> rkeep/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 from this group and stop receiving emails from it, send an
> 

Re: domain name in website/godoc.org

[Will Norris]

On Fri, Jan 5, 2018 at 2:22 PM, Mathieu Lonjaret <mathieu.lonja...@gmail.com
> wrote:

> I'm confused. Are you talking about what is now:
>
> domainNames = []string{"perkeep.org", "camlistore.org"}
>
> in website/godoc.go?
>
> (it became domainNames in 02938281318c8dc1fdb0e7a46b543fb7e583a854)
>
> As far as i can tell, we need the domain to:
>
> 1) verify that we're serving only for one of these two domains (which
> might be overkill, as i think we already filter for that before
> reaching this point)
>

yeah, I think this is overkill.  And also makes it a little harder to test
this on localhost when developing :)


> 2) being able to strip it out of the path, and derive the part of the
> import path that is a "filepath" (as opposed to a domain name).
>
> I think we're inheriting this second point from the logic of the go
> stdlib godoc, since we copied the code from there and adapted it for
> our needs afair.
>

the stdlib godoc doesn't do anything with domains as best as I can tell,
which was why I pointed out the CL where it got added here.  Since we know
the root directory
<https://github.com/camlistore/camlistore/blob/master/website/camweb.go#L76>,
it should be relatively easy to strip that out and figure out the correct
package path.  Granted, that root flag got added much later, so it makes
sense why it wasn't being used.  I'll see if I can achieve everything
without needing any notion of domainName(s) in godoc.go.


>
> Does that answer your question?
>

I think so, thanks.


>
>
>
> On 5 January 2018 at 23:01, Will Norris <w...@willnorris.com> wrote:
> > Mathieu,
> >
> > Do you recall the reason for caring about the domain name appearing in
> the
> > filepath in website/godoc.org?  It looks like it was added in a96ec4e,
> but I
> > can't figure out why it's needed.  I'm working on trying to implement
> #1010,
> > and was seeing what in website/godoc.go could be simplified or cleaned
> up as
> > part of the process.
>

-- 
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.

domain name in website/godoc.org

[Will Norris]

Mathieu,

Do you recall the reason for caring about the domain name appearing in the
filepath in website/godoc.org?  It looks like it was added in a96ec4e
,
but I can't figure out why it's needed.  I'm working on trying to implement
#1010 , and was
seeing what in website/godoc.go could be simplified or cleaned up as part
of the process.

-- 
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.

Re: heads-up: are you using MySQL (or other DBMS)?

[Will Norris]

I'm using perkeep in production with MySQL, though I'm not using dbNames,
just dbname.

You mentioned migrating the index database... wouldn't it be sufficient to
simply rebuild the index and not worry about migrating?  Or are you
specifically trying to avoid users having to do that?

On Thu, Jan 4, 2018 at 8:36 AM, Mathieu Lonjaret  wrote:

> yeah, will do.
>
>
> On 4 January 2018 at 17:34, Brad Fitzpatrick  wrote:
> > We should at least fix the launcher case, which should be easy. We can
> > special-case that, detecting we're a launcher config and changing the
> > automatic config it builds at startup to use the old db names.
> >
> >
> > On Thu, Jan 4, 2018 at 7:47 AM, Mathieu Lonjaret
> >  wrote:
> >>
> >> Hi,
> >>
> >> as of rev 7eda9fd5027fda88166d6c03b6490cffbf2de5fb
> >>
> >> (https://github.com/camlistore/camlistore/commit/
> 7eda9fd5027fda88166d6c03b6490cffbf2de5fb),
> >> the default names of the various databases used by Perkeep change.
> >> That basically means:
> >>
> >> 1) if you were using dbNames (not dbname), to set your "index"
> >> database name, then it concerns you.
> >> 2) if you were using dbNames for the other "secondary" indexes and
> >> queues then your are affected, but it's maybe not as important.
> >> 3) If you are running a Camli/Perkeep instance on GCE, deployed with
> >> the launcher, you fall into case 1) (and case 2) as well).
> >>
> >> We probably need to think about a transition patch to help users
> >> migrate at least their index database, or at the very least warn them.
> >>
> >> But to figure out how much effort we have to put into this, it would
> >> help to know how many among you are affected.
> >>
> >> So, if you are either running Perkeep in production with a DBMS
> >> (MySQL, PostgreSQL, MongoDB), or running an instance from the GCE
> >> launcher, could you please let us know?
> >>
> >> Feel free to forward this to friends who are not on the mailing-list
> too.
> >>
> >> Thanks.
> >>
> >> --
> >> 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 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.

Re: website: update logo/mascot/colors

[Will Norris]

This is great :)  Is there a source file (PSD, AI, etc) that can be checked
in also?  I'm thinking about elements for a favicon, etc.  This is actually
perfect timing as I was prepping a CL to update the website to work better
on mobile, as well as cleanup some of the HTML and CSS.  I wasn't sure how
much effort to put in giving that I knew that new branding was coming
soon.  Do you have additional changes I should hold off for, or do you mind
me jumping in at this point?

On Tue, Jan 2, 2018 at 12:48 PM,  wrote:

>
>
> https://camlistore.googlesource.com/camlistore/+/
> 9427d6eef40018f465ca3309df52adb820b9c4e5
>
> commit 9427d6eef40018f465ca3309df52adb820b9c4e5
> Author: Brad Fitzpatrick 
> Date:   Tue Jan 2 12:45:55 2018 -0800
>
> website: update logo/mascot/colors
>
> This is Keepy the Perkeep Parakeet, from Ashley McNamara,
> @ashleymcnamara.
>
> The CSS & HTML changes are my fault. We can revise later.
>
> For the rename, issue #981
>
> Change-Id: Ifaf4e4d9a92b5d6d79473f0e9aec9db8f51aa7b1
>
> diff --git a/website/static/all.css b/website/static/all.css
> index eff04bc..2778b22 100644
> --- a/website/static/all.css
> +++ b/website/static/all.css
> @@ -98,7 +98,7 @@ h1.rootHeading em {
>  h2,
>  h2>a {
> color: #fff;
> -   background: url(camli-bar-background.png);
> +   background: #699023;
> padding: 4px 8px;
>  }
>  h2 {
> @@ -156,10 +156,10 @@ div#page.wide table.dir td.name {
>height: 43px;
>width: 788;
>text-align: center;
> -  background: url(camli-bar-background.png);
> +  background: #699023;
>margin-left: auto;
>margin-right: auto;
> -  margin-top: 1em;
> +  margin-top: 0em;
>margin-bottom: 1em;
>  }
>
> diff --git a/website/static/camli-header.png
> b/website/static/camli-header.png
> index edaecda..df1d507 100644
> Binary files a/website/static/camli-header.png and
> b/website/static/camli-header.png differ
> diff --git a/website/tmpl/page.html b/website/tmpl/page.html
> index 64098f2..c3c3d39 100644
> --- a/website/tmpl/page.html
> +++ b/website/tmpl/page.html
> @@ -34,7 +34,7 @@
>
>  {{define "banner"}}
>  
> - title="Perkeep" border='0' />
> + title="Perkeep" border='0' />
>  
>  {{end}}
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Camlistore Commits" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to camlistore-commits+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.