Re: TMDA x Debian X python 2.5.x

On Tue, Mar 8, 2011 at 10:25 AM, Jason R. Mastaler <[email protected]> wrote:
> Kevin,
>
> Have you considered applying your changes to the main TMDA codebase
> rather than maintaining a "fork?" That's sort of the point of
> opensource projects -- that while maintainers ebb and flow, the
> project can still continue through global contribution and new
> commitment. TMDA is setup for this being hosted on sourceforge, etc.

Of course. I personally dislike sourceforge, and would want to keep my
github fork as long as I have an interest in it, but there's no reason
that changes couldn't or shouldn't be merged upstream. There are a few
issues, mostly due to my perhaps overly zealous co-opting of the code. I
kind of started with the assumption that merging wouldn't be an option,
as the project appeared to be dead. Therefore I didn't hesitate to make
wide-spread purely stylistic changes, which make merging difficult.

I don't think any merging can reasonably take place until I review the
changes and determine what is appropriate for merging and what may not
be. I'll be in touch when I have an opportunity to start creating
coherent patch sets appropriate for upstream application.

-Kevin

------------------------------------------------------------------------------
What You Don't Know About Data Connectivity CAN Hurt You
This paper provides an overview of data connectivity, details
its effect on application quality, and explores various alternative
solutions. http://p.sf.net/sfu/progress-d2d
_______________________________________________
tmda-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tmda-users