Re: [Gimp-web] Help to registry.gimp.org

[Joao S. O. Bueno]

Hi Peylight  -


So, one of the ideas that come through is that what the KDE folks have
for their  "KDE Store" might attend everything we'd need on the server
side. (Given the rper diplomacy and comunication, we might evenbe able
to share the install and servers and not have to run our own) .

Then, with that, and a GIMP plug-in we could have something in-app to
manage resources  - that would be the "best possible scenario" for
some people working on GIMP.

(Don't expect consensus though  - things are in early stage, and
people may go passionate).

But as a first step, if you are willing, you might try to check the
exact software and capabilities run by the Kde Store, and get us in
touch with their maintainers -
(Yes, getting in touch with people and keeping porper contact is also
part of the volunteer work that has to be done)

   js
  -><-

On 22 April 2017 at 10:39, Pat David  wrote:
> Hi peylight!
>
> We have some ideas about possibly federating plugin repositories and making
> them available though an interface on GIMP, but we're always glad to hear
> suggestions or ideas! What do you have in mind?
>
> Pat
> On Fri, Apr 21, 2017 at 3:45 PM peylight  wrote:
>
>> Hello all
>>
>> I see a message in http://registry.gimp.org/ address and i got sad.
>>
>> My knowledges about security and websites are good. So as an information
>> security specialist, I'd be glad to help GIMP web sites team to make
>> more secure websites (If you need).
>>
>> --
>> Best Regards,
>> peylight
>>
>> ___
>> gimp-web-list mailing list
>> gimp-web-list@gnome.org
>> https://mail.gnome.org/mailman/listinfo/gimp-web-list
>>
> --
> https://patdavid.net
> GPG: 66D1 7CA6 8088 4874 946D  18BD 67C7 6219 89E9 57AC
> ___
> gimp-web-list mailing list
> gimp-web-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gimp-web-list
___
gimp-web-list mailing list
gimp-web-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-web-list

Re: [Gimp-web] 2.8 Splash Screen Attribution

[Joao S. O. Bueno]

The last one I was involved with was the 2.2 version one.  :-p


On 28 July 2016 at 15:55, Pat David  wrote:
> per mitch from irc, I've added the 2.8 splash screen to
>
> http://www.gimp.org/about/splash/stable.html
>
> but I'm not sure who the author is - could someone please point me to the
> author so I can attribute properly?
>
> Thanks!
> pat
> --
> Pat David
> https://pixls.us
> http://blog.patdavid.net
> ___
> gimp-web-list mailing list
> gimp-web-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gimp-web-list
___
gimp-web-list mailing list
gimp-web-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-web-list

Re: [Gimp-web] Tutorial about sharpening using IWrap tool

[Joao S. O. Bueno]

I think you mean  "IWarp" tool?

On 10 April 2016 at 23:42, Pat David  wrote:
> Thanks for the share!  I'll be travelling to LGM this week and likely
> unable to get to it before the following week at the soonest (assuming
> someone else doesn't get it ported first).
>
> I'll have a more detailed look as soon as I get a moment.  Are you willing
> to license the text of the tutorial as at least creative commons,
> by-attribution, share-alike?
>
> On Sun, Apr 10, 2016 at 2:34 PM Nicolas Belleville <
> belleville.nico...@yahoo.fr> wrote:
>
>> Hi
>>
>> I'd like to share an idea I had to sharpen a blurred photo.
>> The idea is to use the IWrap tool to shrink the blurred edges.
>> I made a tutorial, attached to this email.
>>
>> Please don't hesitate to give me feedback.
>> The images have been taken by myself and I hereby declare them as public
>> domain.
>> I can provide the jpg files as well if needed.
>>
>> You can add this tutorial to the gimp website if you want.
>>
>> Thanks
>>
>> Nicolas Belleville
>>
>> --
> Pat David
> https://pixls.us
> http://blog.patdavid.net
> ___
> gimp-web-list mailing list
> gimp-web-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gimp-web-list
___
gimp-web-list mailing list
gimp-web-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-web-list

Re: [Gimp-web] [Gimp-developer] Gitlab as a replacement for registry.gimp.org

[Joao S. O. Bueno]

An asset manager is undoubtedly  something  needed very badly -

There are some features that would be needed - which Jehan summarized quite
well in an e-mail sent about 2 years ago (I remember the date because I was just
back from Leipzig)

At first, I think requiring all assets to be in a git repository (git
uses URLs - no need
to require a specific provider) - would itself be overkill. So maybe,
just make content
'uploadable" might be enough. On the other hand, gitlab might provide
ownership and content meta-information in a way we would not need to
care about them -
just a system for one to enter a git (gitlab) URL and branch name - maybe
requiring certain information to be in the repository.

Curation of assets remains one of the hardest points - it might be a
_lot_ of _boring_ work -
and even somewhat dangerous - but still, I can imagine 2 categories of assets -
one endorsed by the "GIMP team" - - i.e. curated - with no dangerous
scripts/plug-ins,
and a "watch yourself"   mode in which anything could be downloadable.


Either way- wathever is designed to register GIMO assets server side,
a Python program can be made, to
run as a GIMP plug-in, that would provide a search, download and
install interface for things
registered on the server side. This program is not a huge thing to do
and would effectively provide GIMP
with its own "asset-store".

Anyway - just to get the ball rolling -
I suppose this could be a topic with its own BoF session in London

On 1 April 2016 at 17:32, Pat David  wrote:
> Continuing on some discussions from irc...
>
> Registry.gimp.org is down for the count.
>
> I was thinking recently about some ideas for a possible replacement.
> Mostly thinking along the lines of what made the registry work well for
> folks.
>
> In the rest of this email, I'll use the term "asset(s)" to refer to things
> like plug-ins, scripts, or brushes/gradients/curves/other assets.
>
> Some essential functionality based on the old registry drupal instance:
>
> 1. Upload/Download assets for GIMP.
> 2. Describe the asset (usually by the uploader).
> 3. Comment on the assets.
>
> This was handled previously by using drupal, which treated each entry as a
> post/node that included the ability to upload files, write about the files
> as a post, and had comment threads below it.
>
> Keeping this functionality would be good, I think.  The ability to post an
> asset is a given, but the ability to interact around it helps foster the
> community (and provides nice feedback for the authors).
>
> From those thoughts, what would be nice to have in a replacement:
>
> 1. Provide at least the same previous functionality (as listed above).
> 2. Managed or easier to manage and keep updated.
> 3. Easier account management.
> 4. Collaborative environment for shared assets
> 5. Support possible GIMP integration in the future (one-click asset
> install?).
>
>
>
> GitLab?
> ==
>
> Initially, I had thought Github might be a good option for this but given
> its closed-source nature decided to investigate something like GitLab
> instead.
>
> I like this idea personally due to some nice infrastructure:
>
> 1. The service is hosted + managed (and available as Free Software just in
> case we felt we needed to break out and host it ourselves).
> 2. The service integrates OAuth sign-in using a few different account types
> (lowers barrier to entry to participate).
> a. they use accounts, Google, Twitter, Github, or bitbucket accounts
> for sign-in.
> 3. Projects maintain all the git-goodness for control and tracking
> 4. Projects created as a git project can have a full description/README
> along with issue tracking integrated in the site
>
> So, we can fulfill the original registry functionality and get the added
> benefit of a git infrastructure for those wanting to contribute, user
> accounts using OAuth to make it easy to participate, and the ability to do
> some interesting things (git submodules).
>
> In speaking with Jehan about this, we should also consider what might be
> needed to support the ability to install assets from within GIMP in the
> future easily.
>
>
> Organization
> =
>
> Jehan suggested that each script/plugin/asset have it's own git repo.
> This would be handy, particularly if script authors did this as well (as it
> considerably eases the inclusion of external repos as submodules).
> However, akk points out that many folks don't (won't?) organize their repos
> in this way (it gets a little... unwieldy pretty quickly if you have many
> scripts).
>
> I'd like some input on what would make the most sense or work best for
> possible organization of repos.
>
> I was also thinking that we could include some simple metadata in both any
> script files and the README.md files as a means to possibly help parsing
> relevant information for automated inclusion at a later date (GIMP plug-ins
> installer type of idea).
>
>
> Curation
> ==
>
> Initially I was thinking that curating 

Re: [Gimp-web] [Gimp-developer] Gitlab as a replacement for registry.gimp.org

[Joao S. O. Bueno]

On 1 April 2016 at 18:14, Kasim Ahmic  wrote:
> I personally am a huge supporter of redoing the registry, and I like the 
> ideas you've proposed here. My only concern is one that was actually brought 
> up by someone else a few months ago; registry integration within GIMP and the 
> possibility of viruses.
>
> I don't quite remember who mentioned it, but they brought up that registry 
> integration within GIMP itself could potentially open the doors to viruses 
> unless a virus detection feature was built into GIMP as well. Now, I'm not 
> entirely sure how true this is but I would like to hear a final say on this 
> whether this is an actual issue or not.
>
> If it is an issue, what would be the best way to handle it? I'd imagine that 
> building virus scanning within GIMP would take quite a long time and be 
> pretty impractical. As such, I would suggest that we go with a self hosted 
> solution so that we could incorporate a virus scanner on there to scan all 
> the uploaded assets. Either that, or a hosted solution like GitLab that come 
> with a virus scanning option along with it.
>
> Again, not sure how much of an issue this even is. Just a thought.

So - this would be one of the main  purposes of a "curation" -
Only non-malicious assets would be made available as "safe" from the
server-side.
Having security features on the client side (i.e. on the computer of
the person running GIMP), is
not feasible: one single line of code in a rogue plug-in can wipe the
user harddrive.
. Assuring assets are safe, even if few, and can't be maliciously
modified, in the repository is hard enough -
but can be done.

The hard-to-balance thing is allowing publication of assets by a large
amount of people, and having process/volunteers
to ensure these assets are safe. Either way, I think the download and
install should be done with a few clicks from wthin GIMP itself -
we don't have to burden users to locate the file in a browser,
download it, copy it to the right folder, set its file properties
if that is not needed. If the assets represent a danger, they will
represent an equal danger in this "manual way".


>
>  - Kasim Ahmić
>
> Sent from my iPhone
>
>> On Apr 1, 2016, at 4:32 PM, Pat David  wrote:
>>
>> Continuing on some discussions from irc...
>>
>> Registry.gimp.org is down for the count.
>>
>> I was thinking recently about some ideas for a possible replacement.
>> Mostly thinking along the lines of what made the registry work well for
>> folks.
>>
>> In the rest of this email, I'll use the term "asset(s)" to refer to things
>> like plug-ins, scripts, or brushes/gradients/curves/other assets.
>>
>> Some essential functionality based on the old registry drupal instance:
>>
>> 1. Upload/Download assets for GIMP.
>> 2. Describe the asset (usually by the uploader).
>> 3. Comment on the assets.
>>
>> This was handled previously by using drupal, which treated each entry as a
>> post/node that included the ability to upload files, write about the files
>> as a post, and had comment threads below it.
>>
>> Keeping this functionality would be good, I think.  The ability to post an
>> asset is a given, but the ability to interact around it helps foster the
>> community (and provides nice feedback for the authors).
>>
>> From those thoughts, what would be nice to have in a replacement:
>>
>> 1. Provide at least the same previous functionality (as listed above).
>> 2. Managed or easier to manage and keep updated.
>> 3. Easier account management.
>> 4. Collaborative environment for shared assets
>> 5. Support possible GIMP integration in the future (one-click asset
>> install?).
>>
>>
>>
>> GitLab?
>> ==
>>
>> Initially, I had thought Github might be a good option for this but given
>> its closed-source nature decided to investigate something like GitLab
>> instead.
>>
>> I like this idea personally due to some nice infrastructure:
>>
>> 1. The service is hosted + managed (and available as Free Software just in
>> case we felt we needed to break out and host it ourselves).
>> 2. The service integrates OAuth sign-in using a few different account types
>> (lowers barrier to entry to participate).
>>a. they use accounts, Google, Twitter, Github, or bitbucket accounts
>> for sign-in.
>> 3. Projects maintain all the git-goodness for control and tracking
>> 4. Projects created as a git project can have a full description/README
>> along with issue tracking integrated in the site
>>
>> So, we can fulfill the original registry functionality and get the added
>> benefit of a git infrastructure for those wanting to contribute, user
>> accounts using OAuth to make it easy to participate, and the ability to do
>> some interesting things (git submodules).
>>
>> In speaking with Jehan about this, we should also consider what might be
>> needed to support the ability to install assets from within GIMP in the
>> future easily.
>>
>>
>> Organization
>> =
>>
>> Jehan suggested that 

Re: [Gimp-web] Need help to translate the Gimp website?

[Joao S. O. Bueno]

just hold there: is the structure you built capable of handling
multible international versions?

If so, a guide on how to generate the localized versions would be a
nice thing to have.

On 30 November 2015 at 15:25, Pat David  wrote:
> Alex,
>
> I know that some folks may not be comfortable in git just yet. If you'd
> like an easier way to get started, you can view the source tree for the
> website online here: https://git.gnome.org/browse/gimp-web/tree/?h=testing
>
> You can look for files that end in .md, as these are the source files that
> will need to be translated. If you can translate one and email to me or the
> list, we can start making some headway on a process! Thanks again for
> volunteering!
>
> pat
> On Fri, Nov 27, 2015 at 3:17 PM Pat David  wrote:
>
>> -- Forwarded message -
>> From: Pat David 
>> Date: Fri, Nov 27, 2015 at 3:16 PM
>> Subject: Re: [Gimp-web] Need help to translate the Gimp website?
>> To: Alex 
>>
>>
>> Hi Alex!
>>
>> I wrote a preliminary how-to for contributing translations.
>>
>> http://testing.gimp.org/about/meta/translating.html
>>
>> There's some content on the meta page here that might help:
>> http://www.gimp.org/about/meta/
>>
>> If you don't want to use git to get the website source, you can translate
>> an individual markdown file at a time...
>>
>> I might be able to set something up on github if it will help make things
>> easier for you. (I want to make it easy for people to be able to
>> contribute).
>>
>> On Fri, Nov 27, 2015 at 2:45 PM Alex  wrote:
>>
>>> Git git git...
>>> I translated Leanote on Github.
>>> Not sure it is the same thing you're talking about though.
>>>
>>> If by building the site locally, you mean download the entire website on
>>> my localhost, I think I could do that. I guess then I would have to go
>>> through the code to translate the text. Or maybe I'm just wrong?
>>> Could you tell me more?
>>>
>>>
>>>
>>>
>>> Le 27/11/2015 21:42, Pat David a écrit :
>>>
>>> Hi Alex!
>>>
>>> Yes, we would love to have help translating pages in the site!  Are you
>>> familiar with git and can you try to build the site locally?  I can walk
>>> you through the process if needed to get things setup!
>>>
>>> On Fri, Nov 27, 2015 at 2:41 PM Alex 
>>> wrote:
>>>
 Hi,

 I'm Alex, and I'm a huge fan of Gimp.
 If I refer to this page, you plan to internationalize the Gimp website.
 The cool part is that I'm French, and I would be happy to help you for
 this.
 But first of all, do you still need help for that?

 Thanks

 Alex
 ___
 gimp-web-list mailing list
 gimp-web-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/gimp-web-list

>>>
>>>
> ___
> gimp-web-list mailing list
> gimp-web-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/gimp-web-list
___
gimp-web-list mailing list
gimp-web-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-web-list

Re: [Gimp-web] SGO text

[Joao S. O. Bueno]

Hi Pat !

Thank you for the effort you are putting into this.
I myself am busy to take a careful luck now - but a far as I can see
you are taking the right decisions.

Would you mind pinging me later this week? I think I can come up with
some text for
the programing algorithms part.



Regards,

  js
 --

On 23 August 2015 at 23:28, Pat David patda...@gmail.com wrote:
 So, I'm currently poking at the main page for the WGO redesign.  I had
 mentioned in a previous mail the product vision from the vision briefing
 whose main points concerning the product vision were:

 A. HIgh-end photo manipulation
 B. Creating original art.
 C. Production elements (graphical design)
 D. Programming algorithms.

 Alexandre mentioned that there were some complaints about tasks
 specifically relevant to desktop publishing not being mentioned in the
 vision.

 I am looking for any input if anyone would like to offer some on the
 verbiage of a few key places on the site right now (http://static.gimp.org).

 First, the introductory text in the very first section after the name,
 Wilber, and a download link.  It currently reads:

 ===
 ## The Free  Open Source Image Editor

 This is the official GIMP website.
 GIMP is an acronym for GNU Image Manipulation Program. It is the Free and
 Open Source, cross platform image editor available for GNU/Linux, OS X,
 Windows and more. It contains information about downloading, installing,
 using, and enhancing it. This site also serves as a distribution point for
 the latest releases. We try to provide as much information about the GIMP
 community and related projects as possible. Hopefully you will find what
 you need here. Grab a properly chilled beverage and enjoy...
 ===

 I feel that it gets the most important points up front (official site, GIMP
 is an acronym..., cross platform, image editor).  Are there other points
 that need to be made in that first introductory paragraph?

 The next few sections I had broken out to hopefully address/illustrate each
 of the vision statement points.  I can use any input for those sections as
 well if anyone has thoughts:

 ===
 ## High Quality Photo Manipulation

 GIMP provides the tools for needed for high quality image manipulation.
 From retouching to restoring to creative composites, the only limit is your
 imagination.
 ===

 and (A big thanks to David Revoy for allowing use of some of his images),

 ===
 ## Original Artwork Creation

 I have nothing for this section yet to address original artwork creation.
 ===

 I still have to make:

 ===
 ## Production Elements (graphical design?)
 ===

 ===
 ## Programming algorithms (i seriously have no idea what to put here)
 ===

 I think it might be nice to also include something to place GIMP within the
 context of a F/OSS workflow for multiple use-cases, photography, web
 production design, and desktop publishing - I'm still thinking on this.

 So, anyone care to unleash their inner marketing-Hemingway?  Otherwise I'm
 going to take my best guess at things and just hope I don't screw up too
 bad...  (I just realized that almost my entire life can be described in
 that one sentence... :) ).

 pat
 ___
 gimp-web-list mailing list
 gimp-web-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/gimp-web-list
___
gimp-web-list mailing list
gimp-web-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-web-list

Re: [Gimp-web] Would like to be a new user

[Joao S. O. Bueno]

The current color scheme was put together for GIMP 2.4.

While it has been refreshing for a mostly BW web for a while, I agree,
and think  most people do, that we are a bit tired of that color-scheme
for now. And for others, as Bob wrote, it can even be a major showstopper.

All in all, if you could take a pick for an alternate style, I'd be
all for it. we might throw a new
scheme as official as soon as possible - anyway, if you get the write
another CSS and people
prefer to wait for a new GIMP release to change the main page scheme,
I'd happily fiddle with some
mechanism to allow one to choose styles on the page.


Regards,

  js
 --


On 17 July 2014 11:18, Pat David patda...@gmail.com wrote:
 I could take a stab at creating an alternate stylesheet - but would we need
 to implement a way to make choosing alternate styles easy/ier for an end
 user?  Many people may not want to install a chrome extension just to
 choose alt styles (and there should be a way to make that mod on the fly,
 iirc).


 On Wed, Jul 16, 2014 at 8:41 PM, Michael Schumacher schum...@gmx.de wrote:

 On 11.07.2014 18:37, Bob wrote:

  I would like to know more about your program but one thing I can't get
  around and allow me to use your Tutorials is this:
  The graphic coloring scheme is user defeating. What I mean is that by
  using white text on colored backgrounds make it tiring to view to my
  eyes and dissemble/think about what you are attempting to convey.

 The web site uses this style sheet:
 https://git.gnome.org/browse/gimp-web/plain/style/wgo.css

 If you helps us and provide a modified style with different colors (and
 maybe other changes), we could add that and allow the users to select
 from different styles (like this:
 http://www.w3.org/Style/Examples/007/alternatives.en.html).


 --
 Regards,
 Michael
 GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
 ___
 gimp-web-list mailing list
 gimp-web-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/gimp-web-list




 --
 pat david
 http://blog.patdavid.net
 ___
 gimp-web-list mailing list
 gimp-web-list@gnome.org
 https://mail.gnome.org/mailman/listinfo/gimp-web-list
___
gimp-web-list mailing list
gimp-web-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-web-list