(This is in response to a private message by oliver.)
> Hi wrygiel,
> i am Oliver, developer at oc.de. I am very happy to read your
> posting. The first impression is "wow".
Thanks very much

I'm glad to hear you liked it because one of my goals is to have OKAPI
working on both our sites (and later - possibly on every other
opencaching site).
> New oc.de code is based on smarty and has several incompatible
> changes and many improvements. However, some old beginner-stuff from
> my php-beginning time in 2003 is still present.
Currently, OKAPI does not use much of the "legacy code". In fact, the
only things I use are "sql" and "sqlValue" functions + some global
variables. So, the only important thing is the database structure.
I believe it is possible that the current version of OKAPI would work
with opencaching.de "as is", without any need for modifications, but I
would have to see your database to be sure. However, you may just try
it, installation is simple - just 5 minutes of work (see project main
page). It requires PHP 5.3.
In case of incompatibilities, this could be helped with some crude
conditions like "if ($GLOBALS['absolute_site_URI'] ==
'
http://opencaching.de/') { sql1 } else { sql2 }".
If you choose to use OKAPI, I would expect for all code changes to be
commited into the main OKAPI repository. I DON'T want you to develop
your own OKAPI branch, I hope you understand why - the project is all
about compatibility!
In other words - I will be happy to accept all your changes to OKAPI,
*IF* exactly the same changes will go to opencaching.pl. And I really
hope you will agree on this - it would be the best option for both of
our sites.
> I have to view it in detail, but as i remember, the most important
> change for the API is the table "cache_status". Maybe oc.pl does not
> contain boolean columns allow_user_view allow_owner_edit_status
> allow_user_log . It is absolutly required to follow these settings -
> maybe waldek can add that columns to oc.pl code, too (if required).
I think I don't understand what you're saying. Why would API need a
change in table "cache_status"? Also, I don't know about these allow_*
columns. (I am new to OpenCaching project, I've first seen this
database only two months ago. I do not know much...)
> We at oc.de need to decide first what license to apply to the cache
> data. As i remember, oc.pl does CC licensing for cache data?
Our "Terms of Use" page is in BETA, as the rest of OKAPI.

In fact,
I just copied parts of the "opencaching.com API" licence, which I
found apropriate.
Do you think it is possible for us to agree on a common licence, for
both of our sites?
> Let me know if you need write permission to git repository
> (repository is public read). Or if you prefer to keep it in you own
> repository.
I want to keep OKAPI code separate. I think this will simplify
development and deployment process. The idea is to FIRST have things
changed in OKAPI repo, THEN merge them into all production sites.