What can the pixls.us photographic community help DigiKam?

Wed Mar 22 07:35:03 GMT 2017

Hello all,

I can get in touch with Ben if someone would like to send me his contact 
information.

A quick recap, so we're all on the same page:
- drupal site being shut down on March 31
- migration to static site using Hugo (http://gohugo.io) and a redesign 
proposed
-- template based on Zurb Foundation 6
-- current URLs taken into account & can generate redirects
- requires webhosting, which pixls.us can provide, but pixls.us members 
would like to use KDE/digikam's current hosting if possible
-- static site requires only a webserver such as apache and rsync over 
SSH access to the webroot for digikam.org
- site maintained in git; authorization determined by hosting platform, 
e.g. github, gitlab,
- continuous integration like TraviCI, can be used to build and deploy 
the site when a commit is pushed to master
- current admin should back up the drupal database for posterity
- current pages (but not page history) can be migrated

Pat was kind enough to write a script to scrape all the news articles 
from digikam.org, which composed the bulk of content to be migrated, and 
format the results with the proper metadata for hugo. I set up the 
project scaffolding and migrated some of the non-news pages (there are 
pages that still need to be migrated).

You can see the content we've migrated so far here: 
https://github.com/pixlsus/digikam_website

There probably isn't much more content to migrate. I'll follow up with 
some questions about the content and migrate the remaining necessary 
pages.

You can run hugo locally to see the progress:
$ wget 
https://github.com/spf13/hugo/releases/download/v0.19/hugo_0.19_Linux-64bit.tar.gz
$ tar -zxvf hugo_0.19_Linux-64bit.tar.gz
$ git clone https://github.com/pixlsus/digikam_website
$ cd digikam_website/themes
$ git clone https://github.com/tummychow/lanyon-hugo
$ cd ..
$ ./path/to/hugo serve --theme=lanyon-hugo

I can't say we'll have a 100% finished & beautiful website by March 31, 
but I believe we can be pretty close to finished & very functional by 
that date.

Best,
Mica

On 2017-03-21 23:37, Gilles Caulier wrote:
> Note : when Ben said " I think it's best if they contact us with the
> details they require. I'd rather
> not read a long mailing list thread." : the "they" want mean Pixls.us
> team of course....
> 
> Gilles Caulier
> 
> 2017-03-22 7:36 GMT+01:00 Gilles Caulier <caulier.gilles at gmail.com>:
> 
>> Hi all,
>> 
>> This is the response from Ben by private mail :
>> 
>> // ---------------------------------------------------
>> 
>> Hi Gilles,
>> 
>> Given the amount of work which we've put in thus far and the time
>> constraints Sysadmin is under in getting other things done, I think
>> it's best if they contact us with the details they require. I'd
>> rather
>> not read a long mailing list thread.
>> 
>> At this stage, i'll be shutting down the Drupal 6 instance on March
>> 31
>> as we need to protect the security of KDE Infrastructure as a first
>> priority. This migration has effectively been ready to go (theme
>> aside) since early February, with the only reason for the delay
>> being
>> your requirement a theme be customised for Digikam and nobody being
>> able to do it.
>> 
>> Regards,
>> Ben
>> 
>> //
>> -------------------------------------------------------------------
>> 
>> So it become urgent to switch to a new web site. "Static" proposal
>> from pixls.us [1] sound like the best solution.
>> 
>> Comments are welcome. Please be constructive.
>> 
>> Thanks in advance
>> 
>> Gilles Caulier
>> 
>> 2017-03-21 10:49 GMT+01:00 Gilles Caulier
>> <caulier.gilles at gmail.com>:
>> 
>> The contact to KDE team about current www.digikam.org [2] is Ben
>> Cooksley <bcooksley at kde.org>
>> 
>> I CC him to contribute to this thread...
>> 
>> Gilles Caulier
>> 
>> 2017-03-21 10:42 GMT+01:00 Dmitri Popov <lazylegs at gmail.com>:
>> Pat,
>> 
>> Thank you for the detailed outline. If there is anything I can help
>> you with, please do let me know.
>> 
>> Best,
>> Dmitri
>> 
>> On Mon, Mar 20, 2017 at 10:13 PM, Pat David <patdavid at gmail.com>
>> wrote:
>>> The intention here is to provide a new, modern website that is
>> secure and
>>> maintainable.
>>> 
>>> Let me address a couple of possible questions up front:
>>> 
>>> 1. The existing site content can be ported over to a new site.
>> This
>>> includes previous posts in news/blogs and all of the more static
>> pages as
>>> they exist right now.
>>> 
>>> The only thing we may have a problem with would be the comment
>> system used
>>> by Drupal. In this case, old comments are likely not going to get
>> brought
>>> over as actual _comments_. We can probably bring them over as
>> plain content
>>> that gets appended to existing news/blog items.
>>> 
>>> 2. I analyzed the existing site quickly, and noticed that as far
>> as content
>>> pages go, we were looking (roughly) at:
>>> 
>>> About
>>> Overview
>>> Features
>>> Awards & Reviews
>>> Related Projects & links
>>> Screenshots
>>> Testimonials
>>> News *
>>> Release Plan
>>> Changelog
>>> Events
>>> Developers Blogs *
>>> Download
>>> digiKam Recipes Book
>>> Documentation
>>> Wiki
>>> FAQ
>>> Support
>>> Donation & Sponsor
>>> Splash-screens
>>> Contribute
>>> Contact
>>> 
>>> Items marked with (*) are the most likely candidates for more
>> frequently
>>> published content. The rest of the pages are probably fairly
>> consistent and
>>> don't change all that often (every release maybe?).
>>> 
>>> 3. Contributing to the site is easy, just write your content in a
>> plain-text
>>> markdown file.
>>> 
>>> I assume that you don't want to let everyone publish material to
>> your
>>> website? No matter what the system (CMS/Static/Whatever), you
>> likely want a
>>> check step in the publishing process. In the case of a static
>> site, it's
>>> handled by commit access to the repo. If someone w/o access wants
>> to
>>> publish something, send the plain-text file to someone with commit
>> access.
>>> 
>>> At GIMP, we can accept patches, or someone can just email the
>> plain-text
>>> files (+ assets) and one of us with commit access manages the
>> rest.
>>> 
>>> 4. Comments can be handled the same way we are currently doing it
>> on
>>> pixls.us [1], that is - an embed at the bottom of a post will
>> display a threaded
>>> conversation about that topic hosted on https://discuss.pixls.us
>> [3].
>>> 
>>> ---
>>> 
>>> At the end of the day we want to help, and we know that the dev
>> team likely
>>> would rather be hacking on Digikam. As such, we're ready and
>> willing to get
>>> a new site up and running, and to help manage things.
>>> 
>>> Just let us know if we _shouldn't_ continue working on the site.
>> :)
>>> 
>>> Also, is there a contact person for the infrastructure your
>> running the site
>>> on now? I'm assuming a server that the kde folks have somewhere?
>>> 
>>> pat
>>> 
>>> PS (interesting sidenote):
>>> I scraped the existing site quickly to get this, and it appears to
>> me that
>>> over the past 5 years the _majority_ of the posts are from two
>> submitters
>>> (digikam + Dmitri).
>>> A table of posts per person by year, since 2006:
>>> https://paste.gnome.org/pwbvlr6ha [4]
>>> 
>>> 
>>> 
>>> 
>>> --
>>> https://patdavid.net [5]
>>> GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC
> 
> 
> 
> Links:
> ------
> [1] http://pixls.us
> [2] http://www.digikam.org
> [3] https://discuss.pixls.us
> [4] https://paste.gnome.org/pwbvlr6ha
> [5] https://patdavid.net