[jira] [Resolved] (GUMP-163) patch for forrest config to apply trademark to logos
[ https://issues.apache.org/jira/browse/GUMP-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved GUMP-163. - Resolution: Fixed I've committed the patch, many thanks. Personally I'm reasonably happy with the outcome and could merge the two svgs directly (but then again don't know enough about svg to not mess up). patch for forrest config to apply trademark to logos Key: GUMP-163 URL: https://issues.apache.org/jira/browse/GUMP-163 Project: Gump Issue Type: Improvement Components: Documentation Reporter: David Crossley Attachments: logo-tm.txt Use the new Forrest logo input plugin to apply a trademark. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Help needed with ASF Branding Requirements
On 2011-06-10, David Crossley wrote: Stefan Bodewig wrote: I think we cover all the rest of the requirements - but I'll double check - except for our logos that need TM symbols. I'm still not capable of doing any artwork so please, who ever feels like using Gimp or Photoshop or Paint, you are more than welcome to TMify the bench logos (the one on our main site as well as the one on our reports). I am no graphics expert either. I started a Forrest plugin to assist with this. See config patch at GUMP-163 Many many thanks. It overlays a trademark symbol using SVG to create a new image. IIUC we could merge the overlay directly into the logo, is that correct? I'm not familiar with SVG at all but maybe that needs to change anyway. This patch only applies it to the main Gump logo. Add the other reports logo to xdoc/images/ temporarily (i notice that it has the same filename) or give it a new name. I think it is bench.svg, but I'm not sure. Tweak its related SVG file to position its TM appropriately. I'll give it a try. Hope that helps. Thanks again Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Help needed with ASF Branding Requirements
On 2011-06-12, Stefan Bodewig wrote: On 2011-06-10, David Crossley wrote: This patch only applies it to the main Gump logo. Add the other reports logo to xdoc/images/ temporarily (i notice that it has the same filename) or give it a new name. I think it is bench.svg, but I'm not sure. No, it is not. bench.svg doesn't include the feather above the bench. No idea what the source of the reports logo is, it likely isn't in svn. I'll see whether I manage to extract the feather from the site logo by diffing bench.svg and the site logo's svg. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: Help needed with ASF Branding Requirements
On 2011-06-12, Stefan Bodewig wrote: On 2011-06-12, Stefan Bodewig wrote: On 2011-06-10, David Crossley wrote: This patch only applies it to the main Gump logo. Add the other reports logo to xdoc/images/ temporarily (i notice that it has the same filename) or give it a new name. I think it is bench.svg, but I'm not sure. No, it is not. bench.svg doesn't include the feather above the bench. No idea what the source of the reports logo is, it likely isn't in svn. I'll see whether I manage to extract the feather from the site logo by diffing bench.svg and the site logo's svg. No chance without making myself more familiar with SVG first, which won't happen too soon. Both files refer to asf-logo.svg that I don't find anywhere and I think this is the one that pulls the feather in. It is displayed in one and not displayed in the other. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
BATCH: All dressed up, with nowhere to go...
Dear Gumpmeisters,
The following 1 notifys should have been sent
*** G U M P
[GUMP@vmgump]: Project commons-jelly-tags-ant-test (in module commons-jelly)
failed
*** G U M P
[GUMP@vmgump]: Project commons-jelly-tags-ant-test (in module commons-jelly)
failed
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at general@gump.apache.org.
Project commons-jelly-tags-ant-test has an issue affecting its community
integration.
This issue affects 1 projects.
The current state of this project is 'Failed', with reason 'Build Failed'.
For reference only, the following projects are affected by this:
- commons-jelly-tags-ant-test : Commons Jelly
Full details are available at:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-ant-test/index.html
That said, some information snippets are provided here.
The following annotations (debug/informational/warning/error messages) were
provided:
-DEBUG- Dependency on ant exists, no need to add for property
maven.jar.ant-optional.
-DEBUG- Dependency on xml-xerces exists, no need to add for property
maven.jar.xerces.
-DEBUG- Dependency on commons-jexl-1.x exists, no need to add for property
maven.jar.commons-jexl.
-WARNING- Overriding Maven properties:
[/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/build.properties]
-DEBUG- (Apache Gump generated) Apache Maven Properties in:
/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/build.properties
-INFO- Failed with reason build failed
-DEBUG- Maven POM in:
/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/project.xml
-DEBUG- Maven project properties in:
/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/project.properties
-INFO- Project Reports in:
/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/target/test-reports
The following work was performed:
http://vmgump.apache.org/gump/public/commons-jelly/commons-jelly-tags-ant-test/gump_work/build_commons-jelly_commons-jelly-tags-ant-test.html
Work Name: build_commons-jelly_commons-jelly-tags-ant-test (Type: Build)
Work ended in a state of : Failed
Elapsed: 9 secs
Command Line: maven --offline jar
[Working Directory: /srv/gump/public/workspace/commons-jelly/jelly-tags/ant]
-
[junit] Actual expression: (${foo4.1})=(null)
[junit] at
org.apache.commons.jelly.tags.junit.AssertTagSupport.fail(AssertTagSupport.java:44)
[junit] at
org.apache.commons.jelly.tags.junit.AssertTagSupport.failNotEquals(AssertTagSupport.java:77)
[junit] at
org.apache.commons.jelly.tags.junit.AssertEqualsTag.doTag(AssertEqualsTag.java:56)
[junit] at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:267)
[junit] at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
[junit] at
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:60)
[junit]
[junit]
[junit] Testcase:
startUpReadWrite(org.apache.commons.jelly.tags.junit.CaseTag$1): Caused an
ERROR
[junit]
file:/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/target/test-classes/org/apache/commons/jelly/ant/suite.jelly:98:5:
test:assertEquals
file:/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/target/test-classes/org/apache/commons/jelly/ant/suite.jelly:98:5:
test:assertEquals expected:[bar5] but was:[null]
[junit] Expected expression: (bar5)=(bar5)
[junit] Actual expression: (${foo5.1})=(null)
[junit] org.apache.commons.jelly.JellyTagException:
file:/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/target/test-classes/org/apache/commons/jelly/ant/suite.jelly:98:5:
test:assertEquals
file:/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/target/test-classes/org/apache/commons/jelly/ant/suite.jelly:98:5:
test:assertEquals expected:[bar5] but was:[null]
[junit] Expected expression: (bar5)=(bar5)
[junit] Actual expression: (${foo5.1})=(null)
[junit] at
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:732)
[junit] at
org.apache.commons.jelly.impl.TagScript.run(TagScript.java:287)
[junit] at
org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:96)
[junit] at
org.apache.commons.jelly.tags.junit.CaseTag$1.runTest(CaseTag.java:60)
[junit] Caused by:
org.apache.commons.jelly.tags.junit.JellyAssertionFailedError:
file:/srv/gump/public/workspace/commons-jelly/jelly-tags/ant/target/test-classes/org/apache/commons/jelly/ant/suite.jelly:98:5:
test:assertEquals expected:[bar5] but was:[null]
[junit] Expected expression: (bar5)=(bar5)
[junit] Actual expression: (${foo5.1})=(null)
[junit] at
Re: Help needed with ASF Branding Requirements
Stefan Bodewig wrote: David Crossley wrote: Stefan Bodewig wrote: I think we cover all the rest of the requirements - but I'll double check - except for our logos that need TM symbols. I'm still not capable of doing any artwork so please, who ever feels like using Gimp or Photoshop or Paint, you are more than welcome to TMify the bench logos (the one on our main site as well as the one on our reports). I am no graphics expert either. I started a Forrest plugin to assist with this. See config patch at GUMP-163 Many many thanks. However, i noticed yesterday (at Forrest) that the generated PNG has changed colour. Same for Gump. Drat. (FOR-1226) We have been needing to update the Batik used by both Cocoon and Forrest for some time. Perhaps that will help. It overlays a trademark symbol using SVG to create a new image. IIUC we could merge the overlay directly into the logo, is that correct? I'm not familiar with SVG at all but maybe that needs to change anyway. Yes it could. This plugin was just a simple solution to take an existing PNG and generate a new PNG. Yes looking now at the gump-logo-original.svg it would be relatively easy to add the text element directly into that SVG. This patch only applies it to the main Gump logo. Add the other reports logo to xdoc/images/ temporarily (i notice that it has the same filename) or give it a new name. I think it is bench.svg, but I'm not sure. Tweak its related SVG file to position its TM appropriately. I was only considering doing as above to generate a new PNG from the old PNG. Yes amending the SVG directly would be better. -David I'll give it a try. Hope that helps. Thanks again Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: What to do with vmgump2?
On 2011-06-08, Stefan Bodewig wrote: On 2011-06-03, Stefan Bodewig wrote: The machine has been sitting unmaintained for a while now and I think we should decide what to do with it. From the top of my head I see two options: * give it back to infra * run Gump on OpenJDK 7 once it is released but maybe anybody else around has another idea. Unless anybody yells I'll start the process of handing it back to infra next week. Done Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Board Report Q2 2011
Apache Gump is a cross-project continuous integration server. It is different from usual CI servers in that it expects the individual project builds to succeed; its purpose is to check the integration of a project with the latest code rather than a fixed version of the project's dependencies. If you want a more traditional nightly build server, Gump is not for you. Use Gump if you want to know when a change in your dependencies breaks your project or when your changes break other projects. Gump's intention isn't so much to be a CI server but rather a vehicle that makes people look beyond their project's boundaries and helps the projects to collaborate. Gump is written in Python and supports several build tools and version control systems. The Apache installation of Gump builds many ASF projects and their dependencies. It started in the Java part of the foundation but also builds projects like APR, HTTPd and log4net. == Summary == No development activity at all, no issues. == Issues == There are no Board level issues. == Community == The Gump project really consists of two parts, the code base for the project and the ASF installations[1] running this code base to build many ASF projects as well as some related projects. The code base mostly does what its current users need so there isn't much development going on at all. No new committers have been added. All ASF committers have write access to the metadata that configure the ASF installations. There are a few people contributing across all projects and a few additional people maintaining the metadata of the projects they are interested in the most. No changes to the PMC. All in all the community is pretty small by now and it has been a long time since a new project has been added to the Gump runs because the project had asked for it - when we've added new projects over the past two years the driver has been the Gump community. It looks as if most projects are content with the existing vanilla CI options. == Development == None. == Releases == The ASF installations of Gump work on the latest code base almost all of the time. The project is in a state of a perpetual beta. There have been no releases. == Infrastructure == The infra team has provided us with a VM to run Gump on top of Apache Harmony but it is currently not used, we'll hand it back to infra so it doesn't waste resources. At one point in time a Gump run on the FreeBSD jail created many core dumps that filled up the disk space shared by all jails. Gump is now set up to not allow core dumps since nobody would want to look at them anyway. == Project Branding Requirements == We've updated the first sentence of the description to match the revised requirement. Thanks to David Crossley the main site logo now contains a TM and we are confident we will manage to add a TM to the logo Gump uses in its reports soon as well. We believe to meet all other requirements. == Statistics == As of Fri, 10 Jun 2011 the ASF installations check out a bit less than 180 source trees (115 from the ASF repository) and try to build a bit less than 800 projects. A complete Gump run takes about seven and a half hours on vmgump or the FreeBSD jail about six and a half hours on the MacOS X server where more projects fail to build and thus less time is spent building dependent projects. Some builds have been removed since the projects moved to the Attic (regexp, for example) or were unmaintained and always failed to build anyway. [1] the main instance at http://vmgump.apache.org/gump/public/ , a FreeBSD jail at http://gump.zones.apache.org/gump/public/ and a Mac OS X Server at http://adam.apache.org/gump/ - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
