I wasn't sure whether to ask this in gimp-dev or gimp-user. I've been
searching through the archives but I can't really get a clear picture of
the situation. Here's my question:
Has saving the undo history as part of the XCF format been discussed? I
think it would be useful to have a persistent
What are the Windows packagers using for the build? If they're using a
proprietary package system I suggest moving to a more open one such as NSIS
and customizing that. Windows builds can easily be automated using NSIS.
Another advantage of using NSIS is checking the scriptable installer code
int
On Mon, Dec 2, 2013 at 11:09 AM, Sam Gleske wrote:
> What are the Windows packagers using for the build? If they're using a
> proprietary package system I suggest moving to a more open one such as NSIS
> and customizing that. Windows builds can easily be automated using N
Original message below. I see a good feature recommendation here. Sliders
for fuzzy selection in the select Tool Options dialogs. I think it would
be useful.
On Mon, Dec 16, 2013 at 2:34 PM, SirCrow wrote:
> Hello. I've tried using GIMP many times, yet I've accomplished very
> little,
> giv
On Mon, Jan 20, 2014 at 12:51 PM, p...@ppg7.com wrote:
> I have subscribed for access to your mail list for developers although I
> am not
> sure that I am accessing the developers correctly. Please forgive me if I
> have
> done this incorrectly.
>
>
You're correct. What you did was incorrect.
Personally I'd use the Steam version of Gimp if it were available. Sure,
the on-the-fly updates are no problem for a Linux edition of Steam. But on
Mac and Windows there's no such auto-updating functionality (due to the
drawbacks of the OS) and GIMP rightly does not try to fill that gap.
In addi
On Mon, Feb 10, 2014 at 1:57 PM, Sam Gleske wrote:
> Sure, the on-the-fly updates are no problem for a Linux edition of Steam.
>
I meant to say "Linux edition of GIMP."
___
gimp-developer-list mailing list
List address:gim
On Mon, Feb 10, 2014 at 1:57 PM, Sam Gleske wrote:
> ...but on an average daily basis there's more than 5 million users logged
> into Steam using the distribution platform. The largest of it's kind.
>
I should probably back up with a source for statistics. Luckily, Valve
p
Accidentally replied directly... here goes again. This mailing list should
really change the default reply-to on outgoing mailings.
On Mon, Feb 10, 2014 at 2:26 PM, Gez wrote:
> What about the source code? Does the Steam platform provide a way to
> distribute the sources of GIMP?
Not that I'm
On Tue, Feb 11, 2014 at 3:45 AM, Sam Gleske wrote:
> On Mon, Feb 10, 2014 at 2:26 PM, Gez wrote:
>
>> What about the source code? Does the Steam platform provide a way to
>> distribute the sources of GIMP?
>
>
> Not that I'm aware of. If so, then I
On Mon, Feb 3, 2014 at 9:36 AM, Joao S. O. Bueno wrote:
> Therefore, I think posting here is far better for him and for the
> project alike.
>
Perhaps I wrote it off too quickly.
___
gimp-developer-list mailing list
List address:gimp-developer-list
Hi Sven,
I could provide, "Add a (password protected) administrator dashboard to
monitor the status of the relevant GIMP and GNOME infrastructure. For
technical reasons this could also be somewhere else or we join the existing
solutions of the GNOME infrastructure" through the use of Icinga. I'm w
On Fri, Feb 14, 2014 at 11:47 AM, Alexandre Prokoudine <
alexandre.prokoud...@gmail.com> wrote:
> On Fri, Feb 14, 2014 at 8:30 PM, Gez wrote:
>
> > What about this?
> >
> > https://dl.dropboxusercontent.com/u/255376/gimp/GIMP-drop-icon_b.png
>
> Way, way better, IMO.
>
Resending... replying to li
Also, something you might be interested in is front end web testing for bad
links, etc. Recently I've been working on a project to facilitate that
testing.
https://github.com/sag47/frontend_qa
This can easily be used in a Jenkins job to arbitrarily launch and crawl
gimp.org and test all the link
On Sat, Feb 22, 2014 at 4:40 AM, Mukund Sivaraman wrote:
> It would be nice to have docs on how to setup such a Jenkins instance
> (after the other tutorials are written).
>
> * Many bits in GIMP's source code are like a reference for "how to do X"
> which other free software projects can use a
I don't have any Groovy experience but I can say that the Docs on
python.orgare great for learning Python. See their tutorial which
includes best
practices for the language and other tid bits.
http://docs.python.org/2/tutorial/index.html
On Mon, Feb 24, 2014 at 12:05 AM, scl wrote:
> Hi,
>
>
On Mon, Feb 24, 2014 at 2:09 PM, scl wrote:
>
> Forwarded with Sam Gleske's permission:
>
> On 24.2.2014 at 3:21 PM Sam Gleske wrote:
>
>>
>> I'm not familiar with the shorthand "sth". I can start running tests
>> against www.gimp.org <h
On Tue, Feb 25, 2014 at 3:20 AM, Alexandre Prokoudine <
alexandre.prokoud...@gmail.com> wrote:
> On Tue, Feb 25, 2014 at 10:50 AM, Andreas Hübner wrote:
>
> > Meanwhile Chromebooks have a market share of almost 25% in the sale of
> > products in the United States.
>
>
> http://www.zdnet.com/latest
On Thu, Feb 27, 2014 at 12:03 AM, scl wrote:
> how about building the website on Jenkins, too?
>
Testing the website can be part of the build process in the Jenkins job (or
calling another job which does the testing upon a successful build of the
website job).
Also, when do IRC meetings happen
On Thu, Feb 27, 2014 at 11:28 PM, scl wrote:
> We're in #gimp at irc.gimp.org, usually in evening hours (UTC).
>
> GIMP users' discussions are in #gimp-users and GEGL development
> discussions in #gegl.
>
Cool, when I do join I'll be user sag47. I say that because my user will
be different than
failure of your commit via
> IRC and RSS (quicker than before)
>
> For more information see:
> https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin
> http://kohsuke.org/2011/12/01/polling-must-die-triggering-
> jenkins-builds-from-a-git-hook/
>
> Thanks to Sam Gleske fo
On Sat, Mar 1, 2014 at 10:33 PM, Sam Gleske wrote:
> @gimp-dev, @gimp-web
> My crawler has a stable release now. I'd like to request permission to
> crawl www.gimp.org. It will be restricted to that domain and have
> request delays implemented to minimize impact.
>
FYI
On Thu, Mar 6, 2014 at 7:59 AM, Alexandre Prokoudine <
alexandre.prokoud...@gmail.com> wrote:
> TL;DR: there is no consensus on Steam yet.
>
For myself, at least, that's promising. I was willing to drop the subject
entirely with no further discussion based on your feedback response. I
don't fol
On Thu, Mar 6, 2014 at 1:14 PM, Christopher Curtis wrote:
> Speaking strictly as a reader of the mailing list, the GIMP project is
> woefully understaffed. Putting GIMP into the hands of tens of thousands of
> users who are probably not on the primary platform (i.e. Linux) may siphon
> off valuabl
On Fri, Mar 7, 2014 at 3:58 AM, Daniel Sabo wrote:
> When we talk about taking up developer time asking to implement a
> (windows specific) auto-update system, which will also require a
> server side system to be set up and maintained, is a lot more work to
> take on. It is safe to say that won't
Reference - https://github.com/jenkinsci
So recently I've been introduced to the way Jenkins CI does development and
progression of the platform. I decided to write a plugin for Jenkins and
so I hopped over to their IRC channel to discuss with them about it. First
thing they did was make me a me
&tree=name,version,desc.
The Jenkins tree filter also handles structures in a sane manner. Take for
example the following JSON.
{
"id": 1,
"name": "my-plugin",
"version": "0.0.1",
"info": [
{
"author"
To better understand what I mean about tree see the following URLs.
https://ci.jenkins-ci.org/api/json?pretty=true&tree=jobs[name,url]
versus
https://ci.jenkins-ci.org/api/json?pretty=true
SAM
On Wed, Apr 9, 2014 at 2:24 PM, Sam Gleske wrote:
> On Wed, Apr 9, 2014 at 12:06 PM,
As I mentioned in the past the offer is still open for me to QA the GIMP
website frontend for dead links and generate a report. I didn't ever get
approval from any of the core devs so I didn't run any front end tests.
SAM
On Fri, Apr 25, 2014 at 8:57 PM, Jehan Pagès wrote:
> Hey all,
>
> I've
On Sat, Apr 26, 2014 at 11:13 AM, Sam Gleske wrote:
> https://stripe.com/blog/stripe-open-source-retreat
>
> Worth checking out.
>
Posting this to the devel list. Originally posted in gimp-user.
SAM
___
gimp-developer-list mailing list
On Sun, Apr 27, 2014 at 11:28 PM, scl wrote:
> On 28.4.2014 at 3:59 AM Sam Gleske wrote:
>
> As I mentioned in the past the offer is still open for me to QA the GIMP
>> website frontend for dead links and generate a report. I didn't ever get
>> approval from any of
On Mon, Apr 28, 2014 at 8:22 AM, Michael Schumacher wrote:
> Please give it a go and we'll have a look at the results.
It's currently running against the production wgo. I have started
configuring a Jenkins build job and found that using a simple http server
does not appear to be enough for th
On Mon, Apr 28, 2014 at 3:41 PM, Sam Gleske wrote:
>
> On Mon, Apr 28, 2014 at 8:22 AM, Michael Schumacher wrote:
>
>> Please give it a go and we'll have a look at the results.
>
>
> It's currently running against the production wgo. I have started
> conf
On Fri, May 2, 2014 at 5:00 AM, scl wrote:
> Hi,
>
> yesterday I came across http://www.gimp.org/develop/
> and clicked the link 'INSTALL'. It refers to
> https://git.gnome.org/browse/gimp/plain/INSTALL,
> which doesn't exist anymore in this form.
> This raised a question: can the link checker al
I CC all the MAINTAINERS.
For those maintainers who may not be following. I'm in the process of
creating a decent build and QA process for the GIMP website.
I just realized that the install.sh is no good for Jenkins. It's not a
POSIX compatible script which Jenkins requires in order to properly
install -m 755 -d ./htdocs/cgi-common
sed -e 's|${PYTHON}|python2.7|g' -e 's|${LIBDIR}|./htdocs/cgi-common|g'
wgo.py> ./htdocs/cgi-common/wgo.py
sed -e 's|${PYTHON}|python2.7|g' -e 's|${LIBDIR}|./htdocs/cgi-common|g'
apache_ssi.py > ./htdocs/cgi-common/apache_ssi.py
sed -e 's|${PYTHON}|pyth
This was resolved by setting the HTDOCS build target to outside of the
gimp-web repository.
On Fri, May 2, 2014 at 11:33 AM, Sam Gleske wrote:
> install -m 755 -d ./htdocs/cgi-common
> sed -e 's|${PYTHON}|python2.7|g' -e 's|${LIBDIR}|./htdocs/cgi-common|g'
> wgo.py
On Fri, May 2, 2014 at 11:19 AM, Sam Gleske wrote:
> I CC all the MAINTAINERS.
>
> For those maintainers who may not be following. I'm in the process of
> creating a decent build and QA process for the GIMP website.
>
> I just realized that the install.sh is no good f
I'd be willing to take up the flag of managing Jenkins. I've got about 2-3
years of Jenkins experience. Sad to see you go scl.
On Thu, Aug 14, 2014 at 8:43 AM, Tobias Jakobs
wrote:
> 2014-08-13 20:44 GMT+02:00 scl :
>
> > Hi,
> >
> > we have a continuous integration system (Jenkins based) tha
+1
On Thu, Aug 14, 2014 at 8:32 AM, Tobias Jakobs
wrote:
> Hello,
>
> the Siggraph has this year (again) some nice papers. Especially the paper
> "Image completion using planar structure guidance" [1] looks like a nice
> challenge for the GSoC next year.
> What do you thing, should we add it to
On Sun, Aug 24, 2014 at 4:13 PM, Stefan Kullack
wrote:
>
> Haha, and I hope I could do you a small favor by replying after all :)
>
> Best regards,
>
> Stefan
>
I went ahead and took the survey since you replied. Strangely there were
some parts in English and some parts in German. Though, enou
Awesome work.
On Mon, Feb 16, 2015 at 1:36 PM, Alexander Rabtchevich <
alexander.v.rabtchev...@gmx.net> wrote:
> Thank you, guys. Works for me.
>
> With respect,
> Alexander Rabtchevich
>
>
> Thorsten Stettin wrote:
>
>> Am 16.02.2015 um 19:53 schrieb Michael Natterer:
>>
>>> Fixed in git master:
On Fri, May 29, 2015 at 2:35 PM, Michael Schumacher wrote:
> See
> https://mail.gnome.org/archives/gimp-developer-list/2015-May/msg00034.html
> (the mail thread gets constructive beyond the first post).
>
> In this thread, there is work on proposal for the downloads pages that
> makes both the to
On Mon, Jul 6, 2015 at 2:13 PM, Melissa Golobish
wrote:
> Not sure if it's possible or maybe this was even thought about, but could
> someone upload Gimp to Steam?
>
> The team behind Blender has uploaded to Steam, and I think doing this would
> allow for easier updates and community interaction,
Hello devs and users,
I want to lower the barrier of entry of GIMP development for people who
want to contribute to GIMP.
I just made a quick set-up development environment for GIMP. This way new
developers can get their first build of GIMP in minutes (depending on
internet connection) rather tha
Hello Paul,
Thanks for your feedback. I'm not sure if you meant to reply off-list but
I'll include the mailing lists in my reply. Hope you don't mind.
On Sun, Sep 27, 2015 at 3:39 PM, Paul Alkhimov wrote:
> *TL;DR*: it did not work out and I have no idea where to find the gimp
> sources in th
On Sun, Sep 27, 2015 at 6:08 PM, Sam Gleske wrote:
> I'll follow up with when I believe the bootstrapping process is fixed.
>
Hi Paul,
I've fixed the issues you encountered when you first tried to bootstrap.
Here's the detailed changes.
https://github.com/samrocketma
On Mon, Sep 28, 2015 at 10:21 AM, Michael Schumacher
wrote:
>
>
> On 09/27/2015 08:35 PM, Sam Gleske wrote:
>
> >1. Install vagrant https://www.vagrantup.com/
> >2. Clone: git clone https://github.com/samrocketman/vagrant-gimp
>
> Um... why is KDE in there?
On Mon, Sep 28, 2015 at 11:10 AM, Michael Schumacher
wrote:
>
>
> On 09/28/2015 07:30 PM, Sam Gleske wrote:
> > On Mon, Sep 28, 2015 at 10:21 AM, Michael Schumacher
> > wrote:
> >> Um... why is KDE in there?
> >>
> >
> > I realize KDE is n
On Mon, Sep 28, 2015 at 11:17 AM, Pat David wrote:
> Maybe GNOME?. :)
>
It could be provided as an option. KDE is what I use typically during
development which is why I set it. However, setting it to something more
light weight like XFCE by default makes sense in terms of being able to get
rig
On Mon, Sep 28, 2015 at 11:22 AM, Ofnuts wrote:
>
> Plenty of UIs and desktop managers, and plenty of development tastes...
> I'm myself on KDE, but if your VM was running Gnome or Unity, it would be
> useless to me. I do use a VM for some development that can only be done on
> Windows, but using
On Mon, Sep 28, 2015 at 11:55 AM, Michael Schumacher
wrote:
> GIMP developers use Debian Testing, with the assumption that is anything
> is present there, then a GIMP build can require it.
>
> A build based on Debian Jessie, currently aka Debian Stable, will divert
> from that over time, and migh
It's likely that you're missing LD_LIBRARY_PATH when you're loading GIMP.
While you're starting GIMP that was compiled from Git it is loading GEGL
libraries from other sources. You should do the following (assuming GIMP,
GEGL, and BABL were installed under /usr/local prefix by default):
LD_LIBRAR
Regarding the download page. I think it would be nice if the download
links were positioned in a similar area. For instance, when switching
between Mac and Windows downloads the links are in a significantly
different part of the screen.
http://s3.postimg.org/w9ouu1dyp/gimp_downloads.gif
That tr
On Sat, Nov 14, 2015 at 10:59 AM, Jehan Pagès
wrote:
> This is something which is coming with xdg-app. See for instance this
> blog post (which actually proposes already some nightly for GIMP as a
> demo):
>
> https://blogs.gnome.org/alexl/2015/10/06/nightly-devel-builds-using-xdg-app/
>
> When s
I went ahead and created a pull request (PR) addressing the portable
vagrant environment. I created the PR so anybody can comment or give
feedback.
https://github.com/samrocketman/vagrant-gimp/pull/11
For one reason or another, the latest GEGL master is failing to build which
I noted a workaroun
On Fri, Feb 10, 2017 at 6:03 AM, Jehan Pagès
wrote:
> Hi,
>
> On Fri, Feb 10, 2017 at 10:20 AM, gregory grey wrote:
> > I know about build.gimp.org.
> >
> > I just wanted to raise this question to the attention of the team - of
> > whether there is a need to support own CI if security is not an
this
thread. I just wanted to publicly announce my apology since I started this
mess publicly.
Thanks,
SAM
On Thu, Oct 5, 2017 at 7:08 AM, Jehan Pagès
wrote:
> Hello Sam,
>
> On Thu, Oct 5, 2017 at 9:15 AM, Sam Gleske wrote:
> >
> >
> > On Fri, Feb 10, 2017 at
Hey Michael,
I do not get bugzilla notifications on this but I am actually aware of the
issue and have been working on it for a few days now since I know
gimp-master builds were failing.
On Thu, Oct 5, 2017 at 5:03 PM, Michael Schumacher wrote:
> On 10/05/2017 04:08 PM, Jehan Pagès wrote:
>
> >
6:19 PM Ofnuts wrote:
>
> > On 10/06/17 19:29, Sam Gleske wrote:
> > > If anybody is interested in joining me as an admin for maintaining the
> > GIMP
> > > CI server I encourage anybody to reach out to me regardless of your
> skill
> > > level.
Hello gimp devs et al,
I would like to introduce Pat David and ofnuts as Linux admins for
build.gimp.org.
What kind of access do they currently have?
- root (sudo) access to the underlying system of build.gimp.org
- Jenkins admins of build.gimp.org
- Access to contribute to the build.gimp.org infr
Hello GIMP Devs,
I would like collaborate access to the GIMP repository [1]. I'm not able
to assign issues to myself and I can't close or re-open issues that are not
created by me. I need to be able to update Jenkins related issues [2].
How do I go about getting this access?
Thanks,
SAM
[1]: h
Hello all,
Announcing a new release of https://build.gimp.org/
Here's an announcement tweet from twitter
https://twitter.com/sag47/status/1000251383876997120
Key features:
- Branches now show up clearly in the UI. For example:
https://build.gimp.org/job/gimp/
- New Jenkins UI (Blue Oce
63 matches
Mail list logo
