objarni's picture

OSS Check List

Hi!

I'm on a mailinglist and someone posted an Open Source Software Check List ... I thought it was fun and pragmatic, wanted to share it with you ...

1. Does the project scratch someone's itch?

2. Does the web site appeal to developers?

3. Does the web site appeal to users?

4. Is there an existing project that does what you want?

5. Is the goal of the project expressed clearly?

6. Did you choose a good name?

7. Does the project name suggest what the project does?

8. Is the project name easy to remember?

9. Is the project name the same as any other project's name?

10. Is the project name trademarked?

11. Is the project's name domain available, especially in the .ORG domain?

12. Does the project have a clear mission statement?

13. Is the mission statement concrete?

14. Is the mission statement limited?

15. Is the mission statement short?

13. Is the mission statement on the front page of the web site?

14. Is it unambiguously clear on the home page that the project is open source?

15. Does the home page list the features?

16. Does the home page list the requirements?

17. Does the home page list the development status?

18. Is the software downloadable as source code in standard formats?

19. Does the software conform to standard build methods?

20. Does the software conform to standard installation methods?

21. Does each release have a unique version number?

22. Does the project use version control?

23. Does the project use a bug tracker?

24. Does the project have a feature request tracker?

25. Does the project have a mailing list(s)?

26. Does the web site include how to join the mailing list(s)?

27. Does the project have an IRC channel?

28. Does the web site include information about the IRC channel?

29. Does the project have developer guidelines?

30. Do the developer guidelines include pointers to forums for
interaction with other developers?

31. Do the developer guidelines include instructions on how to report
bugs and submit patches?

32. Do the developer guidelines include some indication of how
development is usually done
(is the project a benevolent dictatorship, a democracy, or something else)?

33. Does the project have documentation?

34. Does the documentation include how to quickly set up the software?

35. Does the documentation include an overview of how it works?

36. Does the documentation include some guides to doing common tasks?

37. Does the documentation include how much technical expertise the
users expected to have?

38. Does the documentation list areas that are known to be incomplete?

39. Is the documentation available online?

40. Is the online documentation browseable?

41. Can you click on one link to bring up the entire documentation?

42. Is the documentation included with the software download?

43. Does the project have a Frequently Answered Questions (FAQ)?

44. Does the project have developer documentation?

45. Does the project have a wiki?

46. Are there screenshots on the web site?

47. What license does the project use?

48. Is the license listed on the home page with a link to the text?

49. Are project discussions private or public?

50. Is rudeness in project communications nipped in the bud?

51. Does the project have code reviews?

52. Are commit e-mails turned on?

53. Are you open sourcing an existing project?

54. If so, have you sent out a warning in advance?

55. Are new code releases announced on freshmeat.net?

56. Are new code releases announced on any mailing lists?

57. Are new code releases announced on any news groups?