"Andrew Gillett" <[EMAIL PROTECTED]>; [EMAIL PROTECTED]:19 -0500
Leif W wrote:
"Andrew Gillett" <[EMAIL PROTECTED]>; [EMAIL PROTECTED]:11 -0500
I think what used to be fun, was to have demonstrations from other people that show the amazing things that can be done, with some kind of interactive application, with the full documentation. Or even just one or two little things, and how to combine them in differnt ways.
A few things I would like to do are to include the dynapi 3 examples and documentation on the main web page. Some of the examples are very impressive (those that work ;-). I would also like to set up a wiki as a kind of "shared staging area" for development of the documentation.
Yes, I'd like to see a more integrated home page. To have one spot where people can go, without looking at the hideous SF page until they're ready to post a patch or something, but even then, to have some of those links on the main site somewhere. To put the developer info into a section of the main site. Update all the developer docs, like how to get into the CVS, how to use WinCVS or TortoiseCVS in Windows, or command line CVS in Windows or Linux.
Those demos are where most of the learning occurs. I understand the value of having the DynAPI docs look like a site of their own, but now we've got users looking on the main site, the developer site, and in the source-tree site. And all of the information is out of sync and harder to maintain. It would be nice to have it all broken into the abstract pieces, a doc source, and upon a release regenerate the source docs so they fit in with the main website. Clearly documentation should be a separate project by itself, perhaps having a docs tree in CVS who's major and minor versions follow the releases. With the tools to regenerate docs for web site and source code release.
If there there are people out there who are willing to put their hand up to contribute to DynAPI, perhaps we could work towards getting a final Release 3 out. Some of the things this would involve would include getting admin access to the SourceForge project, updating the web site, writing more documentation, and testing the existing code base.
Anyone interested?
I still have a rough idea of all the "unfixed" things in the DynAPI. This is off the top of my head. I'd have to search the archives for better details.
There are a whole bunch of bug reports and submitted patches and so forth on the project trackers page (http://sourceforge.net/tracker/?group_id=5757). If we're going to do anything with dynapi, we should do it properly and use the existing tracking systems. I would want to add these issues to the tracker and work through the outstanding bugs that have been logged and either fix & close them or delete them.
Yes, good point. I've forgotten about the tracking system but it was in the back of my mind after I posted. Definitely need to make use of what is available.
Leif, you've clearly been a dynapi enthusiast since well before I first heard of it, and I greatly appreciate your quick response. I would still like to see a few more people express some interest before making a significant commitment myself. And of course we need to hear from at least one of the existing site admins.
Well, I'm committed, at least in spirit. I plan to get my focus back, so my committment will mean something. Even if I'm the only one, I'll still do what I can.
Leif
------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 _______________________________________________ Dynapi-Dev mailing list Dynapi-Dev@lists.sourceforge.net http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
