"Frank Alcantara" <[EMAIL PROTECTED]>; [EMAIL PROTECTED]:01 -0500
[snip]
First of all, please forgive my English....:)
We are trying to finish the Thyapi site this weekend... we have one old
version in sf cvs... it is funcional, but it is old... about two months
ago. We as got in surprise with Dynapi coming back to life...:)
Congratulations....
Two months is new-enough for us. ;-)
We did fixed some small bugs in Dynapi, but we will not be able to send
it to you until next Tuesday, sorry for this delay, but we are trying to
finish one project this weekend. We already tested thyapi, in ie,
firefox and safari it is running like a charm...:)
We'll probably be taking some days to a week to read through the admin stuff at SourceForge, and figuring out where every knob and button is located and what happens if you twiddle it. Then we'll have some more days or week discussing different topics and figuring out what to change, what to remove, what to repair. We're not just looking at the code base, but the site content and layout, and also whatever is in the shell server. I think there's a lot of cruft in there that could probably be removed or archived if it's useful.
Anything you can provide would be great, but we won't be ready for a little bit. Did you happen to keep track of all the bugs and the fixes? You could perhaps make patches (diff -u) if the files are similar. Or if they are too different then you could maybe add notes to the bug tracker, identify where the problem is in DynAPI CVS code (file, line, char, string), and how to fix.
Yeap, we will be proud to help DynApi, as far as possible, Unfortunately
we did started ThyApi project and did some local marketing about it. And
do not want to loose these efforts.
Understandable. So long as licensing is observed (DynAPI is LGPL) and full credit is given at least in the source code, there's no problem. If you change the API, I think it means the changes must be released as LGPL. But if you make extensions to the API that exist in completely separate files, then they can be whatever license you want. Contrary to GPL, which would require the other code to also be GPL. At least it's how I understand it. There was discussion some years ago, it's in the archives.
Our main site is partially on air... http://www.thyamad.com there you will find more information about us...
I found it, thanks. The site looks very professional.
I am admin in other projects, and developer in some others. in one of
then I just send one idea to keep descendant projects with the original
one. I got this idea from Apache.org. The incubator.
Well, there is the IDE written using DynAPI, but I think they set up another SF project because there were some problems or confusions about creating CVS entries. I'm not 100% sure that's correct, it's from memory. ;-) There is also the DynAPI compressor, and I can't remember where it is, but that's surely another example of things that should go into the incubator or maybe the project itself.
In few words....
We could create a branch in Dynapi cvs called incubator and create some
rules to put the descendant projects there. So, for example, we could
keep our thyapi project page in source forge, and keep it also in Dynapi
incubator, The vantages are... The projects keep connect and we create a
new barrier, even psychological, to fork, the projects will bring
visibility for each other. And most of all the main project will keep
receiving corrections and enhancements from the descendant projects.
What do you think about it?
Your English was very good up until now, and I'm a little confused. ;-) I think I understand, but we can talk more later to make sure we understand. The main point I am confused about, is how these are connected. If you make a change to Thyapi then how do the changes get into Dynapi? Is it automatic or needs to be done manually. Because as far as I know, it would be manually, and that could create extra maintenance work. But I may not understand correctly. But I agree, it would be good to advertise the code as much as possible... But only when we're ready! ;-)
of course it will need some well wrote guide lines...:)
Besides your opinion we will send our corrections, As far I remember, all of then was about browser compatibility.
Yeah, ther are a lot of open bugs with compatibility problems, some was on the list, some in the trackers, some on other parts of the site, a lot isn't connected into the trackers so it makes a hard job to collect everything and put it there, test and resolve it, but make sure it works with some older browsers too.
Leif
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Dynapi-Dev mailing list Dynapi-Dev@lists.sourceforge.net http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
