Re: SDK header translations licensing?

Hello Peter,

Doesn't this get boring...?

> 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. Nonetheless
please also contact also the DSPack guys.

> 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 and only this is the official position
of JEDI steering until we publish something else.

> 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.

> 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? 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.

Furthermore it is part of our policy to inform people which are not that
close to JEDI about bugs in their API conversions - esp. the ones we link to
since we do not want to create different branches of one and the same API.
It simply would not make any sense to create a local copy, fix a bug and
have to monitor the original for any changes, updates etc. as well.

Ideas on how to improve that process are welcome.

> 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.


> Beside the problem, that the new homepage is furthest unknown and with the
> usually tempo of JEDI Steering this stay valid for many month or even
> years.

The CMS homepage is still under construction. As soon as lets say 80% of the
needed functionality is there we will start to promote it more aggressive -
as soon as over 90% of the needed functionality is there it will replace the
current delphi-jedi homepage completely. It does not make sense to promote a
website with illegal links, non complete descriptions, missing content etc.
During the last few weeks the issuetracker and the general server
configuration simply was more important and therefor had a higher priority
than the website. This will change soon. We are working on that and I hope
to finish it within the 2nd quarter 2004. If someone reading this has a few
hours left and wants to help a little bit please feel free to contace me -
hint, hint :-)


- Matthias



 
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/