关于艺术品开发流程的问题
我们目前正在使用 SVN,并且我们将大部分艺术作品(声音、图像)与其他所有内容一起存储在我们的存储库中。现在,艺术家们将他们的作品直接提交到存储库。当艺术作品获得批准后,它就会链接到代码库。
我们希望保持结账过程简单(这样艺术品就不必单独安装/配置),但我们希望简化一个过程,使生成图像的艺术家可以将他们的作品提交到独立于主存储库的某个地方,并且获得批准后,将被放入主存储库中。我们希望让艺术家尽可能简单地进行操作,无需太多培训。
贵公司通常如何简化此流程?你用什么软件?
We are currently using SVN, and we are storing much of the artwork (sounds, images) in our repository right along with everything else. Right now, the artists commit their work to the repository directly. When the artwork is approved, it is linked to the codebase.
We want to keep the checkout process simple (so that artwork doesn't have to be installed/configured separately) but we would like to streamline a process where the artists who produce the images can submit their work somewhere independent of the main repository, and after it gets approved it is put into the main repository. We want to make it as simple for the artists as possible without much training.
How does your company typically go about streamlining this? What software do you use?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
我曾经合作过的团队过去所做的就是在 Subversion 中分解存储库。因此,举例来说:
然后,艺术团队仅检查美术分支并从中进行工作,而开发人员从项目分支中进行工作。一位艺术家(通常是领导者)有责任将完成的艺术作品签入项目下的“艺术”文件夹(或图像、或媒体等),以供开发人员使用。
虽然它不是自动化的,但我们发现它工作得很好,因为它分离了关注点,但仍然允许团队(最终)一起工作。
What teams I have worked with have done in the past is to break up the repository in Subversion. So, for example:
Then, the art team only checks out the artwork branch and works from that and the developers work from the project branch. It's the responsibility of one of the artists (the lead, typically) to check-in finished artwork to an 'art' folder (or images, or media, etc) underneath the project for use by the developers.
While it's not automated, we have found that it works pretty well because it separates the concerns, but still allows the teams to (ultimately) work together.
为艺术家建立一个单独的存储库,然后创建一个包含最新批准版本的“已批准”标签文件夹怎么样?然后可以通过 svn:externals 将该标签链接到您的主代码存储库。
How about having a seperate repository for the artists, and then a tag folder "approved" which contains the latest approved versions. This tag could then be linked by svn:externals to your main code repository.