Slashdot Mirror

← Back to Stories (view on slashdot.org)

Corporate Software Development Wiki?

Posted by Cliff on from the a-different-use-for-a-wiki dept.

gnujoshua asks: "My company would like to expand the use of its Wiki to include source code and API documentation. It would be nice to have auto-generated, syntax highlighted, and well documented source code, integrated nicely into the Wiki. Ideally, changes to source could be made right in the Wiki, barring permissions, and furthermore, it would be nice to see if it compiles against the library as well. What recommendations does Slashdot have for Wikis and scripts that could be used effectively to this end?"

1 of 79 comments (clear)

  1. Re:Reinventing the wheel? by halivar · · Score: 2, Insightful

    Or at least the (pick one) CVS, SourceSafe, or Sourceforge? Why must it be Wiki when there is a perfectly good ecosystem of software that ALREADY DOES THIS JOB?!?!?!?

    All the options you listed are for engineers only. If only engineers are involved in your design and development process, that's fine. For us, wiki is a great way to document our software development so that it is accessible not just to software developers, but also to documentation developers and tech support. It's great for this purpose because it is orders of magnitude easier to use than a source-versioning system (which is not anything at all like what you would use a wiki for). It's been a great boon to us, and I suggest other development teams look into using it, as well.