Re: [ubuntu-art] Workflow management

2006-09-11 Thread Matthew Nuzum
Michiel Sikma wrote:
 MediaWiki keeps revision histories of _everything_, including images.  
 You can jump back to old revisions of images for comparison.
 
 Not that this makes it a perfect CMS for artwork collaboration,  
 though...

I've looked into this quite a bit in the past. It's a very difficult
thing to find. Most DMS (document management systems) target very
high-end users who need to manage documents/media for 50 years. Popular
with the likes of Boeing and NASA and Phizor etc.

There was a brief conversation on the matter in IRC. A product was
suggested a while back which used Drupal with the Gallery2 plugin. For
our needs, this is fundamentally no different than gallery2 on its own,
since we don't need CMS features (just image colaboration because wiki
provides avenue for content).

The Gallery2 project is foss, mature and very active. The only thing it
doesn't provide is versioning for images, but its plugin system is very
powerful and this could be added.

The installation is easy, and I've got it setup. However the server is
having a problem because of a reverse DNS issue (e-mails are being
selective ignored by strict mail servers).

Here's the gallery2 main website: http://gallery.menalto.com  Here's
where I've placed my quick test: http://art-staging.ubuntu.com/gallery2

I've used and hacked gallery for years, but I'll admit, this newer
version has added a lot of stuff and I've not got it all figured out yet.

If there are a few enterprising souls out there who want to try it out,
please, be my guest. I'm working on the rdns/mailserver issue now. If it
turns out gallery2 isn't suitable, we'll trash it and find something
better. But since its free and we have the server all ready, might as
well give it a try.
-- 
Matthew Nuzum
newz2000 on freenode

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Workflow management

2006-09-10 Thread Nathan Eckenrode
Would a branch or a fork be the same thing as starting a new thread? Perhaps 
then there can be an adaptation in the site's presentation that groups all 
threads for the same app together, and if there is a thread that is 
derivative from another then that could be presented sequentially.

On Saturday 09 September 2006 15:57, Jan Claeys wrote:
 Op do, 07-09-2006 te 08:15 -0400, schreef Nathan Eckenrode:
  There is some interesting work happening over here at
  http://kollabor8.toegristle.com/ I am not certain of the software
  which is being used , but I think that this is the sort of idea that
  you are looking for.

 It seems like this site doesn't support branches (or forks) ?
 Wouldn't that be needed?


 --
 Jan Claeys


pgpE5L1QZiX1m.pgp
Description: PGP signature
-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Workflow management

2006-09-10 Thread Chuck Huber
Jan, I'm resending this.  I meant to cc the group yesterday...

On Sat, 2006-09-09 at 21:57 +0200, Jan Claeys wrote:
 Op do, 07-09-2006 te 08:15 -0400, schreef Nathan Eckenrode:
  There is some interesting work happening over here at 
  http://kollabor8.toegristle.com/ I am not certain of the software
  which is being used , but I think that this is the sort of idea that
  you are looking for. 
 
 It seems like this site doesn't support branches (or forks) ?
 Wouldn't that be needed?
 
 
 -- 
 Jan Claeys
Yeah,  I think Mark has some ideas that he'd like to see implemented
before it's considered optimal.  Kollabor8 just seems like a good
starting point.

Ideally it would be a cvs, svn, or bzr backend with an image gallery
interface and wiki style content management system.  

It's the backend where I see problems arising.  Since the image data is
entirely binary and not text based, there is probably no way to just
save changes like cvs would do.  Because of this the database is going
to grow large quickly and will ultimately slow down.  

Now it may not be realistic in the near term but if the tool could read
certain file formats we could get around some of this bloat.  Say it
understood xcf files... new versions of those files would be based on
the original xcf, with only information for missing layers and edited
layers uploaded.  Then we would be getting close to a true version
control system for images.  Over time, the system could be expanded to
understand and use many of the more open image formats.

That would be awesome.  Just think how popular cvs is...
-- 
Chuck Huber [EMAIL PROTECTED]


-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Workflow management

2006-09-09 Thread Jan Claeys
Op do, 07-09-2006 te 08:15 -0400, schreef Nathan Eckenrode:
 There is some interesting work happening over here at 
 http://kollabor8.toegristle.com/ I am not certain of the software
 which is being used , but I think that this is the sort of idea that
 you are looking for. 

It seems like this site doesn't support branches (or forks) ?
Wouldn't that be needed?


-- 
Jan Claeys


-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Workflow management

2006-09-08 Thread Who
On 9/8/06, Troy James Sobotka [EMAIL PROTECTED] wrote:
 On Thu, 2006-07-09 at 12:43 -0400, Nathan Eckenrode wrote:
  Perhaps this is not what people are looking for to streamline the
 process, but
  it makes sense to me that if the developers of code base have a cvs
 to
  maintain code, then the developers of the distribution's artwork needs
 a
  system which allows the artists to compare the changes to a piece of
 art in a
  visual manner and make decisions on which to make collaborative
  contributions.

 I think you are on the money.  This is exactly the
 kind of tool we require.  The process needs to show a
 more evolutionary progression.  Diverse artwork in a
 plethora of different styles / looks isn't that useful
 to a product that seeks a more polished look.

 I believe imbrandon has something mocked up with a
 Drupal based CMS, but perhaps he could chime in here
 and offer up what he has done.


I agree too - I am forever making huge contact sheets of my work for
posting to the wiki so that the evolution is clear and peopel can
comment on different stages of the process. A usefull system for me
would be the ability to sumit many versions of a specific piece of
work, have it tile them, make a slideshow, order them and allow each
individual one to be commented on and discussed...

Jono Bacon had some thoughts about making it easier for creative
people to contribute:
http://www.jonobacon.org/?p=740

Who

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Workflow management

2006-09-08 Thread Michiel Sikma

Op 7-sep-2006, om 18:43 heeft Nathan Eckenrode het volgende geschreven:

 I am not certain I see how Mediawiki is better at allowing one to  
 see the
 progression of work that has been done on artwork. It appears to be  
 the same
 solution that is currently in place, a wiki. i certainly can be  
 wrong in this
 aspect, it will not be the first time nor the last time.

MediaWiki keeps revision histories of _everything_, including images.  
You can jump back to old revisions of images for comparison.

Not that this makes it a perfect CMS for artwork collaboration,  
though...

Michiel

-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Workflow management

2006-09-07 Thread Nathan Eckenrode
On Thursday 07 September 2006 12:08, PingunZ wrote:
 ubuntuguide.org
I am not certain I see how Mediawiki is better at allowing one to see the 
progression of work that has been done on artwork. It appears to be the same 
solution that is currently in place, a wiki. i certainly can be wrong in this 
aspect, it will not be the first time nor the last time.

The solution which is demonstrated at kollabor8 has images which you check out 
and alter and then upload the new version, very similiar to version control 
for code except demonstrates the visual changes in the item. 

Perhaps this is not what people are looking for to streamline the process, but 
it makes sense to me that if the developers of code base have a cvs to 
maintain code, then the developers of the distribution's artwork needs a 
system which allows the artists to compare the changes to a piece of art in a 
visual manner and make decisions on which to make collaborative 
contributions. 

Still, I retain the right to be wrong and will try to accept it if I am.


pgp7zR19PIKBT.pgp
Description: PGP signature
-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art


Re: [ubuntu-art] Workflow management

2006-09-07 Thread Mark Shuttleworth




Nathan Eckenrode wrote:

  There is some interesting work happening over here at 
http://kollabor8.toegristle.com/ I am not certain of the software which is 
being used , but I think that this is the sort of idea that you are looking 
for.

Yes, this is very close to what I want! I tihnk we need a couple more
features. I'll contact these guys and see if they are interested in
helping out.

Mark


-- 
ubuntu-art mailing list
ubuntu-art@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-art