Re: SDK header translations licensing?

on 2004-03-06T14:55:36+01:00 Matthias Thoma wrote:
> Doesn't this get boring...?

Of course, moreover it reduce the free time to create meaningful work.
But as long as JEDI Steering and in this case especially you refuse a
constructive discussion to solve the problems, is is necessary.
Unfortunately!


>> You should discuss the problems, mentioned in this forum in the DSPack
>> forum, because the problems are DSPack related, not JEDI related.

> Martin, the underlaying problem is also JEDI related so feel free to
> continue discussion API Library, MPL related problems here.

To discuss the problem in this forum can not change it, because the
relevant libraries don't be JEDI libraries from sight of JEDI
Steering. Moreover the preceding discussion don't related the actual
problem, which is not header conversion, rather conversion of sample
code.


>> A half year ago, JEDI Steering confirm this statement from Robert
>> Marquardt: "It is not our job to work on new conversions or update
>> older ones." This was the official end of the original JEDI API
>> Library.

> The position of JEDI Steering is that it is our goel to provide
> Delphi developers with timely access to Application Programming
> Interfaces(APIs), libraries and other facilities which extend the
> capability of the Delphi programming environment - to accomplish
> this task we have set ourselves the task of converting published C
> header files into new Delphi units, classes and components that make
> new technologies freely available for use in the native Delphi
> environment. This includes to work on new conversion and to update
> and maintain older ones.

This is your opinion, the reality I have describe before.


> This and only this is the official position of JEDI steering until
> we publish something else.

The statement was posted and I have ask JEDI Steering for a official
statement. If the statement is not the official position of JEDI
Steering, why JEDI Steering don't have contradict, although this issue
was discussed many times in public. Moreover the statement reflect the
reality.

As long as JEDI Steering don't have state a oficial contradiction and
as long as Mister Marquardt's statement reflect the reality your
statement is only a fantasy.


>> Meantime JEDI Steering have create a new strategy, it reduce the JEDI
>> API Library project to a link list and hope, that anybody from outside
>> modify the entries.

> No, no. We extended the API Library - big difference.

Where? JEDI API Library don't extended the API Library, you have add
external work only. That is the reality, please cease to dream.


>> If a user write a bug report, the author don't have a chance to get
>> the information and therefore to improve his work.

> Quote from the Delphi JEDI+ homepage: "please contact Delphi-JEDI+, if you
> find any bug." - now where is my opportunity to improve my API conversion if
> the guys contact you?

When do you want to improve your conversions?
Currently you don't have enough free time to do your job in the JCL.

BTW: This sentence is part of the old JEDI+ API page, it is not longer
necessary in the new version.


> Our system is better since both the bugtracker as well as the
> comments one can attach to conversions is browseable by anyone. If
> JEDI people do not have time to update an API the bug is still
> publicy visible, trackable etc. by everyone.

Nonsense. Unfortunately this is a example, how arrogance blindfold.

Meantime three years ago we both have discussed about the needed
changes of JEDI's infrastructur and I have recommend the changes,
which now are realized in a furthest unknown JEDI homepage.

Why do you believe, that I don't plan to create the some
infrastructure on JEDI+ API? Long time ago you have add the API
library part to the new JEDI homepage, I have test my new homepage
version. Like you, I don't want to publish it, before it is completed.

BTW: In the last years, I have create new ideas, with other word, our
system is not better.


> Furthermore it is part of our policy to inform people which are not that
> close to JEDI about bugs in their API conversions

This claim, that the author want to be close to JEDI API Library. If
not, he get a mail and modify the conversion. But the bug is still
open in JEDI's bug tracking system, it is related to the people (you
need to create a pseudo member in the bug tracking system). Because
the new version is not available on the JEDI page and a visitor don't
can see or profit from the bug fixes, JEDI harm the reputation of the
original author.

There are more problems. How you can see, many users don't be able to
use the bug tracking system in a correct manner. Therefore you need a
people, which assign a bug to the correct project and category. Which
person should do this?


> - esp. the ones we link to since we do not want to create different
> branches of one and the same API.

Because the page is unmaintained JEDI could cause such branches. If a
visitor of the JEDI API Library page don't see any reactions of a
author, maybe he make a own bugfix and submit it to JEDI.


> Ideas on how to improve that process are welcome.

Not really, as long as JEDI Steering blindfold for the problems.

JEDI Steering welcome slaves, which do the work without opposition.
Ideas, which are not be fit to the Steering opinion become to reject,
as well persons, which are not accepted by a Steering member.


>> Maybe the author create a new version of his conversion. Because there
>> is not anybody, which maintain the JEDI API Library list, any visitor
>> don't have a chance to get the new conversion.

> There are several mechanismens which are designed to prevent that.

You are able to name and explain this mechanismens?
I can not see any.


> We are working on that and I hope to finish it within the 2nd quarter 2004.

We will see.


> If someone reading this has a few hours left and wants to help a
> little bit please feel free to contace me - hint, hint :-)

Unfortunately Mister Marquardt scare potential helpers and JEDI
Steering confirm his behavior as correct and praise Mister Marquardt
instead to rebuke him. Meantime other Steering members participate on
his negative behavior. Other aspects, how JEDI Steering scare
previously active developers, I have describe in the past.

Now you need to live with the consequences. You know the way out from
this problems, but you want to keep your job in Steering instead of
real improvements.

Peter.



------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark
Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada.
http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/i7folB/TM
---------------------------------------------------------------------~->

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
     http://groups.yahoo.com/group/Delphi-JEDI/

<*> To unsubscribe from this group, send an email to:
     [email protected]

<*> Your use of Yahoo! Groups is subject to:
     http://docs.yahoo.com/info/terms/