I was also perusing redmine and found duplicates and issues which have comments 
the issue should be closed.
I can help either port redmine to github, or help manage the issue database on 
occasion. (I would want rules to follow on how to handle issues).
Lastly, I would also be interested in funding some bounties.
Tim
------ Original message------From: Aurélien PierreDate: Fri, Sep 7, 2018 11:25 
PMTo: darktable;Cc: Subject:[darktable-dev] How do you feel about code bounties 
?

    Hi everyone,
    looking at the Redmine feature requests,
      it seems that a lot of legitimate requests are left idle, and some
      have been so for several years, generating duplicates. Most of
      these features are cosmetic User Interface improvements or making
      variables writable, such as :
    
      delete some
          EXIF+GPS meta-data in exported files (for privacy)

      
      set the
          export file resolution from paper size and printing DPI,
        set the DPI value right in EXIF,

      
      add/edit
          unique names/titles for modules instances, also within
          styles, 

      
      decompose
          the darkroom history by module AND module controls
        (decrease the history granularity),
      add more JPEG exportation options (progressive,
        optimized,
        subsampling),
        

      
      apply conditional styles automatically (the same way as the
        presets of the modules),
      make styles hierarchical (to clean-up the list),
      allow drawn
          mask edition (size, feathering, opacity) from the masks
        list and keyboard input values, 

      
      lock
          position and size of drawn masks for safe panning/zooming,
      EXIF
        and IPTC
        management/edition requests (date, time, names of lenses without
        processor, scans with no/wrong metadata),
      create
          arbitrary collections/catalogs of images (ex : family,
        perso, assignments),
      implement
          ESC and RETURN shortcuts in every dialog to cancel and
        validate,
      implement a
          coarse/fine tuning option to increment/decrement values
        with the mouse wheel
      lots of small GTK glitches with scroll
          bars, lighttable selections
        and hovers,
      link exported pictures paths to original RAW files,
      allow to set the UI main color and create user-friendly
        theme/template (whitout editing CSS),

      
      etc.
    
    Some are more algorithmically challenging :
    
      make the RGB
          gains independant in wavelets/non-locals means denoising
        module,
      rotate/flip the sampling patch in the spot removal module and
        in the freshly merged retouch module,
      add a color correction on A and B channels to fix the
        desaturation happening in the local contrast module (laplacian)
        with heavy settings,
      display the
          locked AF point on previews
      detecting
          duplicates and similar pictures in database

      
      etc.

      
      plus all the Windows portability issues.

      
    
    And there are still #TODOs in the source code.

    
    Most of these changes are for sure not the most challenging and
      don't make for the sexiest coding party, so I have no trouble
      imagining how little appealing they can be to hobbyist developers,
      but they are nonetheless useful and game changing for
      professionnals who are bound to efficiency constraints. 

    
    I find quite remarkable the dramatic improvements that software
      such as Blender have known in the past decade, and though I get
      why dt developers aren't thrilled by the admin overhead involved
      in a similar fundation to pay full-time developpers, I think the
      above requests will stay idle for some more time if we don't go
      next-level. That would be a shame considering the core is stable
      and sane, and what is needed is mainly cosmetic.

    
    As more and more professional photographers adopt dt in their job
      and are asking for more efficency-driven features, I know that
      some would be happy to fund developpers to smooth all the sharp
      edges listed above. For now, the features that the developpers
      don't need don't stand a chance to appear in the software.

    
    So I found a platform where you could create a bounty for each
      feature request/bug on Redmine, have users/donators fund the
      requests they want in a crowdfunding way, hire freelancers to do
      it, and take care of the payment : https://www.bountysource.com/.
      You can create a dt group, link it to Github,
      open/accept/close/pay the bounties, etc. Actually, it seems that
      darktable has already a project page, but only linked to the
      Github tracker :
      https://www.bountysource.com/teams/darktable/issues. 

    
    Shouldn't we merge Github issues and Redmine bugs/FR, and promote
      bountysource ?

    
    Cheers,
    Aurélien.

    
  


___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org



___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Reply via email to