Hi Everett,

Sorry about the long delay. I went to find you the information and realized 
that we didn't have a single page that captured all of it adequately.

We've written a new wiki page about contributing, that I hope will provide all 
of the necessary information.

http://wiki.fluidproject.org/display/fluid/Contributing+Code

Thanks for the help, looking forward to seeing your patches.
Justin

On 2010-08-11, at 8:47 AM, E.J. Zufelt wrote:

> Thanks,
> 
> And can you please give me a URL to where I can find information on 
> contributing patches?  I've never patched anything in the Fluid world and 
> have no idea what you use for version control, or how branching works or what 
> branch to develop a patch against.
> 
> Thanks,
> Everett Zufelt
> http://zufelt.ca
> 
> Follow me on Twitter
> http://twitter.com/ezufelt
> 
> View my LinkedIn Profile
> http://www.linkedin.com/in/ezufelt
> 
> 
> 
> On 2010-08-11, at 8:18 AM, Justin Obara wrote:
> 
>> Hi Everett,
>> 
>> I agree, it is a good idea to have a url provided. It keeps track of and 
>> makes explicit where the issue was found. I think in this case, since this 
>> was filed during a bit of a testing sprint, that it was probably just missed 
>> when filling out the jira. Thanks for alerting us to this.
>> 
>> I believe the correct url for the Progress Component demo that was tested is 
>>  http://build.fluidproject.org/infusion/demos/progress/html/progress.html 
>> 
>> I've cc'd Jan here so that he can confirm it, and made a comment on the jira 
>> itself as well.
>> 
>> Thanks
>> Justin
>> 
>> On 2010-08-11, at 6:05 AM, E.J. Zufelt wrote:
>> 
>>> Good morning,
>>> 
>>> I was taking a look at issues in JIRA this morning (a chore with a 
>>> screen-reader), and I came across a progress bar issue:
>>> 
>>> http://issues.fluidproject.org/browse/FLUID-3671
>>> 
>>> The comments on testing were useful, but there was no information, that I 
>>> could find, showing a URL for any example page where the testing was 
>>> performed.  This makes it quite difficult to retest and confirm the posted 
>>> results.
>>> 
>>> In this situation is it safe for me to assume that the problem is always 
>>> experienced with the progress component, regardless of implementation, or 
>>> is it likely that the information was just not posted to the JIRA?  Having 
>>> a URL provided for issues would be useful for future testing and 
>>> troubleshooting.
>>> 
>>> Thanks,
>>> Everett Zufelt
>>> http://zufelt.ca
>>> 
>>> Follow me on Twitter
>>> http://twitter.com/ezufelt
>>> 
>>> View my LinkedIn Profile
>>> http://www.linkedin.com/in/ezufelt
>>> 
>>> 
>>> 
>>> _______________________________________________________
>>> fluid-work mailing list - [email protected]
>>> To unsubscribe, change settings or access archives,
>>> see http://fluidproject.org/mailman/listinfo/fluid-work
>> 
> 

_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work

Reply via email to