Re: [Dynapi-Dev] Submitting patches (was Is this project dead?)

[Leif W <war...@us...>]

> "Andrew Gillett" <an...@zo...>; 2005-04-04@23:19 -0500
>
> Hi Fausto,
>
> Thanks for coming forward.
>
> You can submit bugs, patches, feature requests, etc. on the "trackers" 
> page:
>   http://sourceforge.net/tracker/?group_id=5757
>
> Items submitted to the tracker system have been ignored for a while 
> now, and that is one of the things we're trying to change.

Absolutely, 100%.  Please note that the trackers may continue to be 
ignored for a little while longer.  As admin, we're learning about all 
of the features that SourceForge makes available to projects.  And we're 
also trying to have discussions on the dynapi-admin list (open to all to 
subscribe, and open to subscribers for posting, at the very least during 
the reorganization process).  We need to assess the state of the website 
and other adimistrative tasks, and kind of develop some operating 
procedures.  So we need to research, identify, discuss, make decisions 
and prioritize what needs to be done on a project-wide scope, not just 
the code.

> If you're interested and you persist in helping, then CVS access can 
> be granted.

Also, we need to identify people's specific area(s) of interest and 
identify people who will make a committment to make themselves available 
to be assigned tasks, wether we post a task and a member volunteers, or 
we ask for members to volunteer even if it's not in their primary area 
of interest.  Or if you just want to test code and submit patches, that 
is great too.  But someone still needs to apply the patch to their local 
copy, review and commit them to CVS too.  If you go through all the 
trouble of identifying and fixing a bug, that's only a little more work 
to test it thoroughly, maybe ask others, and commit to the CVS tree. 
It's less work than to have someone like me who might be unfamiliar with 
that part of the code, or the problem, try to understand what is broke, 
apply the patch, re-test it, and then commit it.  That makes double work 
for the same result, so it takes twice as long.  There's a lot of work 
to be done and I know I can't do it all by myself which is why I'd want 
members I can count on who are receptive to the idea of being assigned 
tasks of any type, so long as they agree.  There's nobody forcing 
anything or assigning tasks without getting an OK from the member.  But 
if you're a member, then at the very least expect to be asked to do 
something like check the trackers regularly, check bug reports and test 
patches and submit code in the areas in which you have expressed 
interest.

Check the dynapi-admin mailing list archives, read the posts, and if you 
have ideas on those topics, by all means subscribe and speak up. 
Personally, I may have some good ideas, I may have some bad ideas, I 
can't know unless we have discussions with contributors, wether they are 
other admin, members, developers, or users.  Basically it's up to 
everyone to choose their level of involvement.

Leif

> Andrew
>
> Fausto wrote:
>
>>Hello guys,
>>
>>I've been using DynAPI for about 1 year now and I am very happy to see 
>>this
>>project is again moving along.  Can I be of some help in development?
>>
>>I changed many places in DynAPI to make it work and I am also good 
>>with
>>javaScript and Java.
>>
>>Any directions would be wonderfull.
>>
>>Fausto.
>>
>
>
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real 
> users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://www.mail-archive.com/dyn...@li.../
>
>