Hello Pat,

Am 04.11.2015 um 16:04 schrieb Pat David:

I have a few things to still work on, but can use other eyeballs on the site to spot things I may be too close to. So, please, if you have a moment look at the site and take a moment to note any issues that you may see

Much appreciated, btw! What i have spotted:

On http://static.gimp.org/: There is a typo in Section 'High Quality Photo Manipulation': 'GIMP provides the tools for needed for high quality image' (delete word) -------^

Things you might consider: - Section 'Extensibility & Flexibility': Add Link to http://registry.gimp.org/

- A new Section "Get Involved": ~ "GIMP is a community project which is driven by volunteers with a wide range of interests and skills. Have a look how you can become part of the community" with link to gimp.org/develop/. *)

On http://static.gimp.org/develop/ - Section "GIMP Development Links":

"Martin Nordholts GIMP Blog -- What happens in GIMP development." ^--- The blog is not active anymore, this item can be deleted.

best regards, yahvuu

*) Reasoning: While this information may already be contained in the intro section in a condensed form, i feel it deserves a prominent place on par with the product vision items. Kinda placeholder for a yet-to-be-written project vision.

Judging by the amount of people who manage to get through to the mailings lists despite having a basic understanding of the project's volunteer nature, it won't hurt to give a gentle introduction here. GIMP may be the first encounter with a free software project, in particular for innocent windows platform users.

On Wed, 2015-11-04 at 15:04 +0000, Pat David wrote:

I am still working out the best way to link social + donation links without
tracking our users or compromising security.

This seems like the obvious solution to me: You can avoid adding trackers by leaving out any iframes or JavaScript that Facebook or Paypal might generate for you. Don't use any plugins or whatever, just create normal anchor tag () hyperlinks, possibly wrapped around the social media logos/icons. Is there any reason that wouldn't work?

~Andrew

On 11/04/2015 04:04 PM, Pat David wrote:

Hi all!

You may or may not realize this, but a neat GIMP anniversary is fast approaching. On November 21, we will mark 20 years since Peter Mattis announced a beta of the General Image Manipulation Program on a few different mailing lists...

http://static.gimp.org/about/prehistory.html

As such, I thought it might be fun to use it as a target date for possibly releasing the website redesign. (http://static.gimp.org)

We've got HTTPS now, too:

https://static.gimp.org

Note: Some links might still lead to HTTP sites, or lead into SSL errors

The SSL certificate was issued by Let's Encrypt, a project that aims to get each and every web server to use encryption:

https://letsencrypt.org/

Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD

The site looks great! I only have a few minor cosmetic concerns though:

1. The About GIMP, Documentation, Donations, Get Involved, and Tutorial links in the footer and menu bar don't have icons next to them. What's strange is that on the mobile version, the Documentation and Tutorials links both have icons. I personally think these would look nice: - About GIMP: Not sure but maybe a question mark? - Donations: A simple dollar sign
- Get Involved: A handshake

2. The images for the GIMP icon in the menu bar and footer are much lower quality than the other icons. I'm only looking at the site on my phone so I can't tell for sure but I'm gonna assume that the other icons are vectors whereas the GIMP icon is a bitmap image. Also, the icons for Scribus, Inkscape, and SwatchBooker should either be halved in size or replaced with higher DPI icons for hi-res devices. Perhaps do the same thing with the "Graphic Design Elements" and "Programming Algorithms" backgrounds but loading higher DPI images for those might start causing load issues for people on mobile devices so I don't think that's too important personally.

3. The Recent News title on the News page doesn't have a border and shadow underneath it like the Documentation, Tutorials, and other titles on their respective pages do.

4. The OpenHub activity tracker's design and style doesn't fit with the rest of the site. But that's just mostly color scheme and font.

Other than that, everything else looks great!

A far as the GIMP registry goes, part of me wants to preserve it and just update Drupal to the latest version (assuming it's backwards compatible) and hope it has better spam protection. But on the other hand, I'd like to see it redone entirely in a way that's built for spam protection from the group up. They both have their pros and cons:

Fix the Current Site Pros:
- Should be relatively simple.
- No loss of plugins and posts.
- Current registry users won't have to learn a new system for posting plugins or responses.

Cons: - AFAIK, there's no real version control on Drupal making it difficult for users to find the version of a plugin their looking for. - Potential for future problems due to old server configs.

Create an All New Site Pros:
- We can rest assured spam won't be an issue. - We can modify it to our and the users needs from the ground up.

Cons: - Will be a massive undertaking.
- Will have the need for moving over old plugins from the old site.

Those are just my thoughts on it.

Kasim Ahmic

Sent from my iPhone

On Nov 8, 2015, at 10:27 AM, Pat David wrote:

Thank you for taking the time to provide feedback!

On Wed, Nov 4, 2015 at 4:37 PM yahvuu wrote:

On http://static.gimp.org/: There is a typo in Section 'High Quality Photo Manipulation': 'GIMP provides the tools for needed for high quality image' (delete word) -------^

Awesome! Thank you for that - fixed in 41b3f77

Things you might consider:
- Section 'Extensibility & Flexibility': Add Link to http://registry.gimp.org/

I agree with adding this link to the section, but am not sure if we should hold off until we decide what we want to do with the registry (or just go ahead and link it, and let folks get the archived version until we switch things up). The registry is in a poor state, and there's not much we can do about it from our end (old drupal install that is vulnerable to spam).

I was going to address some ideas in a separate thread on the ML later at some point and see what everyone thought.

- A new Section "Get Involved":
~ "GIMP is a community project which is driven by volunteers with a wide range of interests and skills. Have a look how you can become part of the community" with link to gimp.org/develop/. *)

Great idea! I'll have a look at integrating a section like this. Along that same idea, we should probably have a look at cleaning up /develop/ and making it a bit cleaner, simpler, clearer? We've already had a couple of commits for those pages, yay!

On http://static.gimp.org/develop/ - Section "GIMP Development Links":

"Martin Nordholts’ GIMP Blog -- What happens in GIMP development." ^--- The blog is not active anymore, this item can be deleted.

I see that it's not active, though the information is still archived there. Should we delete the link completely or mark it as inactive and leave the link to the old material? I'm not sure on this and am looking for some guidance/opinions from those who know more than me. :)

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

If we decide to rebuild the registry site from scratch, I think WordPress would be *much* easier to set up than Drupal or Joomla, and WordPress has pretty good spam filters via plugins officially sponsored by Automattic, the company developing. There are a lot of web CMS applications out there, but WordPress is by far the easiest to use among the PHP/MySQL stacks, and still pretty versatile for web development.
Either way, I think the GIMP Plugin Registry provides an important service. We shouldn't let it fall to the wayside.  On Sun, 2015-11-08 at 16:44 -0500, Kasim Ahmic wrote:

The site looks great! I only have a few minor cosmetic concerns though:

1. The About GIMP, Documentation, Donations, Get Involved, and Tutorial links in the footer and menu bar don't have icons next to them. What's strange is that on the mobile version, the Documentation and Tutorials links both have icons. I personally think these would look nice:
 - About GIMP: Not sure but maybe a question mark?  - Donations: A simple dollar sign
 - Get Involved: A handshake

2. The images for the GIMP icon in the menu bar and footer are much lower quality than the other icons. I'm only looking at the site on my phone so I can't tell for sure but I'm gonna assume that the other icons are vectors whereas the GIMP icon is a bitmap image. Also, the icons for Scribus, Inkscape, and SwatchBooker should either be halved in size or replaced with higher DPI icons for hi-res devices. Perhaps do the same thing with the "Graphic Design Elements" and "Programming Algorithms" backgrounds but loading higher DPI images for those might start causing load issues for people on mobile devices so I don't think that's too important personally.

3. The Recent News title on the News page doesn't have a border and shadow underneath it like the Documentation, Tutorials, and other titles on their respective pages do.

4. The OpenHub activity tracker's design and style doesn't fit with the rest of the site. But that's just mostly color scheme and font.

Other than that, everything else looks great!

A far as the GIMP registry goes, part of me wants to preserve it and just update Drupal to the latest version (assuming it's backwards compatible) and hope it has better spam protection. But on the other hand, I'd like to see it redone entirely in a way that's built for spam protection from the group up. They both have their pros and cons:

Fix the Current Site
Pros:
 - Should be relatively simple.
 - No loss of plugins and posts.
 - Current registry users won't have to learn a new system for posting plugins or responses.

Cons:  - AFAIK, there's no real version control on Drupal making it difficult for users to find the version of a plugin their looking for.
 - Potential for future problems due to old server configs.

Create an All New Site Pros:
 - We can rest assured spam won't be an issue.  - We can modify it to our and the users needs from the ground up.

Cons:  - Will be a massive undertaking.
 - Will have the need for moving over old plugins from the old site.

Those are just my thoughts on it.

Kasim Ahmic

Sent from my iPhone

On Nov 8, 2015, at 10:27 AM, Pat David wrote:

Thank you for taking the time to provide feedback!

On Wed, Nov 4, 2015 at 4:37 PM yahvuu wrote:

On http://static.gimp.org/:   There is a typo in Section 'High Quality Photo Manipulation':       'GIMP provides the tools for needed for high quality image'                  (delete word)  -------^

Awesome!  Thank you for that - fixed in 41b3f77

  Things you might consider:
    - Section 'Extensibility & Flexibility':       Add Link to http://registry.gimp.org/

I agree with adding this link to the section, but am not sure if we should
hold off until we decide what we want to do with the registry (or just go
ahead and link it, and let folks get the archived version until we switch
things up).  The registry is in a poor state, and there's not much we can
do about it from our end (old drupal install that is vulnerable to spam).

I was going to address some ideas in a separate thread on the ML later at
some point and see what everyone thought.

    - A new Section "Get Involved":       ~ "GIMP is a community project which is driven by volunteers with
a wide range of interests and skills. Have a look how you can become
part of the community" with link to gimp.org/develop/.  *)

Great idea!  I'll have a look at integrating a section like this.  Along
that same idea, we should probably have a look at cleaning up /develop/ and
making it a bit cleaner, simpler, clearer?  We've already had a couple of
commits for those pages, yay!

On http://static.gimp.org/develop/   - Section "GIMP Development Links":

    "Martin Nordholts’ GIMP Blog -- What happens in GIMP development."
      ^--- The blog is not active anymore, this item can be deleted.

I see that it's not active, though the information is still archived
there.  Should we delete the link completely or mark it as inactive and
leave the link to the old material?  I'm not sure on this and am looking
for some guidance/opinions from those who know more than me. :)

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

Triggering appropriate actions when users click a social or donation link could probably be added as URL queries to the linked address. I could help research the exact strings we'd need if you give me something specific to look for.
~Andrew
On Sun, 2015-11-08 at 15:29 +0000, Pat David wrote:

Hi Andrew!

On Thu, Nov 5, 2015 at 5:39 PM Andrew Toskin wrote:

This seems like the obvious solution to me: You can avoid adding trackers by leaving out any iframes or JavaScript that Facebook or Paypal might generate for you. Don't use any plugins or whatever, just
create normal anchor tag () hyperlinks, possibly wrapped around the
social media logos/icons. Is there any reason that wouldn't work?

Yes, this is the plan.  I was hoping to at least be able to build those links so that they trigger the appropriate action on the other (social) site side (pointing to and including meta information for the link post).

But yes, you're right.  In a nutshell the links will be static objects, using static assets that we host.  Nothing will happen on other sites without the explicit action of a user on our side (which I prefer personally). 

I would be willing to set it up. I have setup at least 5 wordpress sites for various uses before.
I also write scripts for it.
On Monday, November 9, 2015, Andrew Toskin wrote:

If we decide to rebuild the registry site from scratch, I think WordPress would be *much* easier to set up than Drupal or Joomla, and WordPress has pretty good spam filters via plugins officially sponsored by Automattic, the company developing. There are a lot of web CMS applications out there, but WordPress is by far the easiest to use among the PHP/MySQL stacks, and still pretty versatile for web development.
Either way, I think the GIMP Plugin Registry provides an important service. We shouldn't let it fall to the wayside. On Sun, 2015-11-08 at 16:44 -0500, Kasim Ahmic wrote:

The site looks great! I only have a few minor cosmetic concerns though:

1. The About GIMP, Documentation, Donations, Get Involved, and Tutorial links in the footer and menu bar don't have icons next to them. What's strange is that on the mobile version, the Documentation and Tutorials links both have icons. I personally think these would look nice:
- About GIMP: Not sure but maybe a question mark? - Donations: A simple dollar sign
- Get Involved: A handshake

2. The images for the GIMP icon in the menu bar and footer are much lower quality than the other icons. I'm only looking at the site on my phone so I can't tell for sure but I'm gonna assume that the other icons are vectors whereas the GIMP icon is a bitmap image. Also, the icons for Scribus, Inkscape, and SwatchBooker should either be halved in size or replaced with higher DPI icons for hi-res devices. Perhaps do the same thing with the "Graphic Design Elements" and "Programming Algorithms" backgrounds but loading higher DPI images for those might start causing load issues for people on mobile devices so I don't think that's too important personally.

3. The Recent News title on the News page doesn't have a border and shadow underneath it like the Documentation, Tutorials, and other titles on their respective pages do.

4. The OpenHub activity tracker's design and style doesn't fit with the rest of the site. But that's just mostly color scheme and font.

Other than that, everything else looks great!

A far as the GIMP registry goes, part of me wants to preserve it and just update Drupal to the latest version (assuming it's backwards compatible) and hope it has better spam protection. But on the other hand, I'd like to see it redone entirely in a way that's built for spam protection from the group up. They both have their pros and cons:

Fix the Current Site
Pros:
- Should be relatively simple.
- No loss of plugins and posts.
- Current registry users won't have to learn a new system for posting plugins or responses.

Cons: - AFAIK, there's no real version control on Drupal making it difficult for users to find the version of a plugin their looking for.
- Potential for future problems due to old server configs.

Create an All New Site Pros:
- We can rest assured spam won't be an issue. - We can modify it to our and the users needs from the ground up.

Cons: - Will be a massive undertaking.
- Will have the need for moving over old plugins from the old site.

Those are just my thoughts on it.

Kasim Ahmic

Sent from my iPhone

On Nov 8, 2015, at 10:27 AM, Pat David wrote:

Thank you for taking the time to provide feedback!

On Wed, Nov 4, 2015 at 4:37 PM yahvuu wrote:

On http://static.gimp.org/: There is a typo in Section 'High Quality Photo Manipulation': 'GIMP provides the tools for needed for high quality image' (delete word) -------^

Awesome! Thank you for that - fixed in 41b3f77

Things you might consider:
- Section 'Extensibility & Flexibility': Add Link to http://registry.gimp.org/

I agree with adding this link to the section, but am not sure if we should
hold off until we decide what we want to do with the registry (or just go
ahead and link it, and let folks get the archived version until we switch
things up). The registry is in a poor state, and there's not much we can
do about it from our end (old drupal install that is vulnerable to spam).

I was going to address some ideas in a separate thread on the ML later at
some point and see what everyone thought.

- A new Section "Get Involved":
~ "GIMP is a community project which is driven by volunteers with
a wide range of interests and skills. Have a look how you can become
part of the community" with link to gimp.org/develop/. *)

Great idea! I'll have a look at integrating a section like this. Along
that same idea, we should probably have a look at cleaning up /develop/ and
making it a bit cleaner, simpler, clearer? We've already had a couple of
commits for those pages, yay!

On http://static.gimp.org/develop/ - Section "GIMP Development Links":

"Martin Nordholts’ GIMP Blog -- What happens in GIMP development."
^--- The blog is not active anymore, this item can be deleted.

I see that it's not active, though the information is still archived
there. Should we delete the link completely or mark it as inactive and
leave the link to the old material? I'm not sure on this and am looking
for some guidance/opinions from those who know more than me. :)

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

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

John roper
President and CEO of Starlight Graphics Studio
Boston, MA USA
http://starlightgraphics.tuxfamily.org

Pat David (patdavid@gmail.com) wrote:

Keep the discussion on-list to help everyone keep track of what you may find.

Two minor issues:

Please consider making the body text more bold and more black.

For me the text is on the brink on the unreadable due to the lack of contrast. Given that we all age at a rate of 1s/s I'd appreciate that :)

See http://www.home.unix-ag.org/simon/files/weight-comparison.png for a comparison of the original and changing the weight to 400 (gimp.css:153) and color to #333 (home.css:2).

It might be worth looking at more pages than I did. For example the news item date is #aaa on white in a very small light font. If we don't want our visitors to read the text it would be better to remove the text instead :)

Bye,
Simon

simon@budig.de              http://simon.budig.de/

I just finished building a site that had many of the same features. Http://blenderstorm.tuxfamily.org check it out and tell me what you think. It was supposed to be a site for feature requests for Blender. It does have a forum though.

On Tuesday, November 10, 2015, Pat David wrote:

I'm actually sort of leaning towards the idea of possibly using a

discourse instance as a replacement for the registry. It would serve the dual purpose of incorporating a forum/comment system that we could use on the site as well (if we were so inclined).

Honestly, the existing functionality of the registry was pretty much

exactly this. I'll expand on my rationale a little later.

I'm personally not so sure that a Wordpress infrastructure would be the

most appropriate (but would be happy to hear thoughts around it).

On Mon, Nov 9, 2015 at 10:14 PM John Roper wrote:

I would be willing to set it up. I have setup at least 5 wordpress sites

for various uses before.

I also write scripts for it.
On Monday, November 9, 2015, Andrew Toskin wrote:

If we decide to rebuild the registry site from scratch, I think WordPress would be *much* easier to set up than Drupal or Joomla, and WordPress has pretty good spam filters via plugins officially sponsored by Automattic, the company developing. There are a lot of web CMS applications out there, but WordPress is by far the easiest to use among the PHP/MySQL stacks, and still pretty versatile for web development.
Either way, I think the GIMP Plugin Registry provides an important service. We shouldn't let it fall to the wayside. On Sun, 2015-11-08 at 16:44 -0500, Kasim Ahmic wrote:

The site looks great! I only have a few minor cosmetic concerns though:

1. The About GIMP, Documentation, Donations, Get Involved, and Tutorial links in the footer and menu bar don't have icons next to them. What's strange is that on the mobile version, the Documentation and Tutorials links both have icons. I personally think these would look nice:
- About GIMP: Not sure but maybe a question mark? - Donations: A simple dollar sign
- Get Involved: A handshake

2. The images for the GIMP icon in the menu bar and footer are much lower quality than the other icons. I'm only looking at the site on my phone so I can't tell for sure but I'm gonna assume that the other icons are vectors whereas the GIMP icon is a bitmap image. Also, the icons for Scribus, Inkscape, and SwatchBooker should either be halved in size or replaced with higher DPI icons for hi-res devices. Perhaps do the same thing with the "Graphic Design Elements" and "Programming Algorithms" backgrounds but loading higher DPI images for those might start causing load issues for people on mobile devices so I don't think that's too important personally.

3. The Recent News title on the News page doesn't have a border and shadow underneath it like the Documentation, Tutorials, and other titles on their respective pages do.

4. The OpenHub activity tracker's design and style doesn't fit with the rest of the site. But that's just mostly color scheme and font.

Other than that, everything else looks great!

A far as the GIMP registry goes, part of me wants to preserve it and just update Drupal to the latest version (assuming it's backwards compatible) and hope it has better spam protection. But on the other hand, I'd like to see it redone entirely in a way that's built for spam protection from the group up. They both have their pros and cons:

Fix the Current Site
Pros:
- Should be relatively simple.
- No loss of plugins and posts.
- Current registry users won't have to learn a new system for posting plugins or responses.

Cons: - AFAIK, there's no real version control on Drupal making it difficult for users to find the version of a plugin their looking for.
- Potential for future problems due to old server configs.

Create an All New Site Pros:
- We can rest assured spam won't be an issue. - We can modify it to our and the users needs from the ground up.

Cons: - Will be a massive undertaking.
- Will have the need for moving over old plugins from the old site.

Those are just my thoughts on it.

Kasim Ahmic

Sent from my iPhone

On Nov 8, 2015, at 10:27 AM, Pat David wrote:

Thank you for taking the time to provide feedback!

On Wed, Nov 4, 2015 at 4:37 PM yahvuu wrote:

On http://static.gimp.org/: There is a typo in Section 'High Quality Photo Manipulation': 'GIMP provides the tools for needed for high quality image' (delete word) -------^

Awesome! Thank you for that - fixed in 41b3f77

Things you might consider:
- Section 'Extensibility & Flexibility': Add Link to http://registry.gimp.org/

I agree with adding this link to the section, but am not sure if we should
hold off until we decide what we want to do with the registry (or just go
ahead and link it, and let folks get the archived version until we switch
things up). The registry is in a poor state, and there's not much we can
do about it from our end (old drupal install that is vulnerable to spam).

I was going to address some ideas in a separate thread on the ML later at
some point and see what everyone thought.

- A new Section "Get Involved":
~ "GIMP is a community project which is driven by volunteers with
a wide range of interests and skills. Have a look how you can become
part of the community" with link to gimp.org/develop/. *)

Great idea! I'll have a look at integrating a section like this. Along
that same idea, we should probably have a look at cleaning up /develop/ and
making it a bit cleaner, simpler, clearer? We've already had a couple of
commits for those pages, yay!

On http://static.gimp.org/develop/ - Section "GIMP Development Links":

"Martin Nordholts’ GIMP Blog -- What happens in GIMP development."
^--- The blog is not active anymore, this item can be deleted.

I see that it's not active, though the information is still archived
there. Should we delete the link completely or mark it as inactive and
leave the link to the old material? I'm not sure on this and am looking
for some guidance/opinions from those who know more than me. :)

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

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

--
John roper
President and CEO of Starlight Graphics Studio Boston, MA USA
http://starlightgraphics.tuxfamily.org

John roper
President and CEO of Starlight Graphics Studio
Boston, MA USA
http://starlightgraphics.tuxfamily.org

On Tue, Nov 10, 2015 at 10:00:23AM +0100, Simon Budig wrote:

Pat David (patdavid@gmail.com) wrote:

Keep the discussion on-list to help everyone keep track of what you may find.

Two minor issues:

Please consider making the body text more bold and more black.

For me the text is on the brink on the unreadable due to the lack of contrast. Given that we all age at a rate of 1s/s I'd appreciate that :)

See http://www.home.unix-ag.org/simon/files/weight-comparison.png for a comparison of the original and changing the weight to 400 (gimp.css:153) and color to #333 (home.css:2).

I agree 100%.

--

Marco Ciampa

I know a joke about UDP, but you might not get it.

+------------------------+ | GNU/Linux User #78271 |
| FSFE fellow #364 |
+------------------------+

On Tue, 2015-11-10 at 14:40 +0000, Pat David wrote:

Of course I'll have a look!  I'm hoping there might be a nice compromise.
I'm rather fond of the lighter weight, but at the same time don't want to
content to be hard to read.

On the current static site, I like the light font weight too. Make the text color darker -- nearly black, if not all the way black -- and it should be fine.

~Andrew

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

Actually, I'm looking at the static site using tota11y -- a web accessibility visualization toolkit by Khan Academy  -- and it says that the paragraphs which have a white background have a contrast ratio of 2.85. (I'm looking at the first paragraph on the docs page.) According to tota11y, it seems the minimum contrast ratios vary depending on the text size. But I think for main body text, I'd prefer a contrast ratio around 6+.

On Tue, 2015-11-10 at 17:26 -0800, Andrew Toskin wrote:

On Tue, 2015-11-10 at 14:40 +0000, Pat David wrote:

Of course I'll have a look!  I'm hoping there might be a nice compromise.
I'm rather fond of the lighter weight, but at the same time don't want to
content to be hard to read.

On the current static site, I like the light font weight too. Make the
text color darker -- nearly black, if not all the way black -- and it should be fine.

~Andrew

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

I mostly recommended WordPress because, as a PHP/MySQL application, it's the most similar to the previous Drupal solution. And Drupal and Joomla are a lot more painful to work with. I do think WordPress could do just about everything we want for the registry if you install the right plugins, but if we decide to write some of our own plugins, WordPress's beautiful simplicity and usability start to go back down.  After working with WordPress for a couple years, my personal preference is definitely more in favor of using static site generators, but I don't know if that'd work so well for the plugin registry. Instead, what we might do is just maintain a list of descriptions and links to the various GIMP plugin repositories on GitHub or wherever they are being developed... This would certainly be the simplest way -- the registry wouldn't even need to be a separate repository or website. However, that would also isolate the users of each plugin from each other, so it would be harder to try getting help from the larger GIMP community.
I'm just spit-balling here.
Otherwise, for a dynamic web server and friendly web UI, using more focused software would probably be a better solution, I just don't know so much about administrating them. Discourse is definitely high- quality, functional, beautiful forum software. They apparently even have converters for other forums
which is nice. I don't know about versioning for user file uploads, though -- I can't find anything that says Discourse supports such a thing. Perhaps, unless someone finds an even better solution, plugin developers could just update the original post where they first announced and released their GIMP plugins? Or, users could still download plugins from the git repo, but developers are encouraged to provide support/discussion on the GIMP Discourse site. ~Andrew
On Tue, 2015-11-10 at 03:23 +0000, Pat David wrote:

I'm actually sort of leaning towards the idea of possibly using a discourse instance as a replacement for the registry. It would serve the dual purpose of incorporating a forum/comment system that we could use on the site as well (if we were so inclined).

Honestly, the existing functionality of the registry was pretty much exactly this. I'll expand on my rationale a little later.

I'm personally not so sure that a Wordpress infrastructure would be the most appropriate (but would be happy to hear thoughts around it). On Mon, Nov 9, 2015 at 10:14 PM John Roper wrote:

I would be willing to set it up. I have setup at least 5 wordpress sites for various uses before.
I also write scripts for it.
On Monday, November 9, 2015, Andrew Toskin wrote:

If we decide to rebuild the registry site from scratch, I think WordPress would be *much* easier to set up than Drupal or Joomla,

and

WordPress has pretty good spam filters via plugins officially

sponsored

by Automattic, the company developing. There are a lot of web CMS applications out there, but WordPress is by far the easiest to

use

among the PHP/MySQL stacks, and still pretty versatile for web development.
Either way, I think the GIMP Plugin Registry provides an

important

service. We shouldn't let it fall to the wayside.  On Sun, 2015-11-08 at 16:44 -0500, Kasim Ahmic wrote:

The site looks great! I only have a few minor cosmetic concerns though:

1. The About GIMP, Documentation, Donations, Get Involved, and Tutorial links in the footer and menu bar don't have icons next

to

them. What's strange is that on the mobile version, the

Documentation

and Tutorials links both have icons. I personally think these

would

look nice:
 - About GIMP: Not sure but maybe a question mark?  - Donations: A simple dollar sign
 - Get Involved: A handshake

2. The images for the GIMP icon in the menu bar and footer are

much

lower quality than the other icons. I'm only looking at the site

on

my phone so I can't tell for sure but I'm gonna assume that the

other

icons are vectors whereas the GIMP icon is a bitmap image. Also,

the

icons for Scribus, Inkscape, and SwatchBooker should either be

halved

in size or replaced with higher DPI icons for hi-res devices.

Perhaps

do the same thing with the "Graphic Design Elements" and

"Programming

Algorithms" backgrounds but loading higher DPI images for those

might

start causing load issues for people on mobile devices so I

don't

think that's too important personally.

3. The Recent News title on the News page doesn't have a border

and

shadow underneath it like the Documentation, Tutorials, and

other

titles on their respective pages do.

4. The OpenHub activity tracker's design and style doesn't fit

with

the rest of the site. But that's just mostly color scheme and

font.

Other than that, everything else looks great!

A far as the GIMP registry goes, part of me wants to preserve it

and

just update Drupal to the latest version (assuming it's

backwards

compatible) and hope it has better spam protection. But on the

other

hand, I'd like to see it redone entirely in a way that's built

for

spam protection from the group up. They both have their pros and cons:

Fix the Current Site
Pros:
 - Should be relatively simple.
 - No loss of plugins and posts.
 - Current registry users won't have to learn a new system for posting plugins or responses.

Cons:  - AFAIK, there's no real version control on Drupal making it difficult for users to find the version of a plugin their

looking

for.
 - Potential for future problems due to old server configs.

Create an All New Site Pros:
 - We can rest assured spam won't be an issue.  - We can modify it to our and the users needs from the ground

up.

Cons:
 - Will be a massive undertaking.
 - Will have the need for moving over old plugins from the old

site.

Those are just my thoughts on it.

Kasim Ahmic

Sent from my iPhone

On Nov 8, 2015, at 10:27 AM, Pat David

wrote:

Thank you for taking the time to provide feedback!

On Wed, Nov 4, 2015 at 4:37 PM yahvuu

wrote:

On http://static.gimp.org/:
  There is a typo in Section 'High Quality Photo

Manipulation':

      'GIMP provides the tools for needed for high quality

image'

                 (delete word)  -------^

Awesome!  Thank you for that - fixed in 41b3f77

  Things you might consider:
    - Section 'Extensibility & Flexibility':       Add Link to http://registry.gimp.org/

I agree with adding this link to the section, but am not sure

if we

should
hold off until we decide what we want to do with the registry

(or

just go
ahead and link it, and let folks get the archived version

until we

switch
things up).  The registry is in a poor state, and there's not

much

we can
do about it from our end (old drupal install that is

vulnerable to

spam).

I was going to address some ideas in a separate thread on the

ML

later at
some point and see what everyone thought.

    - A new Section "Get Involved":       ~ "GIMP is a community project which is driven by volunteers with
a wide range of interests and skills. Have a look how you

can

become
part of the community" with link to gimp.org/develop/.  *)

Great idea!  I'll have a look at integrating a section like this.  Along
that same idea, we should probably have a look at cleaning up /develop/ and
making it a bit cleaner, simpler, clearer?  We've already had

a

couple of
commits for those pages, yay!

On http://static.gimp.org/develop/   - Section "GIMP Development Links":

    "Martin Nordholts’ GIMP Blog -- What happens in GIMP development."
      ^--- The blog is not active anymore, this item can be deleted.

I see that it's not active, though the information is still archived
there.  Should we delete the link completely or mark it as

inactive

and
leave the link to the old material?  I'm not sure on this and

am

looking
for some guidance/opinions from those who know more than me.

:)

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

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

I'm sorry but I can not commit to anything. My availability is all over the place and I usially just have to work on the lists and email. Sorry.

On Tuesday, November 10, 2015, Pat David wrote:

Well, poop. :)
Will you be around on Thursday at some time to meet on IRC with schumaml and anyone else that wants to come?

By the way - anyone that would like to join us, please do on irc.freenode.net #gimp-web

I am tentatively thinking 1900UTC to meet - does that work ok for

everyone?

On Tue, Nov 10, 2015 at 4:07 AM Simon Budig wrote:

Two minor issues:

Please consider making the body text more bold and more black.

For me the text is on the brink on the unreadable due to the lack of contrast. Given that we all age at a rate of 1s/s I'd appreciate that :)

See http://www.home.unix-ag.org/simon/files/weight-comparison.png for a comparison of the original and changing the weight to 400 (gimp.css:153) and color to #333 (home.css:2).

Of course I'll have a look! I'm hoping there might be a nice compromise. I'm rather fond of the lighter weight, but at the same time don't want to content to be hard to read.

I did at least try to follow the W3C web content accessibility guidelines for contrast ratio (that light body text is actually 4.48:1 ratio, the guidelines for text that size is actually to be at least 3! Also -

there's

a W3C accessibility guideline for contrast ratio! :) ).

http://www.w3.org/WAI/WCAG20/quickref/#qr-visual-audio-contrast-contrast

I'll render out some options later and see if we can't make it a bit more legible.

It might be worth looking at more pages than I did. For example the news item date is #aaa on white in a very small light font. If we don't want our visitors to read the text it would be better to remove the text instead :)

Absolutely, I'll check against the entire site when we find one we like. The news items have a (slightly) different color at the moment as well, I believe. I was trying to use color to differentiate secondary information from that area, but may have gone too far. :)

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

John roper
President and CEO of Starlight Graphics Studio
Boston, MA USA
http://starlightgraphics.tuxfamily.org

On Tuesday, November 10, 2015, Pat David wrote:

I was mostly considering the prior use cases for the registry that made it helpful/handy. I came up with these broad thoughts:

1. Allow registered users to post content: a. Post new scripts/plugins with attachments and versioning if possible b. Post comments on other items
2. Allow embeds, attachments, versioning history, and possibly wiki-like editing on the pages based on user permissions. 3. Allow easy moderation/administration of topics/comments/users (important as there are limited people available to police things).

Honestly, the more I think about it, the more it seems like it might be better served by something like discourse (you can see the instance I'm running over at discuss.pixls.us to see what I mean).

First, what is the purpose of having a registry?

As a user, I think of the registry as a way to find plug-ins that solve whatever problem I'm trying to solve right now.

As a plug-in author, I think of it as a place I can put my plug-ins where users might be able to find them easily, and secondarily as a place to get feedback about them.

But the previous registry was set up more like a discussion forum, like it was intended to be a community people that read regularly. If you tried to search for a plug-in, what you got was a bunch of discussions containing your search terms, and *maybe* intermixed with the discussions might be a few entries that were actually plug-ins. I found it so hard to use as a user that I lost motivation to put my own plug-ins there.

I've periodically seen discussions in the past about having a registry that GIMP could actually talk to: you could search for plug-ins by keyword within GIMP itself, and even download and install those plug-ins, something beginning users have trouble with. Of course, that's a whole separate discussion (there are rating and malware issues, as well as details like how you build C plug-ins and check API compatibility) and might be better done by a separate program: but it can never even be possible without a place to register plug-ins in a standard way.

For that, you'd want a registry that has a few fixed fields: - Plug-in name
- Author (and a way to contact the author) - Short description: what does the plug-in do? - Most recent downloadable version, with date and version number - Language it's written in, with a link to a clear page on how to install plug-ins written in this language on various platforms - Long description (feature list, instructions on use) - Image to show what it does (at least one, maybe several)

Offering discussions in addition to those fields is nice. (Please, with email notifications! Something a lot of forum sites, and the previous registry, don't seem to do very well.) But the discussions aren't the point: there are already quite a few GIMP discussion forums and mailing lists. Meanwhile, there is no place to register plug-ins in a clear and findable way -- let alone a registry that could some day offer an API and maybe even be integrated into GIMP itself.

...Akkana

On Tue, 2015-11-10 at 01:28 +0000, Pat David wrote:

If you'd like to take a look at something, perhaps we can start with something like twitter?  See what url query params are available for us to link to, and we can see about adding the necessary bits to make it work.

Or possibly Google+? :)

Sorry for the delay. Turns out support for URL parameters (as opposed to heavy JavaScript widgets) is a little asymmetrical among the different social media platforms, but I'm figuring it out. I've got Google+ done, and I'm looking into the Twitter API. I notice the live site at static.gimp.org doesn't yet have any social media *icons*. Have we decided yet where we'd like to put those links? I would imagine somewhere in the site footer. But there's also a dedicated "Contacting Us" page, so it might also make sense to put it there, although it would also make the social links less prominent. I could just give you the code snippets and let you figure it out, or I could attach git patches directly to Bugzilla this time. While I'm at it, I can take a look at any other social media platforms that we feel like supporting. Platforms where GIMP maintains a profile and posts updates will need links for subscribing/following, while for other platforms we might only have a "share this page" button at the bottom of blog posts and tutorials. So which ones do we want to do? ~Andrew

Okay, I think we've pretty much discussed ideas about the social links enough, so I'm moving to the Bugzilla :) https://bugzilla.gnome.org/show_bug.cgi?id=758261 ~Andrew
On Tue, 2015-11-17 at 20:10 +0000, Pat David wrote:

On Fri, Nov 13, 2015 at 5:52 PM Andrew Toskin wrote:

Sorry for the delay. Turns out support for URL parameters (as opposed to heavy JavaScript widgets) is a little asymmetrical among the different social media platforms, but I'm figuring it out. I've got Google+ done, and I'm looking into the Twitter API.

I notice the live site at static.gimp.org doesn't yet have any social media *icons*. Have we decided yet where we'd like to put those links? I would imagine somewhere in the site footer. But there's also a dedicated "Contacting Us" page, so it might also make sense to put it there, although it would also make the social links less prominent. I could just give you the code snippets and let you figure it out, or I could attach git patches directly to Bugzilla this time.

I was also thinking in the footer.  At least as simple links to our presence on those platforms (google+, twitter).  I can handle those types of links without a problem (simple links).  

While I'm at it, I can take a look at any other social media platforms that we feel like supporting. Platforms where GIMP maintains a profile and posts updates will need links for subscribing/following, while for other platforms we might only have a "share this page" button at the bottom of blog posts and tutorials. So which ones do we want to do?

What I'm thinking right now is two main approaches that will hopefully work together:

1. Links to our presence on other social platforms for people to follow/etc.  I am fine (and would prefer) sending people off-site to our profile on those other networks with static links to minimize invasive tracking from them.

2. Easy sharing of content from the website on social networks.  Blog/news posts should have the requisite "share this" links available for easy sharing.  I'm not sure that it makes sense to put these types of links on all the pages in the site.  News posts would be a good candidate for this, and possibly high-value/traffic pages like "Downloads".

pat