What's the status of this work? Do we have a config file for framework.swc yet 
that I can use in a Falcon JUnit test? If so, I'd like to get it checked in 
even if we don't switch over the build.xml file yet to use it.

- Gordon


-----Original Message-----
From: Chema Balsas [mailto:jbal...@gmail.com] 
Sent: Tuesday, October 23, 2012 11:45 AM
To: flex-dev@incubator.apache.org
Subject: Re: compc config adjustements (was RE: ASC 2.0 and Falcon)

Sorry if I made a bit of a mess here...

I think the wiki sounds good, but we'll probably be adding more complexity to 
the workflow.

Mike, if you are allowed to assign the tasks to yourself, I'd suggest that we 
create the subtasks. You or any other committer that wants to work on one, just 
needs to assign it to himself. For the rest of us, we can just comment on the 
task saying that we're taking over and that should do it.

Does that sound reasonable? What do you think?

Thanks everyone for the input!

2012/10/23 Michael Schmalle <apa...@teotigraphix.com>

> Well ironically after sending the last message it finally(4 hours 
> later after man tries) downloaded all build stuff, thanks for the info Carol.
>
> Mike
>
>
> Quoting Carol Frampton <cfram...@adobe.com>:
>
>
>>
>> On 10/23/12 11 :39AM, "Michael Schmalle" <apa...@teotigraphix.com> wrote:
>>
>>  Quoting Om <bigosma...@gmail.com>:
>>>
>>>  I believe Alex can help you with setting up your JIRA account to be
>>>> able to
>>>> assign stuff to yourself.
>>>>
>>>
>>> This isn't a problem, I can do this already.
>>>
>>>  As for non-committers, a comment saying 'I am on it'  should be
>>>> sufficient.  Regularly updating tasks/sub-tasks with progress 
>>>> updates would also be helpful in case someone else wants to 
>>>> continue from where things are.
>>>>
>>>> This is an issue I struggled with at the beginning as well.  It 
>>>> became easier as I got used to the process  and stuck to it.
>>>>
>>>> Take a look at FLEX-33106 for an example of how multiple developers 
>>>> worked together by creating sub tasks and posting regular progress 
>>>> updates.
>>>>
>>>
>>>
>>> Yeah I see you have sub tasks and a lot of dialog back and forth.
>>>
>>> I can't even get the framework to build because of the osmf not 
>>> downloading, just one of those days.
>>>
>>
>> Download it from here:
>>
>> http://sourceforge.net/**projects/osmf.adobe/<http://sourceforge.net/
>> projects/osmf.adobe/>
>>
>>
>> extract osmf.swc and put it in {root}/framework/libs
>>
>> The build file will see it is there and not try to download it.
>>
>> Carol
>>
>>
>>> Mike
>>>
>>>  Thanks,
>>>> Om
>>>> On Oct 23, 2012 8:16 AM, "Michael Schmalle" 
>>>> <apa...@teotigraphix.com>
>>>> wrote:
>>>>
>>>>  Quoting Carol Frampton <cfram...@adobe.com>:
>>>>>
>>>>>
>>>>>
>>>>>  I don't have permission as a committer? I created the task and
>>>>>>> assigned it to myself, am I missing something? I know I can't 
>>>>>>> assign a task to Chema since he is not a listed user.
>>>>>>>
>>>>>>>
>>>>>> If it wasn't you then it was Chema that said he couldn't can't 
>>>>>> assign a task.  If he is one of the people working on this how is 
>>>>>> he suppose to indicate this if he can't assign the task to 
>>>>>> himself?
>>>>>>
>>>>>> At this point I'm staying out of this.  You guys can figure out 
>>>>>> how you want to do it.  I was just trying to help but I only seem 
>>>>>> to have complicated matters.
>>>>>>
>>>>>>
>>>>>
>>>>> No, I'm listening to what you are saying, and your not 
>>>>> complicating things. :)
>>>>>
>>>>> I'm new to this stuff to be honest and I'm just looking for a 
>>>>> little guidance.
>>>>>
>>>>> Chema wanted to help, so he went ahead and tried to find all the 
>>>>> files that needed to be updated.
>>>>>
>>>>> He then just tired to create sub tasks himself to organize the effort.
>>>>> I
>>>>> think he didn't realize he couldn't assign tasks to himself.
>>>>>
>>>>> So I think the question is how actually a committer and 
>>>>> contributor can work on something together as large as this task 
>>>>> is and communicate to each other what the other is doing so we 
>>>>> don't duplicate work.
>>>>>
>>>>> Mike
>>>>>
>>>>> --
>>>>> Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com 
>>>>> http://blog.teotigraphix.com
>>>>>
>>>>>
>>>>>
>>>>
>>> --
>>> Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com 
>>> http://blog.teotigraphix.com
>>>
>>>
>>
>>
> --
> Michael Schmalle - Teoti Graphix, LLC
> http://www.teotigraphix.com
> http://blog.teotigraphix.com
>
>


--
Chema

Reply via email to