mirror of
https://github.com/not-kennethreitz/convore.json.git
synced 2026-06-21 23:50:58 +00:00
1 line
1.7 KiB
JSON
1 line
1.7 KiB
JSON
[{"user_id": 8195, "stars": [], "topic_id": 37205, "date_created": 1306614230.2983849, "message": "Do you use GIT/SVN or any version control system?\nDo you archive them in some kind naming template?\nHow do you search/find for old PSD files?", "group_id": 629, "id": 1213866}, {"user_id": 30354, "stars": [], "topic_id": 37205, "date_created": 1306615302.2311871, "message": "Usually archive them by year, then by client. Name by revision. Windows Search seems to do the trick for me!", "group_id": 629, "id": 1213934}, {"user_id": 32775, "stars": [], "topic_id": 37205, "date_created": 1306673345.303858, "message": "Naming convention is key really, you wanna make sure to create a naming convention for your files. Besides this I do use SVN with cornerstone...versions is really good too.", "group_id": 629, "id": 1217275}, {"user_id": 30894, "stars": [{"date_created": 1312160215.4305329, "user_id": 38667}], "topic_id": 37205, "date_created": 1311987092.5677061, "message": "Based on an extended evaluation we did, we choose to go with Evolphin Zoom. See other threads in this group where similar issues were discussed by me. Our software guys were happy with GIT/SVN as these systems are really meant for source code with complex features like branching & branch management. At our company we have large Psd files for print - over 2GB and needed a system that could scale. We looked at everything out there and Evolphin Zoom was the better fit for us for 1) collaboration 2) lock management 3) performance & scalability 4) ease of use 5) Adobe CS integration 6) Mac Finder plugin. In future we are looking at automating our company's workflow and we liked their roadmap w.r.t marrying DAM with versioning and automated reviews.", "group_id": 629, "id": 1752002}] |