<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Contribute on Ansel</title><link>https://ansel.photos/uk/contribute/</link><description>Recent content in Contribute on Ansel</description><generator>Hugo -- gohugo.io</generator><language>uk</language><copyright>© Copyright 2022-2025 – Aurélien Pierre</copyright><lastBuildDate>Sun, 14 Jul 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://ansel.photos/uk/contribute/index.xml" rel="self" type="application/rss+xml"/><item><title>Introduction</title><link>https://ansel.photos/uk/contribute/introduction/</link><pubDate>Sun, 14 Jul 2024 00:00:00 +0000</pubDate><updated>Sun, 14 Jul 2024 00:00:00 +0000</updated><guid>8c7b8bc7e28ece07542e5bc773f8395702d009f39503264f9e5dfd2f3b69058b</guid><description>&lt;/section>
&lt;section id="context">
&lt;h2 class="text-left heading">
Context
&lt;span class="header-filet">&lt;/span>
&lt;/h2>
&lt;p>Digital photography has widely spread in the 2000&amp;rsquo;s as it allowed faster workflows and made possible to get immediate results, compared to the traditional film &amp;amp; darkroom workflow. But this introduced many new problems.&lt;/p>
&lt;p>Firstly, analogue photographers were not necessarily accomplished lab and printing technicians, but could rely on local photo labs to get their developments and prints done. Digital photography added the burden of processing the &amp;ldquo;digital negatives&amp;rdquo; (raw files) on the shoulders of the photographers, by means of software. But those photographers didn&amp;rsquo;t usually got the appropriate training, both in digital color management and in general computer use. That pushed many of them in the hands of over-simplified software, verging on the toy side, which defined the mainstream expectation of what a digital photo editing software should be. Video editing software took another approach, being used by heavily-trained professionals in a billion-dollars industry.&lt;/p></description></item><item><title>Ansel target audience</title><link>https://ansel.photos/uk/contribute/audience/</link><pubDate>Sun, 14 Jul 2024 00:00:00 +0000</pubDate><updated>Sun, 14 Jul 2024 00:00:00 +0000</updated><guid>815f510f779e3512e2466c07f3a6919178fa31689b28db4b5a9ace3aa2eff784</guid><description>&lt;p>As knowing the audience is the first step of design, it is useful to define it.&lt;/p>
&lt;p>&lt;a href="https://eng.aurelienpierre.com/2023/01/who-are-the-darktable-users/" title="External link" target="_blank" rel="noopener noreferrer nofollow" >The Darktable survey&amp;thinsp;&lt;sup class="icon">&lt;i class="fa fa-external-link-alt">&lt;/i>&lt;/sup>&lt;/a> of 2020 showed an abnormal bias among users, favouring highly-educated men coming from technical and scientific background, and with higher programming skills than the average population. This is problematic because it does not overlap with the sociology of photographers at large (regarding computer skills as well as men/women ratio), but is a filtered subset of that social group.&lt;/p></description></item><item><title>Designing Ansel</title><link>https://ansel.photos/uk/contribute/design/</link><pubDate>Sun, 14 Jul 2024 00:00:00 +0000</pubDate><updated>Sun, 14 Jul 2024 00:00:00 +0000</updated><guid>6c4e009d8241515f65929a1fa44bedc808d5233fd2eccb7bdcac5104d3e04e88</guid><description>&lt;p>Ansel is &lt;strong>designed&lt;/strong>, not hacked. Hackers may enjoy &amp;ldquo;working&amp;rdquo; on accelerating the demise of Darktable by increasing its &lt;a href="https://en.wikipedia.org/wiki/Technical_debt" title="Wikipedia link" target="_blank" rel="noopener noreferrer nofollow" >technical debt&amp;thinsp;&lt;sup class="icon">&lt;i class="fab fa-wikipedia-w">&lt;/i>&lt;/sup>&lt;/a>.&lt;/p>
&lt;/section>
&lt;section id="what-is-design">
&lt;h2 class="text-left heading">
What is design ?
&lt;span class="header-filet">&lt;/span>
&lt;/h2>
&lt;p>Design is a process by which you unroll a methodology to bring a technical solution to an human&amp;rsquo;s problem. The design process is meant to converge to the most suitable solution, while fighting the natural urge to rush into the first or the most comfortable idea.&lt;/p></description></item><item><title>Project organization</title><link>https://ansel.photos/uk/contribute/organization/</link><pubDate>Sun, 14 Jul 2024 00:00:00 +0000</pubDate><updated>Sun, 14 Jul 2024 00:00:00 +0000</updated><guid>ffd741fc09418435793ad96cf39d0fb5b8f4a4caf6bd3997bffa5a37f0f1e89a</guid><description>&lt;p>The project is run by Aurélien Pierre, who tries to balance his photography work (mostly unexistent since 2019), developing &amp;amp; maintaining the software, and handling user education in individual training sessions. This calls for low-overhead project management strategies, relying on cloud-based collaborative tools.&lt;/p>
&lt;/section>
&lt;section id="departments">
&lt;h2 class="text-left heading">
Departments
&lt;span class="header-filet">&lt;/span>
&lt;/h2>
&lt;/section>
&lt;section id="software-development">
&lt;h3 class="text-left heading">
Software development
&lt;/h3>
&lt;p>Development is done on &lt;a href="https://github.com/aurelienpierreeng/ansel" title="External link" target="_blank" rel="noopener noreferrer nofollow" >Github&amp;thinsp;&lt;sup class="icon">&lt;i class="fa fa-external-link-alt">&lt;/i>&lt;/sup>&lt;/a>,&lt;/p>
&lt;p>Feature requests are not taken from users at this point. Users are consulted by the developer regarding their needs when a (re)design project is started. This is to prevent disruptive inputs at random times that would only slow-down the opened projects.&lt;/p></description></item><item><title>Coding style</title><link>https://ansel.photos/uk/contribute/coding-style/</link><pubDate>Sun, 14 Jul 2024 00:00:00 +0000</pubDate><updated>Sun, 14 Jul 2024 00:00:00 +0000</updated><guid>18ca6cf106b1e390635154f928a4371f6bdce3fde68f074c8e2a56746a45f7e5</guid><description>&lt;/section>
&lt;section id="values">
&lt;h2 class="text-left heading">
Values
&lt;span class="header-filet">&lt;/span>
&lt;/h2>
&lt;/section>
&lt;section id="if-it-aint-broken-dont-fix-it">
&lt;h3 class="text-left heading">
If it ain&amp;rsquo;t broken, don&amp;rsquo;t fix it
&lt;/h3>
&lt;p>Too much of Darktable &amp;ldquo;design&amp;rdquo; has started with &amp;ldquo;it would be cool if we could &amp;hellip;&amp;rdquo;. I&amp;rsquo;ll tell you what&amp;rsquo;s cool : hanging good pictures of yours on your walls ASAP. Visual arts are not performing art (like music or theater), so only the result matters. Everything that comes before is overhead, and you typically want to keep it minimal. That&amp;rsquo;s not to say that the process can&amp;rsquo;t be enjoyed in itself. However, to enjoy the process, you need to master your tools and to bend them to &lt;strong>your&lt;/strong> will, otherwise you only fight them and the whole process amounts to frustration. Problem is, Darktable &amp;ldquo;design&amp;rdquo; puts too much effort into being different for the sake of it.&lt;/p></description></item><item><title>Translating</title><link>https://ansel.photos/uk/contribute/translating/</link><pubDate>Mon, 15 Jul 2024 00:00:00 +0000</pubDate><updated>Mon, 15 Jul 2024 00:00:00 +0000</updated><guid>74c4feb664941b8f5638015a7f51da873b6b4ab0311e5c293beb254432b8cd7e</guid><description>&lt;p>Ansel uses &lt;a href="https://www.gnu.org/software/gettext/" title="External link" target="_blank" rel="noopener noreferrer nofollow" >Gettext&amp;thinsp;&lt;sup class="icon">&lt;i class="fa fa-external-link-alt">&lt;/i>&lt;/sup>&lt;/a> to translate all parts of the project:&lt;/p>
&lt;ul>
&lt;li>The software application (written in C),&lt;/li>
&lt;li>The website (Hugo templates and Markdown content),&lt;/li>
&lt;li>The documentation/user manual, inserted into the website as a module (Hugo templates and Markdown content too).&lt;/li>
&lt;/ul>
&lt;p>This ensures the same workflow can be used to translate all files, but also that some translated strings can be shared (for example, the translated GUI controls from the applications can be inserted directly into the documentation).&lt;/p></description></item><item><title>Triaging issues</title><link>https://ansel.photos/uk/contribute/triaging/</link><pubDate>Mon, 15 Jul 2024 00:00:00 +0000</pubDate><updated>Mon, 15 Jul 2024 00:00:00 +0000</updated><guid>9b993fd6d1483beb6c1af9b7b19af694bd8b04e08279bb816bf90a15ca7cda97</guid><description>&lt;p>This page is written for people helping triaging issues on the issue Github tracker.&lt;/p>
&lt;/section>
&lt;section id="preamble">
&lt;h2 class="text-left heading">
Preamble
&lt;span class="header-filet">&lt;/span>
&lt;/h2>
&lt;ul>
&lt;li>Any project has limited resources, the difference between projects will be the threshold.&lt;/li>
&lt;li>Any project should have clear goals. For Ansel, it is to manage, edit and export collections of RAW images on a desktop computer by an end-user who is not a CLI user but puts visual image quality above all else.&lt;/li>
&lt;li>Any project has overhead, that is actions requested to meet the goals, although they are not directly the goal and therefore should stay minimal. For Ansel, it is the maintenance of the website, documentation, servers, nightly-built packages, code cleanups, debugging, regression tests, cross-OS support, issues triaging, etc.&lt;/li>
&lt;li>Goals and overhead should be expressed in terms of &lt;strong>tasks&lt;/strong> to perform in order to &lt;strong>solve problems&lt;/strong> (issues). If no problem to solve, then no work to do: status quo is great too, don&amp;rsquo;t create work for the sake of it.&lt;/li>
&lt;li>because of resource limitation, tasks have to be ordered depending on their priority.&lt;/li>
&lt;/ul>
&lt;p>The following document aims at defining this priority.&lt;/p></description></item><item><title>Documenting Ansel</title><link>https://ansel.photos/uk/contribute/documenting/</link><pubDate>Mon, 13 Oct 2025 00:00:00 +0000</pubDate><updated>Mon, 13 Oct 2025 00:00:00 +0000</updated><guid>c53348fae0f6d7e46235b1087a4644244f8f534317b2a7aabe7a7e2204369653</guid><description>&lt;/section>
&lt;section id="introduction">
&lt;h2 class="text-left heading">
Introduction
&lt;span class="header-filet">&lt;/span>
&lt;/h2>
&lt;p>There are different ways to access information :&lt;/p>
&lt;ol>
&lt;li>&lt;strong>(chrono)logical&lt;/strong>, like reading page by page, line by line, until you reach the end of the publication,&lt;/li>
&lt;li>&lt;strong>thematic&lt;/strong>, like getting to the table of contents and jumping straight to the part you are interested at, &lt;strong>provided the content is divided into meaningful units of content&lt;/strong>,&lt;/li>
&lt;li>&lt;strong>transversal&lt;/strong>, like following a &amp;ldquo;related posts&amp;rdquo; section based on content similarity (defined manually, with tags &amp;amp; keywords, or learned by AI topic analysis), or explicit cross-references. For example, most websites have archives listing all pages that have a certain tag/keyword, books have glossaries.&lt;/li>
&lt;li>&lt;strong>hint-based&lt;/strong>, like presenting a bibliography of more in-depth publications or a &amp;ldquo;more info&amp;rdquo; section at the end of the content, or anticipating on later content,&lt;/li>
&lt;li>&lt;strong>source-based&lt;/strong>, following references (typically footnotes or marginnotes) to publications from where the info is extracted, mostly for verification purposes,&lt;/li>
&lt;li>&lt;strong>information retrieval&lt;/strong>, aka search engine.&lt;/li>
&lt;/ol>
&lt;p>You have to support all of them at once because they are complimentary and the best in context depends on the initial knowledge and needs of the reader. Not one of those ways is superior to the others. This means there is a fair deal of &amp;ldquo;keywords stuffing&amp;rdquo; to do into your writing, as to ensure that keyword-based content analysis and information retrieval by keywords will work as expected.&lt;/p></description></item><item><title>Democracy</title><link>https://ansel.photos/uk/contribute/democracy/</link><pubDate>Mon, 13 Oct 2025 00:00:00 +0000</pubDate><updated>Mon, 13 Oct 2025 00:00:00 +0000</updated><guid>82a70a9b451c667646598e63ede1f59d9f7fcf56f793206ab4a78cb57e701c10</guid><description>&lt;p>Ansel should be run democratically and fairly to everyone involved.&lt;/p>
&lt;/section>
&lt;section id="defining-a-cooperative-organization-beyond-open-source-code">
&lt;h2 class="text-left heading">
Defining a cooperative organization beyond open-source code
&lt;span class="header-filet">&lt;/span>
&lt;/h2>
&lt;p>Developers and users landing here are assumed to share a common interest : they want freedom in how they edit their pictures, now and in the future. Meaning :&lt;/p>
&lt;ul>
&lt;li>having a sufficient technical control over their image content and properties,&lt;/li>
&lt;li>being free from capitalists who may :
&lt;ul>
&lt;li>increase their application price at the sole benefit of shareholders,&lt;/li>
&lt;li>mine customer&amp;rsquo;s photos to train AI models without consent,&lt;/li>
&lt;li>extinguish applications without releasing the source code,&lt;/li>
&lt;/ul>
&lt;/li>
&lt;li>having a right to decide on the contours and implementation of said freedom.&lt;/li>
&lt;/ul>
&lt;p>Ansel DNA is more technically-minded and fined-grained than most RAW photo editors, while still emphasizing user-friendliness where it&amp;rsquo;s possible, mostly on typical desktop-centric tasks (interactions with input devices and files, GUI paradigms, etc.). Ansel is not &lt;a href="https://darktable.org" title="External link" target="_blank" rel="noopener noreferrer nofollow" >Darktable&amp;thinsp;&lt;sup class="icon">&lt;i class="fa fa-external-link-alt">&lt;/i>&lt;/sup>&lt;/a> or &lt;a href="https://art.pixls.us/" title="External link" target="_blank" rel="noopener noreferrer nofollow" >ART&amp;thinsp;&lt;sup class="icon">&lt;i class="fa fa-external-link-alt">&lt;/i>&lt;/sup>&lt;/a> because its vision of what a good image retouching software should be is quite different.&lt;/p></description></item><item><title>Automated workflows</title><link>https://ansel.photos/uk/contribute/workflows/</link><pubDate>Thu, 01 May 2025 00:00:00 +0000</pubDate><updated>Thu, 01 May 2025 00:00:00 +0000</updated><guid>61d0f0b8c768ea30b4a84d631015cf54fe4f5677c7751438b968eebdf75a0596</guid><description>&lt;p>Because Ansel is mostly a one-person operation, everything that could be automated was automated. This page keeps track of everything that should be maintained in the future, and where.&lt;/p>
&lt;/section>
&lt;section id="software">
&lt;h2 class="text-left heading">
Software
&lt;span class="header-filet">&lt;/span>
&lt;/h2>
&lt;/section>
&lt;section id="nightly-builds">
&lt;h3 class="text-left heading">
Nightly builds
&lt;/h3>
&lt;p>Nightly builds prepare a compiled and packaged version of the software, every night at 6am UTC, for:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="https://github.com/aurelienpierreeng/ansel/blob/master/.github/workflows/lin-nightly.yml" title="External link" target="_blank" rel="noopener noreferrer nofollow" >Linux&amp;thinsp;&lt;sup class="icon">&lt;i class="fa fa-external-link-alt">&lt;/i>&lt;/sup>&lt;/a>,&lt;/li>
&lt;li>&lt;a href="https://github.com/aurelienpierreeng/ansel/blob/master/.github/workflows/win-nightly.yml" title="External link" target="_blank" rel="noopener noreferrer nofollow" >Windows&amp;thinsp;&lt;sup class="icon">&lt;i class="fa fa-external-link-alt">&lt;/i>&lt;/sup>&lt;/a>,&lt;/li>
&lt;li>MacOS is currently disabled.&lt;/li>
&lt;/ul>
&lt;p>The newest binary files are automatically added to the &lt;a href="https://github.com/aurelienpierreeng/ansel/releases/tag/v0.0.0" title="External link" target="_blank" rel="noopener noreferrer nofollow" >pre-release&amp;thinsp;&lt;sup class="icon">&lt;i class="fa fa-external-link-alt">&lt;/i>&lt;/sup>&lt;/a> assets, are posted on a &lt;a href="https://matrix.to/#/#ansel-builds:matrix.org" title="External link" target="_blank" rel="noopener noreferrer nofollow" >Matrix channel&amp;thinsp;&lt;sup class="icon">&lt;i class="fa fa-external-link-alt">&lt;/i>&lt;/sup>&lt;/a> so users can subscribe to updates, and can be downloaded through (constantly up-to-date) permalinks at:&lt;/p></description></item><item><title>Websites</title><link>https://ansel.photos/uk/contribute/website/</link><pubDate>Thu, 01 May 2025 00:00:00 +0000</pubDate><updated>Thu, 01 May 2025 00:00:00 +0000</updated><guid>b373800da74107f247d3f517f80403df4bcd00ea0b7d7b83d5e8efe056f9c53c</guid><description>&lt;p>Ansel website is built using &lt;a href="https://github.com/gohugoio/hugo/releases/tag/v0.146.7" title="External link" target="_blank" rel="noopener noreferrer nofollow" >Hugo 0.146&amp;thinsp;&lt;sup class="icon">&lt;i class="fa fa-external-link-alt">&lt;/i>&lt;/sup>&lt;/a>. This is a static website generator that allows to build very fast website from Markdown files. A custom template and a lot of custom shortcodes have been built for Ansel. You will need to &lt;a href="https://gohugo.io/installation/" title="External link" target="_blank" rel="noopener noreferrer nofollow" >install Hugo extended version&amp;thinsp;&lt;sup class="icon">&lt;i class="fa fa-external-link-alt">&lt;/i>&lt;/sup>&lt;/a> on your computer first, although minor changes can be made directly to the Markdown files without building the whole website.&lt;/p></description></item></channel></rss>