[Gimp-developer] Query: Saving history already discussed?
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 history or at least have options for keeping. I realize a file can get very large in this scenario (hundreds of megabytes and gigabytes if the history is long enough even for small resolution images). Please let me know, SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Setting Up a Release Procedure
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 into SCM. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Setting Up a Release Procedure
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 NSIS. > Another advantage of using NSIS is checking the scriptable installer code > into SCM. > Does this mean that nobody on this list knows what the release process is on Windows for building installers? ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] [Gimp-user] Why so COMPLICATED?
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, > given all of GIMP's functionality. For example: > > If I want to select part of an image and copy it to another area or to a > new > image/layer, and also FEATHER the edges, here's how I'd do it in an old > graphics > app I often used years ago: > > 1. Select the area. > 2. Hold Ctrl while moving selection with Move tool. > 3. Use the slider to soften the edges to my liking. > 4. Press Enter to anchor selection. Done. > > And there were sliders also for opacity and other things. So very SIMPLE > because the prog. was designed very intuitively. How would I accomplish > the > same in GIMP? Well, most of the time, I WOULD ACCOMPLISH NOTHING! At > best, I'd > enter values into the box, not like the result, enter new values, repeat. > And > that's on a good day. > > PLEASE, I beg you, somebody write a SCRIPT/PLUGIN that allows the use of > sliders > exactly as described above! I desperately want to be a HAPPY GIMP user, > but I'm > growing ever more hopeless. I don't want to turn on my older PC just to > use a > graphics app that actually lets me get things done. Thank you. > > Joe > > -- > SirCrow (via www.gimpusers.com/forums) > ___ > gimp-user-list mailing list > List address:gimp-user-l...@gnome.org > List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list > ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Gimp Programmer Requirement
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. This is a developer mailing list for developers to coordinate the discussion of further developing GIMP. Your efforts are best directed to a job posting website where you can better outline the requirements of workers. If you're merely looking for contract work there are plenty of freelance programmer websites in which you could post. > This message contains confidential information and is intended only for the > individual named > I realize you probably send out the stamp with every email however the developer mailing list (and all associated GIMP mailing lists) are publicly archived conversations. Confidential information should never be broadcast through email in general since it is accepted as being wholly insecure. In any case, good luck finding someone to assist you with your project through other avenues than this mailing list. SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Gimp on Steam
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 addition to the auto-updates on Windows, a neat statistic would be how much time I spend in the program. They track other usage statistics but to me that would be the most interesting. Also, Steam allows DRM free packages (i.e. you install via steam but you can take the software out of steam and run it without steam even if steam is not installed or running). So I think no modification would be required from a developers perspective. It would just require the headache of a packager. I'm not sure the Gimp userbase as it stands would much benefit (unless they play PC games and use Steam) 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 think it would bring steam to a wider audience with little to no effort in the long run just by simply existing on Steam. I think a good approach might be to "wait and see" with what Krita does and ask Krita members for feedback on their experience with Steam. If it's positive I see no reason not to do it. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Gimp on Steam
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:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Gimp on Steam
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 provides Steam stats. http://store.steampowered.com/stats/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Gimp on Steam
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 aware of. If so, then I've not seen any software (gaming or otherwise) take advantage of it. Does a link to the sources in the > description (pointing to gimp.org downloads section) suffice to comply > the GPL requirements? > I would say it does so long as binaries were built from said source code. Since it is being distributed, any modifications made for said distribution would need to be released (if there happened to be any). Also, for those interested here's a link to Krita attempting Greenlight on Steam. http://krita.org/item/213-krita-on-steam http://steamcommunity.com/sharedfiles/filedetails/?id=225403385 Also, I think GIMP project actually selling GIMP on Steam would be beneficial. It seems Krita will be doing that and it will be interesting to see how it turns out. I think it has the potential to turn into a nice avenue of funding for the project (perhaps to also provide revenue large enough for full time development). Alas, I get ahead of myself and let's just see what happens. SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Gimp on Steam
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've not seen any software (gaming or > otherwise) take advantage of it. > I also forgot to mention that COPYING.txt and any license related documentation would need to be distributed with the binaries. It is, before all, GPL. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Gimp Programmer Requirement
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@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Changes in developer websites
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 well versed in using it to monitor large infrastructure. Starting out I can temporarily host it or, if given access to a root system install and configure it. For more information, http://icinga.org/ I'm also willing to work with other infrastructure solutions if Icinga is not desired. Please let me know if you and/or team are interested, SAM On Tue, Feb 4, 2014 at 5:02 PM, scl wrote: > Hi, > > the last weeks I've spent with changes to our developer websites. > > I've integrated most of the contents from developer.gimp.org > into our [developer wiki]. > The main reason is to have all developer related information > in one single place to ease finding the right information > and let new contributors get started quicklier. > > In the wiki you find much contributor related information, > such as > - the roadmap with our plans for the near future, > - build tutorials, > - a developer FAQ, > - the GEGL and GIO porting matrices, > - a brand new developer glossary > and more... It was collected and written down by many > contributors over the time. > > The glossary I mentioned last shall collect all terms > we developers need to know about functional requirements, > computer graphics, color science, babl and GEGL. > I've come a long way with it, but surely there > will be the one or another point missing. > So, if you find something missing or in need of > correction, feel free to tell us. Elle Stone and > and me are looking forward for your input! > I'd like to thank all who helped me collecting and writing > it down, spread the word and gave feedback. > > Thirdly from now on you can also report bugs in > the wiki (about wrong content etc.) In Bugzilla > choose product:=gimp-web and component:=wiki.gimp.org. > > Last but not least I have some more ideas on how > to make the wiki a useful central point of information > for all contributors. I've collected them here: > http://wiki.gimp.org/index.php/Mindstorm:Rethinking_the_wiki > > We can discuss them from now on and realize the > good parts after the LGM. > Thank you in advance for your feedback and ideas. > > Kind regards, > > Sven > > [developer wiki]: > http://wiki.gimp.org/index.php/Main_Page > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: https://mail.gnome.org/mailman/listinfo/gimp- > developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list > ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Remove "you can drop dockable dialogs here" label?
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 list. Agreed, I think it would be useful to take it a step further. Hide the drop icon (as it is currently mocked) completely until user mouses over the area. Regular users who don't populate that area don't necessarily need to see a "drop" area but new users can still discover it if they accidentally mouse over it. With the assumption that they accidentally removed the docs of course. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Jenkins tutorial
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 links in it checking for dead links, etc. Currently it's a work in progress but it's a place that one can easily start for frontend testing the Gimp website. On Sat, Feb 22, 2014 at 4:40 AM, Mukund Sivaraman wrote: > Hi Sven > > On Sat, Feb 22, 2014 at 06:03:35AM +0100, scl wrote: > > Hi, > > > > now that we have our continuous integration server > > Jenkins for babl, GEGL and GIMP at an easy memorable address > > (https://build.gimp.org) I'm going to write a tutorial > > for developers and testers on how to use it. > > Are there any particular questions you want to have > > answered there? > > 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 as examples. In the same > way, "How to setup a Jenkins instance for GIMP" would help others > setup one for their project too. > > * Such docs would enable others to maintain/reconfigure the Jenkins > instance when you are busy and unable to do so. > > Mukund > > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list > > ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Jenkins tutorial
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 as examples. In the same > way, "How to setup a Jenkins instance for GIMP" would help others > setup one for their project too. > > * Such docs would enable others to maintain/reconfigure the Jenkins > instance when you are busy and unable to do so. That being said... would it be useful to have a vagrant instance of the development environment including Jenkins for Job testing? With a vagrant file it can be as easy as a single program executing to pull down virtual box, the image, all of the requirements for gimp building and testing. This is something which could also be tweaked. Also, Jenkins really isn't hard. It's pretty intuitive IMO (java -jar jenkins.jar and you have a local web server) but a turn key dev environment would certainly lower the barrier to entry. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Jenkins infrastructure (Was: Jenkins tutorial)
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, > > I'm currently considering using Python, > Perl or a JVM based scripting language (Groovy etc.) > for the buildjobs. The goal are platform independence, > performance and easy maintainability. > > Without wanting to start a silly flamewar about which > tool is the greatest: > - Where are the experienced benefits and downsides of these > languages for the desired task? > - Which readings would you recommend for Python and the > JVM based language? > > Thank you in advance, > > > Sven > ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Jenkins infrastructure (Was: Jenkins tutorial)
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 <http://www.gimp.org> and begin to start ironing >> >> out bugs which would need to be fixed in my program. I've run into bugs >> here and there running my crawler against large websites. Right now >> I've crawled and run against Drexel University IRT website using the >> crawler which is ~70k links. I'll do it for www.gimp.org >> <http://www.gimp.org> too and then contribute a Job when I have it ready >> >> (and for the other GIMP websites as well). >> > > I don't know whether this could cause technical problems for www.gimp.org. > The reason why I wrote 'something stable for production use' is that I want > to avoid just them ;-) > Thus it would be good to hear our website administrators opinion to that. > > Both the crawler and the tests following it support a --request-delay. Requests can be arbitrarily delayed by 0.3 seconds (smaller or larger if chosen) so as to mitigate impact of the website. I won't run any tests against the GIMP website until I get permission to do so. Also, currently my testing suite support saving crawl data in a JSON format. The advantage of this would be separating the crawl from the actual testing (if that's desired later on). Currently I mostly use it to debug my test suite because crawling can take a bit of time so saving that data allows me to avoid that step. On Mon, Feb 24, 2014 at 2:09 PM, scl wrote: > > Also, I'd like to note that >> if you're not using git hooks now would be a good time to use them. >> Rather than using Jenkins to constantly poll the SCM simply implement a >> hook to launch a Jenkins job when a certain branch is committed to. >> > > Currently we're polling SCM every few minutes. Adding a git hook to the > repository would surely need involvement of the GNOME administrators. > Is there a good reason to switch over from polling to hooking? > The advantage of hooks vs polling is that hooks are on demand. i.e. a job or process is only launched if there is an actual commit. For the sake of covering all topics I'll briefly describe polling. Polling simply keeps checking the state of the repository periodically (e.g. every 5 minutes). If the state hasn't changed (no commits) then it does nothing. If the state has changed (i.e. commits have been made) then it executes based on what was defined for the Job. Hooks simply take less processing time. On a smaller scale they save energy because they're not constantly polling. It's also lowering the request load of the server serving the repository being polled. It's not a big deal if a server is serving a single repository or a few repositories. However, when you have e.g. 1 repositories on a server the polling request load of each repository every few minutes starts to eat up the server's ability to serve. For smaller servers it's not the end of the world to have polling because it is easier to implement. I realize the GIMP project may be only a small part of that ecosystem being served but it is something worth considering. SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Gimp on Chrome OS
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-idc-figures-show-chromebooks-continue-to-struggle-723000/ Not that I really see this feasible in any way but thought I'd contribute a more reliable source. Amazon top laptop sales there are four Chromebooks in the top 10. I'd say that zdnet article is fud after light research. http://www.amazon.com/Best-Sellers-Computers-Accessories-Laptop/zgbs/pc/565108 ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Jenkins infrastructure (Was: Jenkins tutorial)
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 and can anyone participate? What server and channel? http://www.gimp.org/irc SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Jenkins infrastructure (Was: Jenkins tutorial)
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 my email on the list. SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Jenkins infrastructure (Was: Jenkins tutorial)
On Sat, Mar 1, 2014 at 12:49 PM, scl wrote:On Mon, Feb 24, 2014 at 2:09 PM, scl wrote: > together with Andrea Veri I've set up the hook based build trigger. > Currently it is active for testing purposes on the > branches babl/hooktest and GEGL/master. If we encounter > no trouble the other branches will follow in one week or two. > > That's how it works: > 1. You push a commit to babl/hooktest or GEGL/master in our public > repository. > 2. Git's Post-Receive hook notifies Jenkins about changes in the > affected repository and branch. > 3. Jenkins' Git Plugin will scan all the jobs which check out the > specified URL and if they are configured with polling, they'll poll. > 4. The polling will usually find something that's worth a build, > so a build will be triggered. > 5. You get an answer about success or 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 for the advice and Andrea Veri for setting up > the Git side. > +1 Awesome. @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. SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Jenkins infrastructure (Was: Jenkins tutorial)
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 most of the requests will only be HTTP method HEAD - http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.4 It only requests headers and not the response body so it would actually be less of an impact than most crawlers when doing the actual link testing. For the crawling itself the response body is received so that it can find other links. SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Gimp on Steam
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 follow IRC as much as the mailing list so I could only take your message at face value. To the best of my understanding there is no long-term strategy for > involvement with Steam whatsoever > Agreed. At this point it was just a proposal I think. A quote from your earlier message. the core team's opinion currently is that supporting a proprietary software > delivery platform doesn't feel right. > I'm curious to hear Simon's opinions since he openly admitted he was one of the "against" parties. Generally, I understand how any free developer would feel about a proprietary distribution platform. However, I also see Steam filling a need (in my mind) for automatically updating the software on Windows and Mac clients. From my perspective it's just another repository and so long as it doesn't infringe on the project rights or the GPL I see no reason why the full stack of delivery must be completely open source. I think, that is impossible. There's always proprietary software in the full stack of delivery (even if it's low level below the Kernel). So for myself it's not as much of an issue that Steam be required to open source their platform for software delivery. I simply see it as another option. Re: Alexandre pros/cons What sort of pros and cons list would be desired. I realize that's a very open ended question but a start somewhere for building such a list would be useful. So far I can think of the following: Pros: - Not a required form of software delivery, only optional. Users can still obtain their GIMP software from the normal channels. - Automatic software updates when new releases are released (this one is extremely minor considering the rate at which GIMP stable is released). Automatic updates can be turned off. - Available for Mac, Windows, and Linux (however I think it should only be maintained for Windows and maybe Mac?). Linux already has centralized software delivery through package managers which I think would be preferred. - GPL friendly. Applications can be delivered without the requirement of remaining within the Steam platform (i.e. it can be moved out of steam and still "work") or even require Steam to be running for launch. This would need to be implemented as a DRM free application for the "it can be moved out of steam and still 'work'" ability. GPL and assorted licenses as well as links to the source code should be provided with the binaries. The Steam TOS does not infringe on the GPL *from my reading* unlike other companies which will not be named. Being DRM free unlimited copies of the binaries are allowed. - Exposure to 5 million+ active users on a daily basis with little to no marketing effort. source - http://store.steampowered.com/stats/ - *Optional* Steam Cloud for saving GIMP profile information, plugins, and settings to the cloud. When a user re-installs GIMP or installs it using the same method on another computer their settings can be transferred automatically and regularly synced on multiple machines. - *I imagine* news updates in Steam can be linked to the GIMP news feed. Cons: - Steam tracks usage statistics. One metric I can tell is that they track how long you use an application (I enjoy this statistic personally). The Steam interface reports back your usage. There are options to disable this. I have listed this as a con because some of our privacy oriented members may not like this so this should be explicitly mentioned. Beyond that I have no idea what else they track (e.g. system calls or who knows). - Steam is proprietary software. There's no way to verify the aforementioned cons. - Binary only distribution of GIMP however links can be provided to the project website and to the source code. Any modified source code for accommodating the Steam platform (unlikely there will be any modifications) will require source to be released as per the GPL. It is also worth mentioning that I already run GIMP with Steam. Steam supports non-steam delivered applications to be launched from their interface however you don't get tracking or usage statistics. I also can't install GIMP through Steam currently. Hopefully, others will add on to that pros/cons list so that core devs can make an informed decision. I include Alexandre as a core member of the project personally due to his contributions on the mailing list and elsewhere. SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: htt
Re: [Gimp-developer] Gimp on Steam
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 valuable developer resources. > In what way? If so, would distribution though Stream attract sufficient volunteers to > offset this cost? > There's no way to answer that question. Is it a loaded question? Assuming you're asking "what kind of community is Steam?" The answer is it is mostly and end-user community with a surrounding game modding community (many of whom use GIMP for textures in their mods). In what way does that make a difference in how GIMP is developed? I don't think it makes a difference. We *might* see more users participating on the mailing list which is a good thing IMO. GIMP has always been users supporting users with occasional input from devs. Adding an additional distribution avenue would not change that. What would be the consequences if a Steam user downloaded GIMP only to find > out that it's still mostly an 8-bit graphics engine? E.g. negative press. > And again, would this motive people to chip in if so? > Re: negative press due to 8-bit graphics? This is a well known issue. Most photography blogs who do a comparison including GIMP cite that as a con. I don't see how adding more users (or not adding them) would change that. When a new release is issued it will come with a news update like it would on the GIMP website. Again, your last question is so abstract it is impossible to answer. I don't really see these as valid concerns. If you have questions that can actually be answered without here-say then I'll attempt to address them. SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Gimp on Steam
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 happen without a new volunteer. > Agreed I rather gimp-core and gegl be the focus of the current core devs. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] Adopt a development model similar to Jenkins?
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 member of the org. Basically they have two organizational teams: Owners (consists of core devs) and Everyone. By making me a member of the Everyone group I got commit access to all 1000+ repositories associated with Jenkins plugins. I can freely contribute to any one of them. However, I don't have commit access to the core Jenkins repository which is the main application of the whole platform. I think this model is really cool. Because basically when you first commit a pull request the jenkinsadmin bot will tell you how the pull requests work. Here is a pull request as an example [1]. The Jenkins admin posted a comment stating that the pull requester should read the link on pull requests [2]. I think this is cool. It's basically a policy that if any plugin goes unnoticed pipe up and become a contributor with commit access to the organizations. Right now, GIMP has a place for users to dwonload plugins... but there is no place where the source code of all of the plugins live and be maintained. I went looking for the GIMP repository on github (it's nice that there is one!) however it seems sadly buried in the GNOME project repositories. I propose GIMP developer team take the initiative to create an organizational account at github and form teams similar to Jenkins. 1. Owners whom are the only ones with commit access to the GIMP core but can still accept pull requests from outsiders. And 2. an Everyone group in which anybody who asks gets commit access to all of the plugins in the organization area. I think this would spice up and breath development life into the GIMP project. GIMP is much more than just gnome and I think the barrier to entry to developing on GIMP should be so low you can trip over it. Jenkins does that well and I feel like by immediately being made a committer to all of the plugins repositories it makes me want to jump up and start contributing everywhere in Jenkins. There's a few reasons for that... 1) I feel like I'm visiably part of the development process and have been acknowledged. 2) I have a shiny cool Jenkins organization badge on my github user [3]. 3) I think it's great that my friends and coworkers can blatantly see that I have at some point or will continue to contribute to the Jenkins project because the organizational badge is displayed on my profile. GitHub makes coding and contributions fun. I would love to have a GIMP organizational badge in my profile. I'm learning C++ in hopes to contributing to GIMP [4] with more than just recommendations or the mailing list. Developers and contributors, tell me your thoughts. I hope you get as fired up about this as I feel. SAM [1]: https://github.com/jenkinsci/findbugs-plugin/pull/5 [2]: https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories [3]: https://github.com/sag47 [4]: https://github.com/sag47/cplusplus ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Fwd: Gimp Registry Future
On Wed, Apr 9, 2014 at 12:06 PM, Michael Schumacher wrote:
> On 09.04.2014 18:03, Seth Burgess wrote:
> > Are we trying to reinvent a package manager here? A lot of the issues I
> > could see coming up have already been addressed by apt/yum/etc - would
> > adapting one of these be a better approach than reinventing the wheel?
>
> If there is one that can be shipped with GIMP, doesn't interfere with
> the one of the system, and works on all platforms?
>
For now, ignoring security concerns and focusing on the server client
architecture I think this would best be served using JSON. The client
"plugin manager" plugin can be written in Python. The server should talk
JSON because python has better JSON support than XML (or is at least easier
to work with in my opinion although python does have good XML support). By
"better" I meant ease to develop with.
For the server side API there should be filters on accessing the API.
For example I interact with the Jenkins API regularly and it has JSON
filters through a [GET argument tree][1]. The API should be able to filter
based on platform and language as well as other information. The
serverside API should also allow GET arguments for filtering what results
are returned.
Examples of possible filters (of which I can think of off the top of my
head):
* id: a unique ID to identify a plugin (an incrementing int should suffice)
* platform architecture: 32-bit/64-bit/any
* platform: Windows/Mac/Linux/any
* Language (or type of plugin): scheme/python/binary
* tree: similar to tree in Jenkins where elements can be limited on exactly
what is returned. A good example would be using the tree to filter just
the name, version, and description of the plugin only.
The API should use pagination and likely have GET options for per_page and
page (e.g. ?per_page=20&page=3). Maybe there should be a limit for
per_page which limits how much is allowed to be returned at once as a
maximum. This way the size of the request can be limited for the server
and plugins. The plugin manager can iterate across pages. Alternatively
for the initial plugin listing there can be a per_page=all and the tree can
be used to filter out all information except for name, version, and
description (or just the name and version). That could look something like
this... ?per_page=all&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": "Sam Gleske",
"displayName": "my plugin",
"desc": "This is my plugin"
}
],
"source_url": "http://url-to-source/my-plugin_0.0.1.tar.gz";
}
And let's say we send a GET request to the plugin server with the following
arguments: ?per_page=all&tree=name,version,info[displayName,desc] .
per_page=all would theoretically return all plugins in the API with
information filtered by tree. As a result of the GET request the server
would respond with...
{
"name": "my-plugin",
"version": "0.0.1",
"info": [
{
"displayName": "my plugin",
"desc": "This is my plugin"
}
]
}
This is essentially how the tree filter in Jenkins works and I think it
would benefit the plugin registry on limiting the size of the payload
returned based on the request. By doing that the plugin manager can
initially request basic information, and if the user wants to see
additional info about the plugin then the plugin manager can make an
additional request. The plugin can then create the following request.
?id=1 and the server responds with the full payload of everything
associated with the plugin ID (or the payload can be filtered with tree).
SAM
[1]:
http://developer-blog.cloudbees.com/2013/05/taming-jenkins-json-api-with-depth-and.html
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Fwd: Gimp Registry Future
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, Michael Schumacher wrote:
>
>> On 09.04.2014 18:03, Seth Burgess wrote:
>> > Are we trying to reinvent a package manager here? A lot of the issues I
>> > could see coming up have already been addressed by apt/yum/etc - would
>> > adapting one of these be a better approach than reinventing the wheel?
>>
>> If there is one that can be shipped with GIMP, doesn't interfere with
>> the one of the system, and works on all platforms?
>>
>
> For now, ignoring security concerns and focusing on the server client
> architecture I think this would best be served using JSON. The client
> "plugin manager" plugin can be written in Python. The server should talk
> JSON because python has better JSON support than XML (or is at least easier
> to work with in my opinion although python does have good XML support). By
> "better" I meant ease to develop with.
>
> For the server side API there should be filters on accessing the API.
>
> For example I interact with the Jenkins API regularly and it has JSON
> filters through a [GET argument tree][1]. The API should be able to filter
> based on platform and language as well as other information. The
> serverside API should also allow GET arguments for filtering what results
> are returned.
>
> Examples of possible filters (of which I can think of off the top of my
> head):
>
> * id: a unique ID to identify a plugin (an incrementing int should suffice)
> * platform architecture: 32-bit/64-bit/any
> * platform: Windows/Mac/Linux/any
> * Language (or type of plugin): scheme/python/binary
> * tree: similar to tree in Jenkins where elements can be limited on
> exactly what is returned. A good example would be using the tree to filter
> just the name, version, and description of the plugin only.
>
> The API should use pagination and likely have GET options for per_page and
> page (e.g. ?per_page=20&page=3). Maybe there should be a limit for
> per_page which limits how much is allowed to be returned at once as a
> maximum. This way the size of the request can be limited for the server
> and plugins. The plugin manager can iterate across pages. Alternatively
> for the initial plugin listing there can be a per_page=all and the tree can
> be used to filter out all information except for name, version, and
> description (or just the name and version). That could look something like
> this... ?per_page=all&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": "Sam Gleske",
> "displayName": "my plugin",
> "desc": "This is my plugin"
> }
> ],
> "source_url": "http://url-to-source/my-plugin_0.0.1.tar.gz";
> }
>
> And let's say we send a GET request to the plugin server with the
> following arguments: ?per_page=all&tree=name,version,info[displayName,desc]
> . per_page=all would theoretically return all plugins in the API with
> information filtered by tree. As a result of the GET request the server
> would respond with...
>
> {
> "name": "my-plugin",
> "version": "0.0.1",
> "info": [
> {
> "displayName": "my plugin",
> "desc": "This is my plugin"
> }
> ]
> }
>
> This is essentially how the tree filter in Jenkins works and I think it
> would benefit the plugin registry on limiting the size of the payload
> returned based on the request. By doing that the plugin manager can
> initially request basic information, and if the user wants to see
> additional info about the plugin then the plugin manager can make an
> additional request. The plugin can then create the following request.
> ?id=1 and the server responds with the full payload of everything
> associated with the plugin ID (or the payload can be filtered with tree).
>
> SAM
>
> [1]:
> http://developer-blog.cloudbees.com/2013/05/taming-jenkins-json-api-with-depth-and.html
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Updating the website for all the broken download links?
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 checked the testing website with my commit to fix the download > links to the new URLs. All looked ok, so I cherry-picked to master. > Would be great to have this rolled out to production, because right > now our website just gives a bunch of dead links for getting GIMP. > That's not good and could drive users away to go pick GIMP up from > some possibly bad source. > > Also are all our mirror admins aware we changed the source of our main > download? Because if they have scripts to sync with our FTP, then they > will never relay properly our new releases. > Thanks! > > Jehan > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list > ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Open source retreat for GIMP work?
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 List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Updating the website for all the broken download links?
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 the core devs so I didn't run any front end tests. >> >> SAM >> > > Hi Sam, > > yes, we lately had this topic and somehow it went out of sight. > I'm not the webmaster, but I think it's useful. > If we should/can integrate something into our Jenkins job set, > then let me know. > > Greetings, > > Sven > As Jehan suggested I'll clone the website. I wasn't aware of the website git repo. As far as the bot goes the source for the crawler is out there. In general, the requirements for a Jenkins node would be the following... 1. Git for cloning and Python 2 for the robot. 2. A simple HTTP server such as nginx. Or if the website is simply static pages something like python -m SimpleHTTPServer would suffice. 3. A copy of Firefox which would be run for the actual tests. 4. Xvfb - X Virtual Frame Buffer which would be used to provide a "headless GUI" for Firefox to run within. 5. And the requirements for selenium. In general, I have all of the requirements in the setup process detailed for the testing crawler [1]. It integrates fairly well with Jenkins as far as output. If all of the tests pass then it will exit with a POSIX exit code 0 (success). If any of the unit tests fail then it will exit non-zero. So to integrate it with Jenkins one would need to simply add it as a build step in Jenkins. Minimum software requirements are basically what runs Firefox well. As Jehan pointed out the git repository I'll clone it and see what I can come up with. I can get Jenkins up and running java -jar jenkins.war and create a job which I can contribute to you. Though, it will essentially only be a single step job with a shell script executing the robot testing because I don't know what other build steps are involved with the website. That should be enough for you to figure out how to integrate it into your Jenkins build. I'll start with the git repository and go from there. Thanks for pointing it out Jehan. SAM [1]: https://github.com/sag47/chewbotkah ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Updating the website for all the broken download links?
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 the gimp website. I'm using python -m SimpleHTTPServer on the htdocs page and I can view http://localhost:8000and see some of the GIMP website but it appears largely unstyled. What server-side software does the GIMP website require? SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Updating the website for all the broken download links?
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 > configuring a Jenkins build job and found that using a simple http server > does not appear to be enough for the gimp website. I'm using python -m > SimpleHTTPServer on the htdocs page and I can view http://localhost:8000and > see some of the GIMP website but it appears largely unstyled. > > What server-side software does the GIMP website require? > FYI here is my Jenkins job config.xml. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Updating the website for all the broken download links?
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 also > detect dead links that don't result in an HTTP > error but in simply nothing or unreadable garbage? > > Kind regards, > > Sven Hi Sven, If you're inquiring about my link tester then yes it should get it. The [get_link_status function][1] is what does the actual checking. It does a combination of HTTP HEAD method (so it only grabs the headers instead of content) as well has a bit of exception handling for other non-HTTP unexpected responses. If it can be improved I'm all ears for improving it. Also, I'm using python code only in a [main method][2] which means one could write another script which will import frontend_test.py and take advantage of that function (using it like a library instead of an executable). Also, as Jehan pointed out that [INSTALL file][3] returns HTTP 404 not found. So a link checker should catch that. SAM [1]: https://github.com/sag47/chewbotkah/blob/development/frontend_test.py#L38-L83 [2]: https://github.com/sag47/chewbotkah/blob/development/frontend_test.py#L252 [3]: https://git.gnome.org/browse/gimp/plain/INSTALL ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Updating the website for all the broken download links?
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 report the build status. Attached I have a patch of install.sh and the original install.sh. The patch is based off of master 22561ef. I have also attached a standalone install.sh. I added lots of comments and environment information because a good bash script needs environment information in my humble opinion in the off chance it doesn't work years down the road you can at least know what environment it was originally written. SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] Error compiling gimp-web
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}|python2.7|g' -e 's|${LIBDIR}|./htdocs/cgi-common|g'
xhtml.py > ./htdocs/cgi-common/xhtml.py
sed -e 's|${PYTHON}|python2.7|g' -e 's|${LIBDIR}|./htdocs/cgi-common|g'
rdf.py> ./htdocs/cgi-common/rdf.py
sed -e 's|${PYTHON}|python2.7|g' -e 's|${LIBDIR}|./htdocs/cgi-common|g'
x_xml.py > ./htdocs/cgi-common/x_xml.py
sed -e 's|${PYTHON}|python2.7|g' -e 's|${LIBDIR}|./htdocs/cgi-common|g'
changelog.py > ./htdocs/cgi-common/changelog.py
installwgo_config.py ./htdocs/cgi-common
install -m 644 extended.css ./htdocs/style/
install: target ‘./htdocs/style/’ is not a directory: No such file or
directory
make[1]: *** [install-common] Error 1
make[1]: Leaving directory `/home/sam/git/web/gimp-web/programmatic'
make: *** [install] Error 2
Though, ‘./htdocs/style/’ exists and is a directory. So I'm not sure why
it's showing that...
$ ls -l ./htdocs | grep style
drwxrwxr-x 2 sam sam 4096 May 2 11:05 style
I'm currently looking at the make process to figure out what is actually
going wrong but any pointers would be appreciated.
SAM
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Error compiling gimp-web
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> ./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}|python2.7|g' -e 's|${LIBDIR}|./htdocs/cgi-common|g'
> xhtml.py > ./htdocs/cgi-common/xhtml.py
> sed -e 's|${PYTHON}|python2.7|g' -e 's|${LIBDIR}|./htdocs/cgi-common|g'
> rdf.py> ./htdocs/cgi-common/rdf.py
> sed -e 's|${PYTHON}|python2.7|g' -e 's|${LIBDIR}|./htdocs/cgi-common|g'
> x_xml.py > ./htdocs/cgi-common/x_xml.py
> sed -e 's|${PYTHON}|python2.7|g' -e 's|${LIBDIR}|./htdocs/cgi-common|g'
> changelog.py > ./htdocs/cgi-common/changelog.py
> installwgo_config.py ./htdocs/cgi-common
> install -m 644 extended.css ./htdocs/style/
> install: target ‘./htdocs/style/’ is not a directory: No such file or
> directory
> make[1]: *** [install-common] Error 1
> make[1]: Leaving directory `/home/sam/git/web/gimp-web/programmatic'
> make: *** [install] Error 2
>
> Though, ‘./htdocs/style/’ exists and is a directory. So I'm not sure why
> it's showing that...
>
> $ ls -l ./htdocs | grep style
> drwxrwxr-x 2 sam sam 4096 May 2 11:05 style
>
> I'm currently looking at the make process to figure out what is actually
> going wrong but any pointers would be appreciated.
>
> SAM
>
___
gimp-developer-list mailing list
List address:gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Updating the website for all the broken download links?
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 for Jenkins. It's not a > POSIX compatible script which Jenkins requires in order to properly report > the build status. Attached I have a patch of install.sh and the original > install.sh. > > The patch is based off of master 22561ef. I have also attached a > standalone install.sh. > > I added lots of comments and environment information because a good bash > script needs environment information in my humble opinion in the off chance > it doesn't work years down the road you can at least know what environment > it was originally written. > > SAM > I opened a bugzilla report instead. https://bugzilla.gnome.org/show_bug.cgi?id=729421 I'll do that from now on. SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Does anyone want to administer GIMP's continuous integration server (Jenkins)?
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) that we use to > > check that our commits to GIMP, GEGL, babl, etc. build ok and tests > > run properly. > > As I'm leaving the project asap it needs a new maintainer. > > If nobody steps up, then it will have to be abandoned. > > > > What happened, why do you want to leave the project? > > Regards, > Tobias > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list > -- GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Siggraph 2014
+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 the list of GSoC ideas in the wiki? > > Regards > Tobias > > [1] > > http://www.siggraph.org/learn/open-access-s2014-conference-proceedings#Image%20Tricks > [2] http://wiki.gimp.org/wiki/Hacking:GSoC/Future/Ideas > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list > -- GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Two-minute(!)-survey on motivation and free time contribution of open source developers
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, enough English I could understand what was going on. It took me longer to read this thread. -- GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] compilation of current git master fails
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: >>> >>> commit 4c7338c0974096dca8566a1d570ed51fbe721ae6 >>> Author: Michael Natterer >>> Date: Mon Feb 16 19:35:00 2015 +0100 >>> >>> app: link against -lm, whatever new linker version seems to need is >>> >>> app/Makefile.am | 5 - >>> 1 file changed, 4 insertions(+), 1 deletion(-) >>> >> Good news, but it's a strange behavior. :-D >> >>> >>> On Sun, 2015-02-15 at 20:13 +0300, Alexander Rabtchevich wrote: >>> Hello Compilation of the current git master fails on Mint 17 64x. Here is the error from the console. Make clean does not help. CC main.o CC gimp_console_2.9-app.o CC gimp_console_2.9-batch.o CC gimp_console_2.9-errors.o CC gimp_console_2.9-language.o CC gimp_console_2.9-sanity.o CC gimp_console_2.9-signals.o CC gimp_console_2.9-tests.o CC gimp_console_2.9-unique.o CC gimp_console_2.9-units.o CC gimp_console_2.9-gimp-debug.o CC gimp_console_2.9-gimp-log.o CC gimp_console_2.9-main.o CC version.o CC gimp_console_2.9-version.o CCLD gimp-console-2.9 AR libapp.a CCLD gimp-2.9 /usr/bin/ld: pdb/libappinternal-procs.a(plug-in-compat-cmds.o): undefined reference to symbol 'fmod@@GLIBC_2.2.5' //lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[4]: *** [gimp-console-2.9] Error 1 make[4]: *** Waiting for unfinished jobs /usr/bin/ld: pdb/libappinternal-procs.a(plug-in-compat-cmds.o): undefined reference to symbol 'fmod@@GLIBC_2.2.5' //lib/x86_64-linux-gnu/libm.so.6: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[4]: *** [gimp-2.9] Error 1 make[4]: Leaving directory `/home/sasha/Install/gimp/app' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/sasha/Install/gimp/app' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/sasha/Install/gimp/app' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/sasha/Install/gimp' make: *** [all] Error 2 With respect, Alexander Rabtchevich >>> >> > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: https://mail.gnome.org/mailman/listinfo/gimp- > developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list > -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] What next after sourceforge.net?
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 torrent link and the direct link (to e.g. the Windows > .exe file) more obvious. The reason for emphasizing the torrent file > over the direct link was to spread knowledge of BitTorrent and put less > load on our server, but having both as equals should work just as fine. > > There has been another proposal on our #gimp IRC channel to make the > platform selection available again, I'm currently checking the status of > that. > > Yeah... most non-technical people haven't heart of torrents (except for maybe the ones downloading illegal software, movies, and music). The largest link for Windows on that page is a misleading .torrent link (as a normal person would expect to download the software to install it rather than download a file that requires them to install other software to install it). In fact, the direct download link for Windows is a tiny "this link" at the end of the description paragraph underneath the GIANT torrent link. There are plenty of trusted binary hosting services for open source projects. One not need look far for alternate hosting if the worry is GIMP infrastructure overload. Personally I feel the "Download" button on the front page should actually download the software (detecting your browser language and platform). Then perhaps make the link on the right called "Downloads" or "More Downloads" where users can find the comprehensive list of items to download to their heart's content. Regardless of the way in which the downloads are presented. I do think the downloads page is pretty busy. My friends need someone like me to help them sort it out when they're getting their copy of GIMP. I feel that flow is in need of improvement. SAM -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] upload to Steam
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, and could also make > sharing community plug-in easier > It has been mentioned on the user list as well as the developer list. http://www.mail-archive.com/gimp-user-list%40gnome.org/msg04505.html http://www.mail-archive.com/gimp-developer-list%40gnome.org/msg04651.html (this thread has a lot of discussion) The TLDR at the time was developers didn't want to distribute through a proprietary platform or require users to have a Steam account to download. I was then, and still now, of the opinion it would be great to distribute through Steam in *addition* to our normal download channels for obtaining GIMP. Some of the modelers and game mod developers use GIMP to create textures for their models. As it stands, I don't think Steam will be a considered distribution channel unless a core developer wishes to speak up with a change of opinion. It would also require a contributor to get familiar with the Steam release process and provide steam releases as GIMP is released. -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] Portable development environment for GIMP
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 than hours of dependency discovery. ***It takes the pain out of building GIMP for the first time**.* https://github.com/samrocketman/vagrant-gimp Instructions: 1. Install vagrant https://www.vagrantup.com/ 2. Clone: git clone https://github.com/samrocketman/vagrant-gimp 3. cd vagrant-gimp 4. vagrant up 5. Log in with username: vagrant, password: gimp It will automatically provision Debian Jessie 64-bit, upgrade the OS, install all GIMP development dependencies, and build GIMP. It builds babl, gegl, and gimp from the master branch. After logging in, open a terminal and open the latest development version of GIMP by typing "gimp-2.9". All of the GIMP user settings are stored in ~/.config/GIMP/2.9. Right now only babl, gegl, and gimp are cloned. Some other ideas I have around this include cloning all of the GIMP project repositories (including the website, etc.). Please tell me your thoughts/feedback/ideas. SAM (irc nickname samrocketman) -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] On Portable GIMP/Vagrant development environment
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 the vm. > It should have cloned GIMP source in the following steps (upon typing "vagrant up"). https://github.com/samrocketman/vagrant-gimp/blob/43fd5d67fa2808ad8f987ee626bcbd6451a475dd/Vagrantfile#L55 https://github.com/samrocketman/vagrant-gimp/blob/43fd5d67fa2808ad8f987ee626bcbd6451a475dd/setup/everything.sh#L41 https://github.com/samrocketman/vagrant-gimp/blob/43fd5d67fa2808ad8f987ee626bcbd6451a475dd/setup/gimp-source/install.sh#L18-L34 > I attach the log copied directly from the terminal. In this way you can > see the way your solution is used by a random person. My approach is to try > first is everything works and then, if necessary - to fix the stuff. > So, here is what I did: > 1. Read your e-mail, read the readme.md at > https://github.com/samrocketman/vagrant-gimp > 2. git clone https://github.com/samrocketman/vagrant-gimp.git (SUCCESS) > 3. cd vagrant-gimp && vagrant up (FAILURE: "The program 'vagrant' is > currently not installed.") > 4. sudo apt-get install vagrant (OK) > 5. vagrant up (FAILURE: "Vagrant could not detect VirtualBox") > 6. sudo apt-get install virtualbox (OK) > 7. vagrant up (FAILURE: vm: * The box 'debian/jessie64' could not be > found.) > 8. as the error looked strange, I went to the vagrant site and installed > the latest provided version=1.7.4. (OK) > > *COMMENT*: up to this step I had the problems with wrong version of the > vagrant. I accept that I ignored your first instruction in the e-mail ( 1. > Install vagrant https://www.vagrantup.com/), but on the other hand, > neither this e-mail, nor github repo mentioned that I absolutely must use > the latest version from the site instead of the provided by the system => I > wrongly supposed that any version is ok. > I have incorporated your feedback into the README. See the section at the top for prerequisites. https://github.com/samrocketman/vagrant-gimp/blob/43fd5d67fa2808ad8f987ee626bcbd6451a475dd/README.md#prerequisites > 9. vagrant up (FAILURE: "Atlas push: * Missing required configuration > parameter 'token'") > 10. tried vagrant login with provided vagrant/gimp pair (FAILURE) > 11. registered on https://atlas.hashicorp.com/ (OK) > 12. vagrant login (OK) > > *COMMENT*: these mistakes are also stupid for those who know what vagrant > is, but for others I believe this behavior can be completely logical. > These mistakes are not stupid and an account at hashicorp should not have been a barrier to entry. I have updated the bootstrapping process and removed this requirement. https://github.com/samrocketman/vagrant-gimp/blob/43fd5d67fa2808ad8f987ee626bcbd6451a475dd/Vagrantfile#L43-L45 > 13. vagrant up (OK, but it was not extremely fast on my 8MBit connection) > 14. I tried to log in into the running system, but did not succeed for > unknown reason (FAILURE) > 15. shutdown the vm with "sudo shutdown" and vagrant reload (OK) > 16. could not find the GIMP sources => *FAILURE* > > In fact I found the scripts in setup/gimp-packages/ and other folders, but > I don't know where the sources actually are. You say "There should the > following files and directories in the vagrant user. > >- ~/gimp-git - contains all of the output from the gimp build. >- ~/gimp-git/share/config.site - a file containing variables used by >the build process. >- ~/git/babl - source code of BABL >- ~/git/gegl - source code of GEGL >- ~/git/gimp - source code of GIMP >- ~/build-gimp.sh - a script to compile BABL, GEGL, and GIMP all at >once." > > But they are just not there. > // I attach a complete host log if it helps. > After reviewing your log it appears the bootstrap failed due to an out-of-date package. I'll work on bootstrapping again to ensure that it is fixed. It's quite possible Debian Jessie removed the package. Here's the excerpt from the log. ==> default: Package libjpeg8-dev is not available, but is referred to by another package. ==> default: This may mean that the package is missing, has been obsoleted, or ==> default: is only available from another source ==> default: However the following packages replace it: ==> default: libjpeg62-turbo-dev ==> default: E ==> default: : ==> default: Package 'libjpeg8-dev' has no installation candidate ==> default: + apt-get update --fix-missing ==> default: Hit http://security.debian.org jessie/updates InRelease ==> default: Hit http://security.debian.org jessie/updates/main Sources ==> default: Hit http://security.debian.org jessie/updates/main amd64 Packages ==> default: Hit http://security.debian.org jessie/updates/main Translation-en ==> default: Ign http://httpredir.debian.org jessie InRelease ==> default: Get:1 http://httpredir.debian.org jessie Release.g
Re: [Gimp-developer] On Portable GIMP/Vagrant development environment
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/samrocketman/vagrant-gimp/commit/46a563b4d4d69cc3397a811f673146c0d2ffc672 To fix your development environment be sure you're in the vagrant-gimp working directory (the one you cloned) 1. git pull origin master 2. vagrant destroy 3. vagrant box update 4. vagrant up That should correctly bootstrap your environment. For anyone else, refer to the README at https://github.com/samrocketman/vagrant-gimp Please let me know how your second experience goes. SAM -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Portable development environment for GIMP
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? > > Because it's a UI. Would you rather build headless? -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Portable development environment for GIMP
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 not everyone's preference in UI. What UI do you and > other > > core developers use? > > I'd say that we should stick to something that has the same basic > dependencies as GIMP - XFCE, for example. > > +mailing list XFCE would definitely lighten the load in terms of number of dependencies. UI aside, any feedback on how I'm building GIMP? Have you tried spinning up the development environment? Is it able to build GIMP like one would expect? Should I have it auto-build GIMP for the first time as part of the bootstrapping? -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Portable development environment for GIMP
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 right in and develop. -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Portable development environment for GIMP
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 a Linux VM over my existing Linux install is a bit > wasteful? In this case, it is not wasteful. Consider the goals of this project (and development from the perspective of a newcomer). NEWCOMER PERSPECTIVE: * Must assemble over 100 dependency packages from Debian (for Debian GNU/Linux alone; not including other platforms). * Must clone two additional projects (GEGL and BABL). * Must compile projects in the correct order: 1) BABL 2) GEGL 3) GIMP. * On the mailing list there's a lot of "works for me, so it must be something wrong with what you're doing" The point of a bootstrapped development environment is to avoid even having to answer most of the above questions before they're even asked. PRIMARY GOALS: * Lower the barrier to entry for contributing to GIMP source code. * Repeatable and consistent configuration between someone who is new and someone who can verify if issues experienced by the new contributor is with the development environment or with GIMP itself. FUTURE: Even when I maintain the build system at build.gimp.org there's regularly a "works for me" statement when the build system fails but it passes on a developers laptop. These challenges hinder progress when having a repeatable build environment would solve these issues. Future-looking action items for me that will come out of this: * Containerize (via docker) a build environment based off of the vagrant bootstrap development environment. This means build.gimp.org will run the same code and dependencies as the development environment. Avoids the "works for me" syndrome between core developers and the build system. * Create a Windows-based development environment based on https://atlas.hashicorp.com/modernIE and https://dev.modern.ie/ (free Windows VMs provided by Microsoft). CONCLUSION: By settling on a convention for how we build the GIMP software we'll: * speed up development velocity * be more consistent * have a lower barrier to entry for new contributors SAM -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] Portable development environment for GIMP
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 might not even contain some of the required > dependencies. Due to the recent release of Jessie, this is not very > noticeable yet. > > A moving target like Debian Testing is probably a less than optimal > building block for a vagrant-based approach. I'm aware the core devs use Debian testing. I would have used Debian testing but currently there's no Debian testing in any of the tooling like Vagrant [1] and Docker [2]. However, as time progresses, and new Debian versions come out, the development tooling can to be updated to newer Debian versions before any anticipated or noticeable divergence occurs. If a divergence becomes a regular problem then perhaps it would be more useful to fall back on developing in a more stable platform. Though, since that isn't currently an issue it's just a thought. [1]: https://atlas.hashicorp.com/debian/ [2]: https://hub.docker.com/_/debian/ -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] building GIMP from git
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_LIBRARY_PATH=/usr/local/lib gimp-2.9 GIMP will then look to /usr/local/lib for its GEGL and BABL libraries instead of /usr/lib (which is where it is typically installed by a package manager). On Wed, Oct 7, 2015 at 11:31 PM, Olivier wrote: > In fact, I also built glib from git, thus maybe GIO_EXTRA_MODULES was also > needed. Anyway, I used it and everything is OK now. > > Olivier Lecarme > > 2015-10-07 21:23 GMT+02:00 Elle Stone : > > > On 10/07/2015 12:54 PM, Olivier wrote: > > > >> Finally I succedded in installing GIMP, by fetching gegl, babl, > >> gdk-pixbuf, and gimp itself from git, and configuring and installing > >> them all under the same prefix. Under Ubuntu 15.04, the GIO extra > >> modules are located in usr/lib/x86_64-linux-gnu/gio/modules. > >> > >> Thus I used Martin Nordholts' explanation in > >> http://www.gimp.org/source/howtos/gimp-git-build.html, but I added > gegl, > >> babl, and gdk-pixbuf tothe packages to be fetched from git, compiled and > >> installed, and I added GIO_EXTRA_MODULES to the exported variables, > >> although I'm not sure that is needed. > >> > >> Thanks to all! > >> > >> Olivier Lecarme > >> > > > > Based on comments in https://aur.archlinux.org/packages/gegl-git/, it > > does look like maybe the original problem was that GIMP was finding a > > too-outdated version of GEGL. > > > > I never needed to export GIO_EXTRA_MODULES until I tried to run GIMP 2.8 > > installed from the Gentoo package manager alongside babl/GEGL/GIMP from > git > > installed in a prefix. But here's the reference, fwiw: > > > > > > > https://mail.gnome.org/archives/gimp-developer-list/2015-February/msg00042.html > > > > > https://mail.gnome.org/archives/gimp-developer-list/2015-February/msg00051.html > > > > Looking at what Mitch said, it seems exporting GIO_EXTRA_MODULES is only > > be needed if glib is also built in the prefix. So sorry for the noise! if > > you didn't also build glib in the prefix. > > > > For the next person trying to build GIMP from git who might stumble over > > this thread, a few other "why it doesn't work and what to do" are > > documented here: > > > > http://wiki.gimp.org/wiki/Hacking:Problems_and_solutions > > > > > > > -- > Olivier Lecarme > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list > -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] WGO Transition Meeting
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 transition makes me lose focus but I think it's a minor issue if an issue at all for others. On Thu, Nov 12, 2015 at 2:11 PM, Pat David wrote: > For reference (thanks Sam!), > > SGO = http://static.gimp.org > This is going to be the new website soon. > > WGO = http://www.gimp.org > This site will soon be replaced by what is on static.gimp.org > > On Thu, Nov 12, 2015 at 3:49 PM Pat David wrote: > > > We had a meeting today on #gimp-web around what needs to be done to the > > new site (SGO) as we transition to replace the old one (WGO). > > > > The consensus was that there are still a few things to iron out, but that > > we should be able to announce the new site in time to coincide with our > > 20th anniversary on November 21. > > > > I am still soliciting any input that anyone would like to add (bonus > > points if you actually use bugzilla to ease the tracking and > classification > > of feedback: > > https://bugzilla.gnome.org/page.cgi?id=browse.html&product=gimp-web). > > > > This is not a comprehensive list of things I'm working on for the site. > > There are still lingering things that I didn't bother to add to the list > > (static image asset social link stuff that's being looked at, including > > donations links for instance). > > > > Below is the list of items and notes from the meeting ( > > https://public.etherpad-mozilla.org/p/SGO_Meeting) > > > > SGO Pre-Release meeting > > > > Content > > > > > >- Tutorials Index - being rebuilt - only Free/Libre content from now > >on! > > > > > >- Not internally linking to old (c) tutorials - but keeping URI's > > > > > >- > > > > > >- Tutorials - add section on contributing new tutorials (how-to), > >along with > > > > > >- message template to send to ML specifying license. > > > > > >- Acceptable licenses? > > > > > >- GFDL > > > > > >- CC-(0|BY)-(SA)? (not accepting NC/ND) > > > > > >- Free Art (http://artlibre.org/) > > > > > > > >- Create a more detailed "how to contribute a tutorial" section. > > > > > >- Consider styling the tutorial list better (date/version/etc?) > > > > > >- > > > > > >- Art > > > > > >- Aryeom is making new download page image + 404 error page image + > >Wilber SVG for tiny icon > > > > > >- > > > > > > Styling (CSS) > > > >- > > > > > >- Header > > > > > >- Put the Wilber/GIMP link back in header on index page (Header nav) > > > > > > > >- Footer > > > > > >- Distribute single column links across three columns in footer > > > > > > > >- There are two styling ideas currently that are similar, > > > > > >- Content pages > > > > > >- News Items > > > > > >- Need to fix some styling to be consistent between the two. > > > > > >- > > > > > >- Fonts > > > > > >- Change fonts from (Open Sans) weight: 300, color: #777 > > > > > >- Change to: weight: normal (400), color: #666 > > > > > > Download button on index page: version numbers are too close and > dot > > too small. Use better font? (same as the Windows download page buttons > for > > instance?). > > > >- PD: I'll keep the font and style the spacing a bit better to > >be more clear > > > > > > Operations > > > > > >- SSL/https > > > > > >- Check internal links for HTTPS > > > > > >- Support HTTPS, no redirect for HTTP (allow browsing either protocol) > > > > > > > >- testing branch? > > > > > >- Yes - same way it is being used right now. > > > > > >- Find a possible way to hook against a tag or branch for automating a > >push into master (after verifying testing) > > > > > > Transition to www.gimp.org (check with schumaml to make this happen) > > > >- keep old content around > > > > > >- move to legacy branch (yes) > > > > > >- add read-only legacy.gimp.org? (yes) > > > > > > > >- > > > > > > > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list > -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman curl https://keybase.io/samrocketman/key.asc | gpg --import - Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: ht
Re: [Gimp-developer] xdg-app; was: WGO Transition Meeting
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 such technology is stable enough, we should be able to propose > real distro-independent packages for GIMP (which are not ugly binaries > in tarball to uncompress in a dirty way without any desktop > integration). > I would think using a distro-independent packager is more useful then something like xdg-app. There's a couple in existence already I can think off the top of my head. * FPM - https://github.com/jordansissel/fpm * omnibus - https://github.com/chef/omnibus I think it would be useful to have regular builds of packages along with builds of the software; if we can get that far. I'd rather dpkg -i or rpm -i to install a package than use a 3rd party app. For Windows/Mac platforms I'd say it's useful but for Linux I don't have much of a use for it. I had proposed a 3rd party platform to be distro-independent in the past (Steam) but there wasn't much interest around supporting that. SAM -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman curl https://keybase.io/samrocketman/key.asc | gpg --import - Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] GIMP can't find libmypaint-gegl
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 workaround in the PR description. Additionally, I've created a libmypaint-master job on the build server - https://build.gimp.org/job/libmypaint-master/ I made updates to the gimp-master job but I'm still having difficulties getting it to correctly build. On Mon, Dec 28, 2015 at 12:04 AM, scl wrote: > Hi, > > I'm facing the same problem when trying to build GIMP with Sam's > portable environment Vagrant VM. > Just FYI the issue is already reported to Sam's Github repo. > > Have all a happy new year ;-) > > Greetings > > Sven > > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list > -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman curl https://keybase.io/samrocketman/key.asc | gpg --import - Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] GIMP testing cooperation
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 > > issue.It is literally only reason people do that now when we have > > travis-ci.org/https://circleci.com/etc.Travis is even free for > > opensource projects. > > > > https://build.gimp.org/plugin/disk-usage/ looks pretty full to me, for > > example. External CI do not have problems with that. > > We know of the disk usage issue: > https://bugzilla.gnome.org/show_bug.cgi?id=776631 > That's one of the many issues which triggered us into either looking > for alternative solutions or collaboration or whatever you want. > Basically we want something which works, is useful and reliable. The > "need" stops there. > > After, which software is it using? I think we don't really care. Now > obviously we'd prefer our whole infrastructure to run on Free > Software. And personally I like self-hosting for full control. But > then there is reality check: it requires contributor time and > administration skills. So in the end, the CI contributor(s) choose. In > the GIMP team, our policy is more or less that the one who *do* are > the one who are in charge of what they do. > > Jehan > Since I don't appear to be seen as a contributor or "doer" I'm happy to just step down completely and remove myself from the project. Much as I like GIMP I don't really like the tone of the thread. ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] GIMP testing cooperation
Hello gimp-dev and community, I'd like to apologize for my remarks. I think my pride got in the way a bit and I definitely misunderstood the intent of the thread. Hopefully, my reaction does not turn of RedHat for wanting to contribute. I will take this as an opportunity to reflect on my actions and work to continue to improve myself. I definitely want to be seen as a healthy part of this community and I really do appreciate and love what the GIMP dev team does. 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. Even if you're new to Linux and wish to get better at Linux (zero experience) I'm willing to provide you training and act as a senior for advice in Linux system administration. I'll try to keep conversation more productive than my first reply to 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 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 > >> > issue.It is literally only reason people do that now when we have > >> > travis-ci.org/https://circleci.com/etc.Travis is even free for > >> > opensource projects. > >> > > >> > https://build.gimp.org/plugin/disk-usage/ looks pretty full to me, > for > >> > example. External CI do not have problems with that. > >> > >> We know of the disk usage issue: > >> https://bugzilla.gnome.org/show_bug.cgi?id=776631 > >> That's one of the many issues which triggered us into either looking > >> for alternative solutions or collaboration or whatever you want. > >> Basically we want something which works, is useful and reliable. The > >> "need" stops there. > >> > >> After, which software is it using? I think we don't really care. Now > >> obviously we'd prefer our whole infrastructure to run on Free > >> Software. And personally I like self-hosting for full control. But > >> then there is reality check: it requires contributor time and > >> administration skills. So in the end, the CI contributor(s) choose. In > >> the GIMP team, our policy is more or less that the one who *do* are > >> the one who are in charge of what they do. > >> > >> Jehan > > > > > > Since I don't appear to be seen as a contributor or "doer" I'm happy to > just > > step down completely and remove myself from the project. Much as I like > > GIMP I don't really like the tone of the thread. > > I don't really understand what triggers this sudden anger but I see > you are quoting one of my last emails. And if that is your trigger, > then you got the opposite of its meaning since what it meant is that > *you* were the one in charge since *you* are the one who does right > now! So whoever who wants something different has to go through you > first then help you make things happen. > > You are considered a contributor and a doer. That's even what I said > in my first email (if you haven't, please read it: > https://mail.gnome.org/archives/gimp-developer-list/ > 2016-September/msg00018.html), > which was the most important, answering Vladimir and telling him to > get in touch with you because you are the one making things happen > right now. That's pretty much the definition of both a contributor of > the project and a doer. > > Now if the problem is that we are welcoming additional administrators > who want to help (especially if they could be backed by a big company > like RedHat), I don't understand. Having additional administrators > won't mean at all that we reject you or anything, quite the contrary > (cf. again my first email). But if you absolutely want to be alone to > administrate (and if that were your issue here), then yes it is a > problem. You don't have all the time of the world to maintain > perfectly the server (which is no big deal at all! You also have a > life and do this voluntarily. We thank you for this), but several > admins together could. Same as we are several developers (fortunately > since none of us could maintain GIMP as wel
Re: [Gimp-developer] GIMP testing cooperation
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: > > > Hello Sam, > > [...] > > > I don't really understand what triggers this sudden anger but I see > > you are quoting one of my last emails. And if that is your trigger, > > then you got the opposite of its meaning since what it meant is that > > *you* were the one in charge since *you* are the one who does right > > now! So whoever who wants something different has to go through you > > first then help you make things happen. > > Speaking of which, I think the following is an issue with the build > environment: > > https://bugzilla.gnome.org/show_bug.cgi?id=787115 > > P.S. Sam, do you receive Bugzilla notification mails for these bugs? > > > -- > Regards, > Michael > GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: https://mail.gnome.org/mailman/listinfo/gimp- > developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list > ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
Re: [Gimp-developer] GIMP testing cooperation
Heh, I've seen ofnuts post before so I don't mind onboarding him. On Fri, Oct 6, 2017 at 5:10 PM, Pat David wrote: > I can vouch for Ofnuts not being an awful malicious actor. But I can’t > vouch for him not being awful. :D (I kid, I kid). > > On Fri, Oct 6, 2017 at 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. Even if you're new to Linux and wish to get better at Linux > (zero > > > experience) I'm willing to provide you training and act as a senior for > > > advice in Linux system administration. > > > > > > > *steps forward* > > ___ > > gimp-developer-list mailing list > > List address:gimp-developer-list@gnome.org > > List membership: > > https://mail.gnome.org/mailman/listinfo/gimp-developer-list > > List archives: https://mail.gnome.org/archives/gimp-developer-list > > > -- > https://patdavid.net > GPG: 66D1 7CA6 8088 4874 946D 18BD 67C7 6219 89E9 57AC > ___ > gimp-developer-list mailing list > List address:gimp-developer-list@gnome.org > List membership: https://mail.gnome.org/mailman/listinfo/gimp- > developer-list > List archives: https://mail.gnome.org/archives/gimp-developer-list > ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] Welcome backup admins to build.gimp.org
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 infrastructure repositories hosted at https://github.com/gimp-ci Please join me in welcoming them. SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] I would like collaborator access
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]: https://gitlab.gnome.org/GNOME/gimp [2]: https://gitlab.gnome.org/GNOME/gimp/issues?label_name%5B%5D=5.+Jenkins ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Gimp-developer] build.gimp.org re-architecture complete
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 Ocean) which nicely renders build pipelines. For example: https://build.gimp.org/blue/organizations/jenkins/gegl/detail/master/3/pipeline The GIMP build server has also been re-designed so that anybody can run it from their local computer if they desire. Key repositories include: - https://github.com/gimp-ci/jenkins-os-packages - The Jenkins operating system packages used on build.gimp.org. These are immutable packages which contain all Jenkins plugins included. - https://github.com/gimp-ci/docker-jenkins-gimp This repository contains the shell scripts used to build GIMP and its dependencies. It is also the source for the Docker container in which GIMP and all of its dependencies are built. An official image has also been published to docker hub https://hub.docker.com/r/gimp/gimp/ - https://github.com/gimp-ci/jenkins-dsl - The source for all Jenkins jobs and pipelines used to build GIMP and its dependencies. There is also a documentation repository but it needs to be updated. I'll be working on updating all of the documentation next in case someone really does to run a copy of their own build system themselves. Bonus tweet: running the three latest major versions of GIMP from their development branches. All on the same computer and within Docker containers. https://twitter.com/sag47/status/998641858065588224 That's all for now, SAM ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
