0GIMP Meeting Agenda
- Merchandising
- Shirts
- Design selection
- Existing designs
- New design
- to be decided by the usual suspects
- Designs contributed by people we reach out to
- Design guidelines
- Purpose
- Outreach
- Sell them as well
- Doing
- Simon
- Prices, options
- Kernelconcepts
- sizes and cuts
- Hoodies
- Design selection
- Purpose
- Doing
- Stickers
- Designs
- Roll of stickers
- Large sheets create waste
- Lets start small with Wilber and Gegl stickers on rolls
- Doing
- Other things
- No useless crap
- ?hats, socks, scarves, tote bags, laptop sleeves, pencil cases, notepads, mouspads, patches
- We have standards
- Environmental
- Ethical (no sweatshops)
- Guidelines
- Deadlines
- Website
- Review
- Does it lack anything?
- Internationalisation
- Technically possible
- Contribute translation button?
- Language negotiation
- Lets start on the most-visited pages
- Https://www.gimp.org/about/meta/
- Add Meta information to a README in the site root. (particularly translation information and workflow) [patdavid]
- Dynamic header image (rotate out different images on load?) [patdavid]
- Guidelines
- Document how the current ones were chosen [patdavid]
- Licensing (cc-by-sa at least?)
- Switch/cycle the imageshown in long-term intervals
- Like every six months
- Jauftomatically from a set
- ?interaction with help and releases
- Copy of gimp 2.9 help with a disclaimer
- Interlinking help and tutorials
- Do we link to third-party sites?
- We try to get permission to use them (tutorials) on gimp.org (licensing)
- Should more things be on all pages?
- Donations options shown on all the pages (header bar)
- Include Bitcoin + PayPal on the header everywhere!
- More (small) GIMP hacker meetings
- Funds are not an issue
- Needs an organizer/herder
- Gnome assigns a theme to their meetings of this kind (e.g. specific goal/feature)
- All expenses have to be covered
- Proposals with goals
- Reports with results
- Sending people to other similar meetings
- Release procedure see https://mail.gnome.org/archives/gimp-developer-list/2016-April/msg00062.html
- Enhancement request policy, see https://mail.gnome.org/archives/gimp-developer-list/2016-April/msg00069.html
- Plug-in registry
- Server requirements
- Infrastructure
- Administration/management
- Make it obvious to users who wrote a plug-in
- Find a server to host it
-
- What do we need for 2.10
- Todo list for peple to identify action items
-
- Blockers:
- Finish libgimp review, deprecate everything that's not wanted
- Libgimp drawable color API
- Libgimp lcms API (final review only)
- Libgimp metadata API (final review only)
-
- All bugs with 2.10 milestone, or move them to the 3.0 milestone
- Sort out high bit depth menu (e.g. probably remove 64 bit)
- Support layer masks on layer groups
- Warp tool algorithm is broken
- Foreground select tool (make sure works properly again)
- Clean out duplicate menu entires (gimp / gegl impl)
- IScissors tool (make sure works properly again)
- Make sure blocking GEGL ops don't block the GUI (at least have an indication)
- PSD plug-in (final review)
- TIFF plug-in (final review)
- PNG plug-in (final review)
- Update API docs to at least have all new functions
-
- Nice to have:
- Port all plug-ins that still use the old pixel region API to GEGL
- Metadata editing
- Make sure windows builds are properly automated
- Make sure OSX builds are properly automated (Kris will work on this)
- OSX: Kris needs to finish and commit his new scanner image acquire plugin
- Seamless clone tool
- Unified transform tool (would be nice to be closer to spec)
- NPD tool (fix and move out of playground)
- Handle Transform tool (fix and move out of playground)
- Seamless integration with darktable
- Update API docs to properly document all new functions
-
-
- Do we need warnings for outdated third-party plug-ins?
- For example by adding a new register function
- Announce upcoming 3.0 breakage publically
-