What can the pixls.us photographic community help DigiKam?

[Mica Semrick]

Greetings DigiKam Users,


Thank you for making such a fantastic application and congrats on the
5.5.0 release!

My name is Mica and I'm a community member over at https://pixls.us. We
promote free software for photographers.

We have a forum at https://discuss.pixls.us where we are already
providing official support for RawTherapee, G'MIC, and Rapid Photo
Downloader, but we're willing to host any discussion around FOSS
photography applications. We can setup a category for digikam as well if
you're interested, though we understand if you have your own
infrastructure.

I also read you're in need of a new website/web admin. If the project is
interested in moving away from Drupal and to a static site generator,
we'd be willing to assist in that project as well. Pat David recently
helped GIMP migrate to a new static site. Looking at the DigiKam
website, I don't see too much dynamic content.

We'd love it if you'd come and join us!

Best,
Mica

[Gilles Caulier-4]

2017-03-16 5:00 GMT+01:00 <[hidden email]>:

Greetings DigiKam Users,


Thank you for making such a fantastic application and congrats on the 5.5.0 release!

My name is Mica and I'm a community member over at https://pixls.us. We promote free software for photographers.

We have a forum at https://discuss.pixls.us where we are already providing official support for RawTherapee, G'MIC, and Rapid Photo Downloader, but we're willing to host any discussion around FOSS photography applications. We can setup a category for digikam as well if you're interested, though we understand if you have your own infrastructure.

I also read you're in need of a new website/web admin. If the project is interested in moving away from Drupal and to a static site generator, we'd be willing to assist in that project as well. Pat David recently helped GIMP migrate to a new static site. Looking at the DigiKam website, I don't see too much dynamic content.

Right for the requirement. A new web site must be planed quickly (dixit KDE team request about security issues with old Drupal 6)

You propose something about a static web site, so without a CMS. What's about the story of the site. All will be lost ?

What do you propose as technical details for this static web site ? Where it will be hosted ? Did you have any example already done ?

Best

Gilles Caulier

PS : I would like digiKam users imply a little bit with this topic as it can be managed without complexity. Web site is not like the one million of C++ code lines from digiKam...

[patdavid]

Hello all!

Just an addendum to what Mica was saying, based on this thread:

http://digikam.1695700.n4.nabble.com/digikam-org-Webmaster-wanted-td4694408.html

There might be a desire to migrate the website to something new.  One of the things that we're hoping to do (as part of paying it back to the Free Software projects that we use) is to help provide support on infrastructure of this type so that the developers and project team can focus on the things they do best (or would rather be working on).  This includes running and managing the forums over at https://discuss.pixls.us.  In case you hadn't had a chance to use a discourse forum yet, it can easily be used entirely like a mailing list if you'd prefer (but has the added benefit of a web interface as well).

We'd be happy to offload other things if needed (for example, we're hosting all of the raw samples that are used for regression testing in raw processing at https://raw.pixls.us - this is a replacement for the old rawsamples.ch site). 

We'd love to help out if we can.  It is honestly the least we can do for projects that so many of us rely on and use your work.

On Wed, Mar 15, 2017 at 11:00 PM <[hidden email]> wrote:

Greetings DigiKam Users,


Thank you for making such a fantastic application and congrats on the
5.5.0 release!

My name is Mica and I'm a community member over at https://pixls.us. We
promote free software for photographers.

We have a forum at https://discuss.pixls.us where we are already
providing official support for RawTherapee, G'MIC, and Rapid Photo
Downloader, but we're willing to host any discussion around FOSS
photography applications. We can setup a category for digikam as well if
you're interested, though we understand if you have your own
infrastructure.

I also read you're in need of a new website/web admin. If the project is
interested in moving away from Drupal and to a static site generator,
we'd be willing to assist in that project as well. Pat David recently
helped GIMP migrate to a new static site. Looking at the DigiKam
website, I don't see too much dynamic content.

We'd love it if you'd come and join us!

Best,
Mica

--

[patdavid]

On Thu, Mar 16, 2017 at 2:14 PM Gilles Caulier <[hidden email]> wrote:

 

You propose something about a static web site, so without a CMS. What's about the story of the site. All will be lost ?

What do you propose as technical details for this static web site ? Where it will be hosted ? Did you have any example already done ?

The static site is simply the full website where all of the pages are pre-compiled and generated.  In this way, the actual website content will be served as static assets from the webserver (as opposed to having content be created on the server, on the fly, by a scripting language + database - which is the way Drupal does it now).

All of the content of the current site can be migrated to a static site, so nothing would be lost (as far as I can tell from looking around the website now).

You can keep the code and content for the website in a git repository.  If you use CI service of some sort, we can likely include hooks for building and publishing the site when content is commited to certain branches.  I'm assuming you already have a host on the infrastructure your using for the current website?  If not, we can happily host for you on the same server we host https://pixls.us from.

The two biggest examples of this infrastructure in action is our main site at https://pixls.us.

The site code is hosted on github at the moment: https://github.com/pixlsus/website

Our articles and news/blog posts are simply written in Markdown and included in the appropriate folders.  We commit, have the CI server call a build script, and a few moments later we have an entire directory that is our website, ready to be rsync'd to the server.  It's all automated at the moment so a new website is built and pushed for every commit to our master branch.

Another example of this is the redesign on the GIMP website from last November (https://www.gimp.org).

The site code is hosted on our GIMP/GNOME infrastructure (provided by Red Hat): https://git.gnome.org/browse/gimp-web/

In this case, our master branch gets built every 20 minutes on the actual webserver.  Our testing branch gets built every 5 minutes (https://testing.gimp.org).

Just as before, our content is written as Markdown (but could be reStructuredText or AsciiDoc), and placed in the appropriate folders.

The system is simple, elegant, and resilient to changes.  By only serving static assets the security footprint is significantly decreased from having PHP/Ruby/MySQL/postgre etc exposed to the internet.  The server resources requirements are much, much smaller, and you can likely serve far more people simultaneously on the same infrastructure without stressing the server.

I didn't mean to barge in on Mica, and I apologize. :)  Hopefully this answers some of the questions, though!

pat

--

[Mica Semrick]

Hello,

Static sties operate very simply: there are a few templates and content pages. The content is moved through the templates based on how the templating logic is written. We would first do a little analysis to see what content you want to migrate from the current site to the new site. Then we'd identify any other necessary features. Then we'd use one of several export and convert tools to move the content into files on the file system, clean them up, then design the new site.

As for the history of the current site, we can migrate all applicable content, but if you mean database history, most converters don't exporting database history. You can always download a copy of the database in case it is needed for further use.

As far as technical details are concerned, I am familiar with the static site generators: middleman (ruby), hugo (go), and metalsmith (javascript/nodejs). As far as hosting goes, you can continue to use your current host as all a static site requires is a webserver and a way to upload the site. If you're in need of hosting, it can likely be done on the same server as the main pixls.us site. The static site is maintained in git or similar and access to add or alter posts and content is handled by a git host such as githib or gitlab. If CI is involved, then we can build the site on commits to the master branch and deploy the site via rsync or sftp if the site builds successfully. Examples of sites completed are my own site silentumbrella.com, pixls.us, and gimp.org.

Best,
Mica

On March 16, 2017 12:13:31 PM PDT, Gilles Caulier <[hidden email]> wrote:

2017-03-16 5:00 GMT+01:00 <[hidden email]>:

Greetings DigiKam Users,


Thank you for making such a fantastic application and congrats on the 5.5.0 release!

My name is Mica and I'm a community member over at https://pixls.us. We promote free software for photographers.

We have a forum at https://discuss.pixls.us where we are already providing official support for RawTherapee, G'MIC, and Rapid Photo Downloader, but we're willing to host any discussion around FOSS photography applications. We can setup a category for digikam as well if you're interested, though we understand if you have your own infrastructure.

I also read you're in need of a new website/web admin. If the project is interested in moving away from Drupal and to a static site generator, we'd be willing to assist in that project as well. Pat David recently helped GIMP migrate to a new static site. Looking at the DigiKam website, I don't see too much dynamic content.

Right for the requirement. A new web site must be planed quickly (dixit KDE team request about security issues with old Drupal 6)

You propose something about a static web site, so without a CMS. What's about the story of the site. All will be lost ?

What do you propose as technical details for this static web site ? Where it will be hosted ? Did you have any example already done ?

Best

Gilles Caulier

PS : I would like digiKam users imply a little bit with this topic as it can be managed without complexity. Web site is not like the one million of C++ code lines from digiKam...

[Dmitri Popov-2]

I would very much like to keep this discussion going forward, as
digiKam is in a dire need of a new and improved website.

Best,
Dmitri

On Fri, Mar 17, 2017 at 7:04 AM, Mica Semrick <[hidden email]> wrote:

> Hello,
>
> Static sties operate very simply: there are a few templates and content
> pages. The content is moved through the templates based on how the
> templating logic is written. We would first do a little analysis to see what
> content you want to migrate from the current site to the new site. Then we'd
> identify any other necessary features. Then we'd use one of several export
> and convert tools to move the content into files on the file system, clean
> them up, then design the new site.
>
> As for the history of the current site, we can migrate all applicable
> content, but if you mean database history, most converters don't exporting
> database history. You can always download a copy of the database in case it
> is needed for further use.
>
> As far as technical details are concerned, I am familiar with the static
> site generators: middleman (ruby), hugo (go), and metalsmith
> (javascript/nodejs). As far as hosting goes, you can continue to use your
> current host as all a static site requires is a webserver and a way to
> upload the site. If you're in need of hosting, it can likely be done on the
> same server as the main pixls.us site. The static site is maintained in git
> or similar and access to add or alter posts and content is handled by a git
> host such as githib or gitlab. If CI is involved, then we can build the site
> on commits to the master branch and deploy the site via rsync or sftp if the
> site builds successfully. Examples of sites completed are my own site
> silentumbrella.com, pixls.us, and gimp.org.
>
> Best,
> Mica
>
>
> On March 16, 2017 12:13:31 PM PDT, Gilles Caulier <[hidden email]>
> wrote:
>>
>>
>>
>> 2017-03-16 5:00 GMT+01:00 <[hidden email]>:
>>>
>>> Greetings DigiKam Users,
>>>
>>>
>>> Thank you for making such a fantastic application and congrats on the
>>> 5.5.0 release!
>>>
>>> My name is Mica and I'm a community member over at https://pixls.us. We
>>> promote free software for photographers.
>>>
>>> We have a forum at https://discuss.pixls.us where we are already
>>> providing official support for RawTherapee, G'MIC, and Rapid Photo
>>> Downloader, but we're willing to host any discussion around FOSS photography
>>> applications. We can setup a category for digikam as well if you're
>>> interested, though we understand if you have your own infrastructure.
>>>
>>> I also read you're in need of a new website/web admin. If the project is
>>> interested in moving away from Drupal and to a static site generator, we'd
>>> be willing to assist in that project as well. Pat David recently helped GIMP
>>> migrate to a new static site. Looking at the DigiKam website, I don't see
>>> too much dynamic content.
>>
>>
>> Right for the requirement. A new web site must be planed quickly (dixit
>> KDE team request about security issues with old Drupal 6)
>>
>> You propose something about a static web site, so without a CMS. What's
>> about the story of the site. All will be lost ?
>>
>> What do you propose as technical details for this static web site ? Where
>> it will be hosted ? Did you have any example already done ?
>>
>> Best
>>
>> Gilles Caulier
>>
>> PS : I would like digiKam users imply a little bit with this topic as it
>> can be managed without complexity. Web site is not like the one million of
>> C++ code lines from digiKam...
>>
>>
>

[Richard Mortimer-2]

On 20/03/2017 09:53, Dmitri Popov wrote:
> I would very much like to keep this discussion going forward, as
> digiKam is in a dire need of a new and improved website.
>
I agree with Dmitri. This is a good opportunity to utilise the skills of
a group who have a proven track record delivering top notch sites.

On a technical level I like the idea of static site generation. The live
site would have fewer dependencies and hence there is much less to go
wrong and/or exploit.

My only concern is whether the static site content management can be
made sufficiently straightfoward for non-technical digikam users to
contribute content to the website.

Mica/Pat can hopefully share their experiences here and guide towards a
workflow that would work for these users. I know that git is much more
user friendly these days with many graphical packages available. A
simple text editor can edit the markdown and a continuous integration
system can do all the magic to make the finished site appear in situ.
I'm not really one to judge what is simple given that I use git daily in
my non-digikam life.

Regards

Richard

> Best,
> Dmitri
>
> On Fri, Mar 17, 2017 at 7:04 AM, Mica Semrick <[hidden email]> wrote:
>> Hello,
>>
>> Static sties operate very simply: there are a few templates and content
>> pages. The content is moved through the templates based on how the
>> templating logic is written. We would first do a little analysis to see what
>> content you want to migrate from the current site to the new site. Then we'd
>> identify any other necessary features. Then we'd use one of several export
>> and convert tools to move the content into files on the file system, clean
>> them up, then design the new site.
>>
>> As for the history of the current site, we can migrate all applicable
>> content, but if you mean database history, most converters don't exporting
>> database history. You can always download a copy of the database in case it
>> is needed for further use.
>>
>> As far as technical details are concerned, I am familiar with the static
>> site generators: middleman (ruby), hugo (go), and metalsmith
>> (javascript/nodejs). As far as hosting goes, you can continue to use your
>> current host as all a static site requires is a webserver and a way to
>> upload the site. If you're in need of hosting, it can likely be done on the
>> same server as the main pixls.us site. The static site is maintained in git
>> or similar and access to add or alter posts and content is handled by a git
>> host such as githib or gitlab. If CI is involved, then we can build the site
>> on commits to the master branch and deploy the site via rsync or sftp if the
>> site builds successfully. Examples of sites completed are my own site
>> silentumbrella.com, pixls.us, and gimp.org.
>>
>> Best,
>> Mica
>>
>>
>> On March 16, 2017 12:13:31 PM PDT, Gilles Caulier <[hidden email]>
>> wrote:
>>>
>>>
>>>
>>> 2017-03-16 5:00 GMT+01:00 <[hidden email]>:
>>>>
>>>> Greetings DigiKam Users,
>>>>
>>>>
>>>> Thank you for making such a fantastic application and congrats on the
>>>> 5.5.0 release!
>>>>
>>>> My name is Mica and I'm a community member over at https://pixls.us. We
>>>> promote free software for photographers.
>>>>
>>>> We have a forum at https://discuss.pixls.us where we are already
>>>> providing official support for RawTherapee, G'MIC, and Rapid Photo
>>>> Downloader, but we're willing to host any discussion around FOSS photography
>>>> applications. We can setup a category for digikam as well if you're
>>>> interested, though we understand if you have your own infrastructure.
>>>>
>>>> I also read you're in need of a new website/web admin. If the project is
>>>> interested in moving away from Drupal and to a static site generator, we'd
>>>> be willing to assist in that project as well. Pat David recently helped GIMP
>>>> migrate to a new static site. Looking at the DigiKam website, I don't see
>>>> too much dynamic content.
>>>
>>>
>>> Right for the requirement. A new web site must be planed quickly (dixit
>>> KDE team request about security issues with old Drupal 6)
>>>
>>> You propose something about a static web site, so without a CMS. What's
>>> about the story of the site. All will be lost ?
>>>
>>> What do you propose as technical details for this static web site ? Where
>>> it will be hosted ? Did you have any example already done ?
>>>
>>> Best
>>>
>>> Gilles Caulier
>>>
>>> PS : I would like digiKam users imply a little bit with this topic as it
>>> can be managed without complexity. Web site is not like the one million of
>>> C++ code lines from digiKam...
>>>
>>>
>>

[Jürgen Blumenschein]

Hallo,

I thought about how I can give back a little of my resources for using
DK a long time. I have some experiences with Typo3 but none with Drupal.

So I'll at this moment only my support in translating if you are going
to build a multilanguage Website. As I see there are at least some german,
french and spanish speaking people on the list. The acceptance of DK could
improve if there are more languages supported.
My help in administrating digikam.org could be a second step, but not for now.

Btw. Could a static site offer multilanguage support?

Jürgen

Zitat von Dmitri Popov <[hidden email]>:

> I would very much like to keep this discussion going forward, as
> digiKam is in a dire need of a new and improved website.
>
> Best,
> Dmitri
>
> On Fri, Mar 17, 2017 at 7:04 AM, Mica Semrick  
> <[hidden email]> wrote:
>> Hello,
>>
>> Static sties operate very simply: there are a few templates and content
>> pages. The content is moved through the templates based on how the
>> templating logic is written. We would first do a little analysis to see what
>> content you want to migrate from the current site to the new site. Then we'd
>> identify any other necessary features. Then we'd use one of several export
>> and convert tools to move the content into files on the file system, clean
>> them up, then design the new site.
>>
>> As for the history of the current site, we can migrate all applicable
>> content, but if you mean database history, most converters don't exporting
>> database history. You can always download a copy of the database in case it
>> is needed for further use.
>>
>> As far as technical details are concerned, I am familiar with the static
>> site generators: middleman (ruby), hugo (go), and metalsmith
>> (javascript/nodejs). As far as hosting goes, you can continue to use your
>> current host as all a static site requires is a webserver and a way to
>> upload the site. If you're in need of hosting, it can likely be done on the
>> same server as the main pixls.us site. The static site is maintained in git
>> or similar and access to add or alter posts and content is handled by a git
>> host such as githib or gitlab. If CI is involved, then we can build the site
>> on commits to the master branch and deploy the site via rsync or sftp if the
>> site builds successfully. Examples of sites completed are my own site
>> silentumbrella.com, pixls.us, and gimp.org.
>>
>> Best,
>> Mica
>>
>>
>> On March 16, 2017 12:13:31 PM PDT, Gilles Caulier <[hidden email]>
>> wrote:
>>>
>>>
>>>
>>> 2017-03-16 5:00 GMT+01:00 <[hidden email]>:
>>>>
>>>> Greetings DigiKam Users,
>>>>
>>>>
>>>> Thank you for making such a fantastic application and congrats on the
>>>> 5.5.0 release!
>>>>
>>>> My name is Mica and I'm a community member over at https://pixls.us. We
>>>> promote free software for photographers.
>>>>
>>>> We have a forum at https://discuss.pixls.us where we are already
>>>> providing official support for RawTherapee, G'MIC, and Rapid Photo
>>>> Downloader, but we're willing to host any discussion around FOSS  
>>>> photography
>>>> applications. We can setup a category for digikam as well if you're
>>>> interested, though we understand if you have your own infrastructure.
>>>>
>>>> I also read you're in need of a new website/web admin. If the project is
>>>> interested in moving away from Drupal and to a static site generator, we'd
>>>> be willing to assist in that project as well. Pat David recently  
>>>> helped GIMP
>>>> migrate to a new static site. Looking at the DigiKam website, I don't see
>>>> too much dynamic content.
>>>
>>>
>>> Right for the requirement. A new web site must be planed quickly (dixit
>>> KDE team request about security issues with old Drupal 6)
>>>
>>> You propose something about a static web site, so without a CMS. What's
>>> about the story of the site. All will be lost ?
>>>
>>> What do you propose as technical details for this static web site ? Where
>>> it will be hosted ? Did you have any example already done ?
>>>
>>> Best
>>>
>>> Gilles Caulier
>>>
>>> PS : I would like digiKam users imply a little bit with this topic as it
>>> can be managed without complexity. Web site is not like the one million of
>>> C++ code lines from digiKam...
>>>
>>>
>>

--
Jürgen Blumenschein, eMail: [hidden email]
Homepage: http://members.dokom.net/blumenschein
Am Quartus 17
D-44149 Dortmund
Tel.: [phone], Handy: [phone]
public key:  
http://members.dokom.net/blumenscheinJuergen_Blumenschein_(0xC9358EBB)_public_key.asc

[tosca]

Hi to everybody,

I must admit I'm a bit surprised by the direction this discussion seems to be going: are static sites the new trend of the day?

I didn't answer to previous Gilles's request about upgrading Digikam website, as I thought Drupal was a requirement. As it is, after having studied it for some time, I gave up trying to use Drupal a couple of years ago: it is a very particular CMS, requires some serious apprenticeship (for web creators at least) and is notoriously backward not compatible.

But I've been using other CMS for years, developed websites for both (non techy) customers and myself. Several years ago, I switched entirely to WordPress and have been very happy with it ever since. I know enough of WP itself, PHP, jQuery and such to have developed all my sites themes, and use ready-made plugins only sparingly, From my point of view, WP brings versatility and flexibility I'm not sure a static site can provide. It is also very user-friendly and its community size speaks wonders.

I might be mistaken, but I don't understand how a static site could be so easy to maintain, when you'll probably have quite a number of editors that need to publish different kind of information quite frequently.

My own two cents,
Marie-Noëlle

--

Le 20/03/2017 à 13:28, Marie-Noëlle Augendre a écrit :

> I might be mistaken, but I don't understand how a static site could be
> so easy to maintain, when you'll probably have quite a number of editors
> that need to publish different kind of information quite frequently.
>

and if you want to avoid the fuss of managing wordpress (anti-spam, for
example), PmWiki is a very simple and secure system

http://dodin.info/wiki/pmwiki.php

as are many others...

I don't think github to be friendly, except for developpers

jdd

[tosca]

2017-03-20 13:58 GMT+01:00 jdd <[hidden email]>:

and if you want to avoid the fuss of managing wordpress (anti-spam, for example), PmWiki is a very simple and secure system

http://dodin.info/wiki/pmwiki.php

as are many others...

I've used dokuwiki in several occasions. It's a good software too, especially for shared documentation; but I wouldn't say it's so versatile as WordPress

 

I don't think github to be friendly, except for developpers

I fully agree!

Marie-Noëlle

 

jdd

--

[Simon Frei]

Honestly, this is less about which technology is better than the other, than about a group of people (pixls.us team) stepping up to manage the digikam website. Their tool of choice is a static website generated from some kind of markup language. What matters is that they are willing to invest this work and they definitely proved that the results are (more than) good.

The only content that changes (more like appears) are new releases and some blog entries from Dmitri. These can easily be done via a static site. For user contribution it will be as easy as editing a text file and submitting it per mail or git.

On 20/03/17 14:03, Marie-Noëlle Augendre wrote:

2017-03-20 13:58 GMT+01:00 jdd <[hidden email]>:

and if you want to avoid the fuss of managing wordpress (anti-spam, for example), PmWiki is a very simple and secure system

http://dodin.info/wiki/pmwiki.php

as are many others...

I've used dokuwiki in several occasions. It's a good software too, especially for shared documentation; but I wouldn't say it's so versatile as WordPress

 

I don't think github to be friendly, except for developpers

I fully agree!

Marie-Noëlle

 

jdd

--

Le 20/03/2017 à 14:06, Simon Frei a écrit :

> The only content that changes (more like appears) are new releases and
> some blog entries from Dmitri. These can easily be done via a static
> site. For user contribution it will be as easy as editing a text file
> and submitting it per mail or git.

it's entirely the matter: will the site be user (writing) friendly or
only managed by the developers.

it can even be both, with forum/wiki/etc. and static content

jdd

[Gilles Caulier-4]

2017-03-20 14:09 GMT+01:00 jdd <[hidden email]>:

Le 20/03/2017 à 14:06, Simon Frei a écrit :

The only content that changes (more like appears) are new releases and
some blog entries from Dmitri. These can easily be done via a static
site. For user contribution it will be as easy as editing a text file
and submitting it per mail or git.

it's entirely the matter: will the site be user (writing) friendly or only managed by the developers.

Typically, it's only managed by developers, excepted Dmitry posts.

The users interractions are the comments at release announcements This is very important.

But this can be moved in a dedicated forum, as i understand pixls.us comments from this thread.

If it's the case, i have no direct objection... The subject still open and clarification given to be sure.

Gilles

[patdavid]

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, that is - an embed at the bottom of a post will display a threaded conversation about that topic hosted on https://discuss.pixls.us.

---

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 

--

[Dmitri Popov-2]

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 <[hidden email]> 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, that is - an embed at the bottom of a post will display a threaded
> conversation about that topic hosted on https://discuss.pixls.us.
>
> ---
>
> 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
>
>
>
>
> --
> https://patdavid.net
> GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC

[Gilles Caulier-4]

The contact to KDE team about current www.digikam.org is Ben Cooksley <[hidden email]>

I CC him to contribute to this thread...

Gilles Caulier

2017-03-21 10:42 GMT+01:00 Dmitri Popov <[hidden email]>:

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 <[hidden email]> 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, that is - an embed at the bottom of a post will display a threaded
> conversation about that topic hosted on https://discuss.pixls.us.
>
> ---
>
> 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
>
>
>
>
> --
> https://patdavid.net
> GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC

[Gilles Caulier-4]

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 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 <[hidden email]>:

The contact to KDE team about current www.digikam.org is Ben Cooksley <[hidden email]>

I CC him to contribute to this thread...

Gilles Caulier

2017-03-21 10:42 GMT+01:00 Dmitri Popov <[hidden email]>:

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 <[hidden email]> 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, that is - an embed at the bottom of a post will display a threaded
> conversation about that topic hosted on https://discuss.pixls.us.
>
> ---
>
> 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
>
>
>
>
> --
> https://patdavid.net
> GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC

[Gilles Caulier-4]

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 <[hidden email]>:

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 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 <[hidden email]>:

The contact to KDE team about current www.digikam.org is Ben Cooksley <[hidden email]>

I CC him to contribute to this thread...

Gilles Caulier

2017-03-21 10:42 GMT+01:00 Dmitri Popov <[hidden email]>:

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 <[hidden email]> 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, that is - an embed at the bottom of a post will display a threaded
> conversation about that topic hosted on https://discuss.pixls.us.
>
> ---
>
> 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
>
>
>
>
> --
> https://patdavid.net
> GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC

[Mica Semrick]

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 <[hidden email]>:
>
>> 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
>> <[hidden email]>:
>>
>> The contact to KDE team about current www.digikam.org [2] is Ben
>> Cooksley <[hidden email]>
>>
>> I CC him to contribute to this thread...
>>
>> Gilles Caulier
>>
>> 2017-03-21 10:42 GMT+01:00 Dmitri Popov <[hidden email]>:
>> 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 <[hidden email]>
>> 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