[jira] Updated: (GUMP-29) new user howto
[ http://issues.apache.org/jira/browse/GUMP-29?page=all ] Leo Simons updated GUMP-29: --- Fix Version: Gump3-alpha-6 (was: Gump3-alpha-5) Description: New users seem weary of editing gump descriptors (especially when they don't live in their own cvs module but they have to change things in the gump repository), and most of them are very sketchy as to the steps one takes to fix things. Niclas Hedhman' recent experience in getting some of avalon to build using gump and the talk resulting from it on avalon-dev and gump-general are a good example of a new user we need to talk through things. We need a howto. Not just the technical explanation, but some philosophy (Everyone is free to work on gump. Everyone. Stuff like that) intertwined. was: New users seem weary of editing gump descriptors (especially when they don't live in their own cvs module but they have to change things in the gump repository), and most of them are very sketchy as to the steps one takes to fix things. Niclas Hedhman' recent experience in getting some of avalon to build using gump and the talk resulting from it on avalon-dev and gump-general are a good example of a new user we need to talk through things. We need a howto. Not just the technical explanation, but some philosophy (Everyone is free to work on gump. Everyone. Stuff like that) intertwined. Version: Gump3-alpha-6 (was: Gump3-alpha-5) (was: Gump3-alpha-4) Environment: bump. new user howto -- Key: GUMP-29 URL: http://issues.apache.org/jira/browse/GUMP-29 Project: Gump Type: Improvement Components: Documentation Versions: Gump3-alpha-6 Reporter: Leo Simons Fix For: Gump3-alpha-6 New users seem weary of editing gump descriptors (especially when they don't live in their own cvs module but they have to change things in the gump repository), and most of them are very sketchy as to the steps one takes to fix things. Niclas Hedhman' recent experience in getting some of avalon to build using gump and the talk resulting from it on avalon-dev and gump-general are a good example of a new user we need to talk through things. We need a howto. Not just the technical explanation, but some philosophy (Everyone is free to work on gump. Everyone. Stuff like that) intertwined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-29) new user howto
[ http://issues.apache.org/jira/browse/GUMP-29?page=history ] Leo Simons updated GUMP-29: --- Version: unspecified new user howto -- Key: GUMP-29 URL: http://issues.apache.org/jira/browse/GUMP-29 Project: Gump Type: Improvement Components: Documentation Versions: Gump3-beta, Gump3-alpha Reporter: Leo Simons Assignee: Leo Simons Fix For: Gump3-beta New users seem weary of editing gump descriptors (especially when they don't live in their own cvs module but they have to change things in the gump repository), and most of them are very sketchy as to the steps one takes to fix things. Niclas Hedhman' recent experience in getting some of avalon to build using gump and the talk resulting from it on avalon-dev and gump-general are a good example of a new user we need to talk through things. We need a howto. Not just the technical explanation, but some philosophy (Everyone is free to work on gump. Everyone. Stuff like that) intertwined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-29) new user howto
[ http://issues.apache.org/jira/browse/GUMP-29?page=history ] Leo Simons updated GUMP-29: --- Version: Gump3-beta new user howto -- Key: GUMP-29 URL: http://issues.apache.org/jira/browse/GUMP-29 Project: Gump Type: Improvement Components: Documentation Versions: Gump3-beta, Gump3-alpha Reporter: Leo Simons Fix For: Gump3-beta New users seem weary of editing gump descriptors (especially when they don't live in their own cvs module but they have to change things in the gump repository), and most of them are very sketchy as to the steps one takes to fix things. Niclas Hedhman' recent experience in getting some of avalon to build using gump and the talk resulting from it on avalon-dev and gump-general are a good example of a new user we need to talk through things. We need a howto. Not just the technical explanation, but some philosophy (Everyone is free to work on gump. Everyone. Stuff like that) intertwined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-29) new user howto
[ http://issues.apache.org/jira/browse/GUMP-29?page=history ] Leo Simons updated GUMP-29: --- Assign To: (was: Leo Simons) Version: Gump3-alpha (was: unspecified) Fix Version: Gump3-beta (was: unspecified) new user howto -- Key: GUMP-29 URL: http://issues.apache.org/jira/browse/GUMP-29 Project: Gump Type: Improvement Components: Documentation Versions: Gump3-beta, Gump3-alpha Reporter: Leo Simons Fix For: Gump3-beta New users seem weary of editing gump descriptors (especially when they don't live in their own cvs module but they have to change things in the gump repository), and most of them are very sketchy as to the steps one takes to fix things. Niclas Hedhman' recent experience in getting some of avalon to build using gump and the talk resulting from it on avalon-dev and gump-general are a good example of a new user we need to talk through things. We need a howto. Not just the technical explanation, but some philosophy (Everyone is free to work on gump. Everyone. Stuff like that) intertwined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (GUMP-29) new user howto
[ http://issues.apache.org/jira/browse/GUMP-29?page=history ] Leo Simons updated GUMP-29: --- Version: (was: unspecified) new user howto -- Key: GUMP-29 URL: http://issues.apache.org/jira/browse/GUMP-29 Project: Gump Type: Improvement Components: Documentation Reporter: Leo Simons Assignee: Leo Simons Fix For: unspecified New users seem weary of editing gump descriptors (especially when they don't live in their own cvs module but they have to change things in the gump repository), and most of them are very sketchy as to the steps one takes to fix things. Niclas Hedhman' recent experience in getting some of avalon to build using gump and the talk resulting from it on avalon-dev and gump-general are a good example of a new user we need to talk through things. We need a howto. Not just the technical explanation, but some philosophy (Everyone is free to work on gump. Everyone. Stuff like that) intertwined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
