This document discusses open source project stewardship and provides recommendations for maintaining a project after initial release. It emphasizes the importance of documentation like a README and LICENSE, as well as supporting users through mechanisms like a wiki, issue tracking, and community forums. Automated testing, contribution guidelines, and communication are also presented as important aspects of ongoing project maintenance and development. Links to additional resources on these topics are included.

1. Prelude

3. - (void)testLogInSucceedsWithUsernameAndPassword {
NSString *username = @"Jeff", *password = @"foo";
[_usernameField setText:username];
[_passwordField setText:password];
[_submitButton tap];
SLAssertTrueWithTimeout([_loginSpinner isInvalidOrInvisible], 3,
@"Log-in was not successful.");
NSString *successMessage = [NSString stringWithFormat:@"Hello, %@!", username];
SLAssertTrue([[SLElement elementWithAccessibilityLabel:successMessage] isValid],
@"Log-in did not succeed.");
}

5. —Objective-C tests
—No private APIs
—No dependencies
—Fully-tested

6. AFNetworking lets you
communicate with other
machines so you can
download images.

7. Subliminal lets you
manipulate your UI and
make assertions so you
can ???.

8. —491 stars
—45 watchers
—13 contributors

9. REPO MADNESS

10. http://nshipster.com/stewardship/
Earlier this year, Mattt Thompson wrote an essay on
open-source stewardship:
on launching an open-source project with your eyes
open to the responsibilities
that lie ahead.

11. It's not enough to dump a
pile of source code
somewhere and declare it
"open source".
— Mattt Thompson

12. ✓ README
✓ LICENSE
✓ Cocoapods

13. And then?

19. Hold on.

23. Braces keep existing
growth on track.

24. Braces support new
growth.

28. Braces for projects.

29. Braces support growth in...
—documentation
—user support
—development

30. Braces for
documentation.

36. README
READ FIRST

42. Braces for user support.

48. —If you need help, use Stack Overflow. (Tag
'subliminal'.)
—If you'd like to ask a general question, use Stack
Overflow.
—If you've found a bug, open an issue.
—If you have a feature request, open an issue.

49. Stack Overflow is the best place
for questions.

53. Get better issues with contributing
guidelines.

56. Braces for development.

57. Many hands
lighten the load.

58. In the contributing guidelines:
—How to set up development
—How to make changes
—How to document changes
—How to test changes

59. http://nshipster.com/unit-
testing/

60. Automated testing: as easy as
language: objective-c
xcode_project: MyNewProject.xcodeproj
xcode_scheme: MyNewProjectTests

62. Feature requests are
too late.

63. Separate problem
from solution.

64. Optimize for issues closed,
not PRs merged.

65. Communicate.

66. Say thanks.

68. Links
—http://nshipster.com/stewardship/
—https://github.com/blog/1828-wikis-now-with-
more-love
—http://stackoverflow.com/help/privileges/create-
tags
—https://github.com/blog/1184-contributing-
guidelines
—https://github.com/inkling/Subliminal/blob/
master/CONTRIBUTING.md

69. Links con't.
—http://docs.travis-ci.com/user/languages/
objective-c/
—https://github.com/inkling/Subliminal/wiki/
Continuous-Integration
—https://gitter.im/