Bringing this conversation full circle...
One important thing I think some folks are missing about the standards argument is that no one is suggesting the OSS be legislated to use any given standard. As folks have mentioned, that flys in the face of the OSS ethos.
If lone devs want to work in isolation, then have at it. Some of the most brilliant men in history have worked as hermits. This discussion is not about making the lone wolf feel like he should "get with the program".
Rather, the discussion focuses on making things simpler for teams of OS devs. THe Team for Product X requires standards against which they should develop, else none of the code will fit together. We all naturally do this when working in a team.
All that is being suggested is that Standards are required for Team X and Team Y and Team Z to connect their individual products in meaningful ways while not reniventing the wheel.
If your product can or should operate in complete isolation, don't adopt the standards. No harm, no foul.
(there is no such thing as an Open Source Artist people)
Don't agree with that. There are plenty of folks who are willing to contribute non-coding talents (artwork, UI design, documentation, etc.). I know,I've worked with them. Just checkout
Xaraya.com. We put out a call for a logo and got back over 50 original designs. We have theme designers lining up to learn to use Block Layout. And, we have talented writers in line to help with documentation.
If you are willing to work with people, they are generally willing to work with you.
Slashdot Mirror
LMAO
Mr. Gaiman,
Thanks for your blog and taking the time to anser questions here.
Regards,
Doug Daulton
Bringing this conversation full circle ...
One important thing I think some folks are missing about the standards argument is that no one is suggesting the OSS be legislated to use any given standard. As folks have mentioned, that flys in the face of the OSS ethos.
If lone devs want to work in isolation, then have at it. Some of the most brilliant men in history have worked as hermits. This discussion is not about making the lone wolf feel like he should "get with the program".
Rather, the discussion focuses on making things simpler for teams of OS devs. THe Team for Product X requires standards against which they should develop, else none of the code will fit together. We all naturally do this when working in a team.
All that is being suggested is that Standards are required for Team X and Team Y and Team Z to connect their individual products in meaningful ways while not reniventing the wheel.
If your product can or should operate in complete isolation, don't adopt the standards. No harm, no foul.