Please create an account to participate in the Slashdot moderation system


Forgot your password?

Submission Summary: 0 pending, 5 declined, 2 accepted (7 total, 28.57% accepted)

DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Submission + - Simple versioning share drive for Windows? 1

maiden_taiwan writes: My company's documents are stored on a big Windows share drive. We'd like to install a simple versioning system to track document history and roll back to previous versions when needed. Unfortunately, our needs are too simple for the marketplace, which pushes Documentum, SharePoint, and other massive, expensive systems that want to "be in charge" and change everybody's work habits. All we want is a simple Windows share drive (CIFS, not WebDAV, which rules out Subversion with autoversioning) that automatically versions documents when saved or on request, scales internationally to thousands of users, and doesn't cost half a million dollars. Is there really nothing out there for Windows? What does your company use?

Submission + - Getting a development group to adopt a standard?

maiden_taiwan writes: "At my software company, we occasionally need all engineers to adopt a new standard or "best practice." Some are small, like the use of Camel Case for function names, while others have tangible business value, such as "every check-in must be accompanied by a unit test." As you might guess, some new practices get ignored, not because people are evil or lazy, but because they're simply too busy to pay attention and change their work habits. So we are seeking creative ways to announce, roll out, and enforce a standard for 100+ engineers so they will actually follow it. We already know to automate compliance when possible (e.g., the revision control system could reject check-ins without unit tests), and simple platitudes like "tie compliance to their year-end bonuses" aren't helpful by themselves, as someone will still need to check compliance. The engineers here are smart people, so we want to spend less time on enforcement (having architects read the code and flag any nonstandardisms) and more on evangelization (getting engineers to see the benefits of the standards and want to follow them). I'd welcome any advice on formal processes or just plain fun ways to get people's attention."

Slashdot Top Deals

Did you know that for the price of a 280-Z you can buy two Z-80's? -- P.J. Plauger