I think having you on the call tmrw would be really great Jukka. We
definitely won't be using SVN as the primary dev src (but its fine if
it has to act as canonical release src).

Getting this workflow sorted w/ your guidance would be very much appreciated!!

Call is tmrw at 11am details below:

1.  Please join my meeting, 2011-10-20 at 11:00 AM.
https://www1.gotomeeting.com/join/352481768

2.  Use your microphone and speakers (VoIP) - a headset is
recommended. Or, call in using your telephone.

Dial +1 (416) 900-1164
Access Code: 352-481-768
Audio PIN: Shown after joining the meeting

Meeting ID: 352-481-768




On Wed, Oct 19, 2011 at 4:39 PM, Jukka Zitting <[email protected]> wrote:
> Hi,
>
> On Thu, Oct 20, 2011 at 1:17 AM, Brian LeRoux <[email protected]> wrote:
>> Hey Jukka, so what should our process for contribution look like precisely?
>
> That depends mostly on how you want to organize things. The common way
> for Apache projects is to direct all contributions to the issue
> tracker, where proposed patches (or pull requests) are discussed
> before one of the project committers commits them.
>
>> I'd like to propose we:
>>
>> 1. update the github.com/phonegap/[PROJECT NAME] w/ a single README.md
>> document that has links to the Apache mirrors on Github and encourages
>> contributers on GH to send pull req's there
>
> Pull requests sent at the Apache mirrors on Github will automatically
> be forwarded to dev@, from where we can pick them up. As noted above,
> I'd also recommend pointing people to the Callback Jira to file issues
> to go with all pull requests or patches they contribute.
>
>> 2. nominate platform developers to ensure the mirrors are in sync w/
>> the mainlines on apache.org
>
> If you're referring to the Git mirrors at github.com/apache, they are
> automatically kept up to date with the latest changes in Subversion.
>
>> we're having a team call tmrw morning so we can talk about this then
>
> If you like, I'd be happy to join the call to answer any questions
> about Apache processes and infrastructure.
>
> BR,
>
> Jukka Zitting
>

Reply via email to