Good to know, I was just commenting on Denis' request to let you know ahead 
of time so we could be briefed on your process.

I still think a readme explaining that you welcome contributions and 
certainly mentioning the copyright language would be helpful, especially 
given Github's automatic rendering of readme files and how they act as a 
pseudo-"home page" for the repository.  Might help introduce the framework 
to new users exploring.

Just my two cents.

On Monday, October 28, 2013 10:48:56 PM UTC-4, Geoff Bowers wrote:
>
> Sean,
>
> On 23 October 2013 00:09, Sean Coyne <[email protected] <javascript:>>wrote:
>
>> Might I suggest adding a README explaining the process for pull requests? 
>>  Might help encourage others to provide bug fixes and enhancements.
>>
>  
> I don't believe there's any specific procedure beyond github's standard 
> recommendations:
>   https://help.github.com/articles/using-pull-requests
>
> The only caveat is that all submissions must continue to cede copyright to 
> "Daemon Pty Limited", the corporate custodian of the code base.
>
> Simple "pulls" will go through almost immediately.  More complex stuff 
> might spark a bit of discussion on the pull request itself, prior to going 
> into the code base.
>
> Fork now! Pull at will ;)
>
> GB
>

-- 
You received this message cos you are subscribed to "farcry-dev" Google group.
To post, email: [email protected]
To unsubscribe, email: [email protected]
For more options: http://groups.google.com/group/farcry-dev
--------------------------------
Follow us on Twitter: http://twitter.com/farcry
--- 
You received this message because you are subscribed to the Google Groups 
"farcry-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to