Topics for podcast

[mrondina]

@GarthDB
I've been thinking about what topics might be interesting to discuss on the podcast. Here are some I've been kicking around.

• tools
• discussions from the project issues list
• best practices and resources to learn more or participate
• methods of open source design and forms it can take
• recent examples of open design
• license types for projects
• what to do when you can't - NDAs, classified projects, privacy

I'd like to expand this list as ideas come. I'm thinking discussions that are 30-40 minutes in length would be good.

[GarthDB]

Sweet.

I really like this - we should also put together a list of Some Easily Rebutted Objections like GNU's manifesto.

I'll put it in a separate comment, feel free to edit it.

[GarthDB]

• OSD is design by committee
• Designers can't collaborate on projects like developers
• You'll get terrible feedback that will be annoying to deal with
• Nobody will need/want the design
• the design will be inferior/compromised

[mrondina]

We could also discuss client objections and how to handle the approach to open design.

[GarthDB]

Yeah - add that to the list too if you come up with anything differently

[GarthDB]

@mrondina do you have the edit icon on the comments? You have privileges to edit right?

[mrondina]

It looks like I do. You want me to edit the comments or the original post

[GarthDB]

Edit my bulleted list to add more, or clarify.

[Skud]

I've been researching this topic for, oh, DAYS, and bookmarked a bajillion articles about design and open source. I've seen a pattern of myths propagated by non-designers in open source over this time:

• the main thing is to make a visible statement that you welcome designers ("We welcome designers!") -- yes, but this is FAR from enough
• a good way to attract designers is to solicit a logo design
• all "non-coders" have similar needs
• designers can/will use your existing collaboration tools if you just teach them (eg. painstakingly explain how to use github)
• design is only done by designers (who are separate people, almost mystical beasts)
• an open source project with a design team is an open source project with good design

... at least I assume these are myths.