What can the pixls.us photographic community help DigiKam?

[Gilles Caulier]

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 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 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, 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
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170322/8a03a31e/attachment.html>