On Mon, May 08, 2017 at 07:29:17PM -0700, Alyssa Rosenzweig wrote:
> As per a discussion with wolftune.
> ---
>  community/team-engagement.page | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/community/team-engagement.page b/community/team-engagement.page
> index 804fac9..890d1a6 100644
> --- a/community/team-engagement.page
> +++ b/community/team-engagement.page
> @@ -56,6 +56,16 @@ Organizations need some meetings, and when run well, they 
> can produce powerful r
>  * To set major priorities, especially for the long term
>  * To conduct project post-mortems in order to reflect on what succeeded and 
> what needs improvement
>  
> +## Starting a project
> +
> +* Be social. Talk to your friends about your project. Talk to their friends 
> about it. Talk about it in public IRC channels. Post about it on Reddit. It's 
> okay if it's not "ready" yet -- just get the word out and find people 
> interested.
> +* Get people involved. See the rest of this document for help here.
> +* Make it a community effort. It isn't *your* project; it's *our* project. 
> Let your new contributors have a say in the direction.
> +* If they've earned it, give people titles. Titles are fun and motivating, 
> and they don't cost you anything. Don't give them out recklessly, but if 
> people start accumulating real responsibilities, let them now! Titles are an 
> honour in FLO projects.
> +* Ask for help. Even if you do all the work for the project itself, reaching 
> out to advisors can be helpful in finding direction. Maybe someone in 
> `#snowdrift` can help bounce ideas off.
> +* If you can, a co-founder is even better.
> +* Open it out of your circle. It's one thing to build a project that appeals 
> to enthusiasts. It's another to make it appeal to non-enthusiasts. You'll 
> never please everybody, but you can always broaden your project's domain.
> +
>  ## Resources
>  
>  * [OpenHatch](http://openhatch.org) helps new volunteers get involved in FLO 
> software development
> -- 
> 2.11.0

Thanks. I see this has been merged already, but definitely feel welcome
to submit patches like this. :)

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Dev mailing list
Dev@lists.snowdrift.coop
https://lists.snowdrift.coop/mailman/listinfo/dev

Reply via email to