xmlvm-users

[xmlvm-users] Monster patches and GPL linking exception

[Dr. A. K. S. <al...@se...>]

Hi,

I've also submitted "monster" patches in the past. The problem is
that XMLVM is evolving so fast that it is a major effort to resync
the patches, and in some cases it is not possible (e.g. the old way
to localize strings is not compatible with the new way, I had to
reimplement it basically from scratch). So I don't think it makes
sense to submit monster patches anymore, but rather self-contained
parts with significant functionality.

Currently it works like that: Wolfgang, Arno or Sascha ask me about
a specific functionality (currently it's audio recording), and I
resync that part of my code with SVN head, polish it, beat out the
memory management bugs and submit it. IMHO that is a better way to
go than monster patches because it allows the XMLVM team to pace the
development and do the things in the right order as they make sense.
A lot of ways to fix things are ad-hoc and not really useful for
anyone else (e.g. the way I've implemented ProgressDialog.. :->>)

I personally won't go away for a long time from my r953-synchronized
private patch set which allows me to cross-compile my app with a minimum
of hassle... which is what XMLVM is about for me.

Best,
  Alex
-- 
Dr. Alexander K. Seewald

Seewald Solutions
www.seewald.at
Tel. +43(664)1106886
Fax. +43(1)2533033/2764

Re: [xmlvm-users] Monster patches and GPL linking exception

[Panayotis K. <pan...@pa...>]

On 18 Μαρ 2010, at 6:15 ΜΜ, Dr. Alexander K. Seewald wrote:

...

> Currently it works like that: Wolfgang, Arno or Sascha ask me about
> a specific functionality (currently it's audio recording), and I

....
right, that's the key point:
they "asked" you :)


I know that it really is difficult to handle, but (as I said in  
previous posts), it is expected for a new project to have patches like  
these.

Of course if such patch is not desirable, I could take it back and  
send, for example, only UIViewContoller, then tomorrow another object,  
and so forth :)
But I believe the total effort then will be much much larger than now,  
since this whole patch has a common logic which at the end of the day  
will make evaluating it easier than to send one file at a time.
Maybe it might seem too difficult, but it would be easier than to  
"divide and conquer" :)

Re: [xmlvm-users] Monster patches and GPL linking exception

[Wolfgang K. <wol...@xm...>]

I think I have to correct a little bit. Actually we did not ask for a  
particular functionality. In fact we asked for some corrections/ 
rewritings after reviewing patches. Some of that was necessary due to  
the integration of other patches. And that boils down to the problem  
of concurrent patches, which is being discussed.

-- Wolfgang

Sent from my iPhone

On 18.03.2010, at 17:49, Panayotis Katsaloulis  
<pan...@pa...> wrote:

>
> On 18 Μαρ 2010, at 6:15 ΜΜ, Dr. Alexander K. Seewald wrote:
>
> ...
>
>> Currently it works like that: Wolfgang, Arno or Sascha ask me about
>> a specific functionality (currently it's audio recording), and I
>
> ....
> right, that's the key point:
> they "asked" you :)
>
>
> I know that it really is difficult to handle, but (as I said in
> previous posts), it is expected for a new project to have patches like
> these.
>
> Of course if such patch is not desirable, I could take it back and
> send, for example, only UIViewContoller, then tomorrow another object,
> and so forth :)
> But I believe the total effort then will be much much larger than now,
> since this whole patch has a common logic which at the end of the day
> will make evaluating it easier than to send one file at a time.
> Maybe it might seem too difficult, but it would be easier than to
> "divide and conquer" :)
>
>
> --- 
> --- 
> --- 
> ---------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] Monster patches and GPL linking exception

[Gergely K. <ger...@ma...>]

Hi,

I think the solution for this is to communicate more on the mailing list, to
lay down the technical directions of the project. Right now everyone is
developing privately, then throws patches "over the wall". If we discussed
the approaches on the mailing list, then each of us would make less
duplicated efforts.

Of course, when you are under time pressure, to get an application working,
you have to go ahead on your private branch. In this case you take the risk
that your changes are never going to be merged.

Best Regards,
Gergely

2010/3/18 Panayotis Katsaloulis <pan...@pa...>

>
> On 18 Μαρ 2010, at 6:15 ΜΜ, Dr. Alexander K. Seewald wrote:
>
> ...
>
> > Currently it works like that: Wolfgang, Arno or Sascha ask me about
> > a specific functionality (currently it's audio recording), and I
>
> ....
> right, that's the key point:
> they "asked" you :)
>
>
> I know that it really is difficult to handle, but (as I said in
> previous posts), it is expected for a new project to have patches like
> these.
>
> Of course if such patch is not desirable, I could take it back and
> send, for example, only UIViewContoller, then tomorrow another object,
> and so forth :)
> But I believe the total effort then will be much much larger than now,
> since this whole patch has a common logic which at the end of the day
> will make evaluating it easier than to send one file at a time.
> Maybe it might seem too difficult, but it would be easier than to
> "divide and conquer" :)
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>



-- 
Kis Gergely
MattaKis Consulting
Email: ger...@ma...
Web: http://www.mattakis.com
Phone: +36 70 408 1723
Fax: +36 27 998 622

Re: [xmlvm-users] Monster patches and GPL linking exception

[Arno P. <ar...@pu...>]

I wholeheartedly agree with this. If you plan to work on a non-trivial 
enhancement for XMLVM, you should announce that on the mailing list 
before you begin to avoid redundant work.

Arno


On 3/20/10 2:32 AM, Gergely Kis wrote:
> Hi,
>
> I think the solution for this is to communicate more on the mailing
> list, to lay down the technical directions of the project. Right now
> everyone is developing privately, then throws patches "over the wall".
> If we discussed the approaches on the mailing list, then each of us
> would make less duplicated efforts.
>
> Of course, when you are under time pressure, to get an application
> working, you have to go ahead on your private branch. In this case you
> take the risk that your changes are never going to be merged.
>
> Best Regards,
> Gergely
>
> 2010/3/18 Panayotis Katsaloulis <pan...@pa...
> <mailto:pan...@pa...>>
>
>
>     On 18 Μαρ 2010, at 6:15 ΜΜ, Dr. Alexander K. Seewald wrote:
>
>     ...
>
>      > Currently it works like that: Wolfgang, Arno or Sascha ask me about
>      > a specific functionality (currently it's audio recording), and I
>
>     ....
>     right, that's the key point:
>     they "asked" you :)
>
>
>     I know that it really is difficult to handle, but (as I said in
>     previous posts), it is expected for a new project to have patches like
>     these.
>
>     Of course if such patch is not desirable, I could take it back and
>     send, for example, only UIViewContoller, then tomorrow another object,
>     and so forth :)
>     But I believe the total effort then will be much much larger than now,
>     since this whole patch has a common logic which at the end of the day
>     will make evaluating it easier than to send one file at a time.
>     Maybe it might seem too difficult, but it would be easier than to
>     "divide and conquer" :)
>
>
>     ------------------------------------------------------------------------------
>     Download Intel&#174; Parallel Studio Eval
>     Try the new software tools for yourself. Speed compiling, find bugs
>     proactively, and fine-tune applications for parallel performance.
>     See why Intel Parallel Studio got high marks during beta.
>     http://p.sf.net/sfu/intel-sw-dev
>     _______________________________________________
>     xmlvm-users mailing list
>     xml...@li...
>     <mailto:xml...@li...>
>     https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>
>
>
> --
> Kis Gergely
> MattaKis Consulting
> Email: ger...@ma... <mailto:ger...@ma...>
> Web: http://www.mattakis.com
> Phone: +36 70 408 1723
> Fax: +36 27 998 622
>
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
>
>
>
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users

Re: [xmlvm-users] Monster patches and GPL linking exception

[Sascha H. <sa...@xm...>]

I very much agree.

So far, we (the core team) weren't very open about what we are working on
either I take it as a task on my todo list to create a page on our home
page, where we can track what people are working on. This roadmap should be
extremly useful for everyone involved

// Sascha

On Thu, Mar 25, 2010 at 2:28 PM, Arno Puder <ar...@pu...> wrote:

>
>
> I wholeheartedly agree with this. If you plan to work on a non-trivial
> enhancement for XMLVM, you should announce that on the mailing list
> before you begin to avoid redundant work.
>
> Arno
>
>
> On 3/20/10 2:32 AM, Gergely Kis wrote:
> > Hi,
> >
> > I think the solution for this is to communicate more on the mailing
> > list, to lay down the technical directions of the project. Right now
> > everyone is developing privately, then throws patches "over the wall".
> > If we discussed the approaches on the mailing list, then each of us
> > would make less duplicated efforts.
> >
> > Of course, when you are under time pressure, to get an application
> > working, you have to go ahead on your private branch. In this case you
> > take the risk that your changes are never going to be merged.
> >
> > Best Regards,
> > Gergely
> >
> > 2010/3/18 Panayotis Katsaloulis <pan...@pa...
> > <mailto:pan...@pa...>>
> >
> >
> >     On 18 Μαρ 2010, at 6:15 ΜΜ, Dr. Alexander K. Seewald wrote:
> >
> >     ...
> >
> >      > Currently it works like that: Wolfgang, Arno or Sascha ask me
> about
> >      > a specific functionality (currently it's audio recording), and I
> >
> >     ....
> >     right, that's the key point:
> >     they "asked" you :)
> >
> >
> >     I know that it really is difficult to handle, but (as I said in
> >     previous posts), it is expected for a new project to have patches
> like
> >     these.
> >
> >     Of course if such patch is not desirable, I could take it back and
> >     send, for example, only UIViewContoller, then tomorrow another
> object,
> >     and so forth :)
> >     But I believe the total effort then will be much much larger than
> now,
> >     since this whole patch has a common logic which at the end of the day
> >     will make evaluating it easier than to send one file at a time.
> >     Maybe it might seem too difficult, but it would be easier than to
> >     "divide and conquer" :)
> >
> >
> >
> ------------------------------------------------------------------------------
> >     Download Intel&#174; Parallel Studio Eval
> >     Try the new software tools for yourself. Speed compiling, find bugs
> >     proactively, and fine-tune applications for parallel performance.
> >     See why Intel Parallel Studio got high marks during beta.
> >     http://p.sf.net/sfu/intel-sw-dev
> >     _______________________________________________
> >     xmlvm-users mailing list
> >     xml...@li...
> >     <mailto:xml...@li...>
> >     https://lists.sourceforge.net/lists/listinfo/xmlvm-users
> >
> >
> >
> >
> > --
> > Kis Gergely
> > MattaKis Consulting
> > Email: ger...@ma... <mailto:ger...@ma...>
> > Web: http://www.mattakis.com
> > Phone: +36 70 408 1723
> > Fax: +36 27 998 622
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > Download Intel&#174; Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> >
> >
> >
> > _______________________________________________
> > xmlvm-users mailing list
> > xml...@li...
> > https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> xmlvm-users mailing list
> xml...@li...
> https://lists.sourceforge.net/lists/listinfo/xmlvm-users
>