Thread: [Doxygen-develop] Maintainance of the "Projects that use doxygen" page
Brought to you by:
dimitri
From: Sebastian P. <web...@ha...> - 2007-02-20 01:32:28
|
Hello everybody! I think it was several months ago when I sent in requests for additions to the doxygen users page to Dimitri. Nothing happened and from monitoring that page I know that is has not seen any additions at all for a long time. But I'm not here to complain - I am here to offer help. I'm here to ask for the right to help maintaining that page. The list is not structered, might contain broken links and is getting more out of date every day. I don't need exclusive rights - I just want to be in the set of people maintaining this page so it stays part of the present, not past. I am one of the maintainers of the application section on the XSPF website (http://www.xspf.org/applications/) so this is not a new job to me. Please let me know if you are interested in working together. My SourceForge nick is "hartwork" in case write access is bound to project membership. Sebastian |
From: Sebastian P. <web...@ha...> - 2007-02-27 18:50:57
|
Hello again! If you don't want me for the maintainer please let someone else do that job - just don't let the page die. Please say a word to this, I don't like talking to myself. Sebastian |
From: Dimitri v. H. <do...@gm...> - 2007-02-27 20:09:31
|
Hi Sebastian, Sorry for not replying before. As usual I was too busy at the time I read your mail and it then forgot about it later on :-( I really appreciate your offer and would like to make use of it. You are right in that the page does not get updated as often as it should. I think there are two ways to proceed. 1) I send you the current source page (the raw page without the headers and side panel) and you update it on a regular basis, send me the result and I upload it to my site. 2) We move to page to sourceforge altogether and I add you as a developer so you can update it completely independent of me. I would propose to start with option 1) and see if that is workable. If not then go to option 2), ok? Thanks again for your offer to help, Regards, Dimitri On 2/27/07, Sebastian Pipping <web...@ha...> wrote: > > Hello again! > > > If you don't want me for the maintainer please > let someone else do that job - just don't let the > page die. Please say a word to this, I don't like > talking to myself. > > > > Sebastian > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > |
From: Sebastian P. <web...@ha...> - 2007-02-27 21:24:53
|
Dimitri van Heesch wrote: > I think there are two ways to proceed. > 1) I send you the current source page (the raw page without the headers > and side panel) > and you update it on a regular basis, send me the result and I > upload it to my site. > 2) We move to page to sourceforge altogether and I add you as a > developer so you can > update it completely independent of me. > > I would propose to start with option 1) and see if that is workable. If > not then go to option 2), ok? ------------------------------------------------------------------- I don't think we can go for 1) as a longterm solution but we can start with that. Thank you! Sebastian |
From: Kevin M. <ke...@pl...> - 2007-02-27 22:35:58
|
Please make sure that my project, libteklti [http://sourceforge.net/projects/libteklti] is added to the list. Thank you, - KJM Sebastian Pipping wrote: > Dimitri van Heesch wrote: > >>I think there are two ways to proceed. >>1) I send you the current source page (the raw page without the headers >>and side panel) >> and you update it on a regular basis, send me the result and I >>upload it to my site. >>2) We move to page to sourceforge altogether and I add you as a >>developer so you can >> update it completely independent of me. >> >>I would propose to start with option 1) and see if that is workable. If >>not then go to option 2), ok? > > > ------------------------------------------------------------------- > I don't think we can go for 1) as a longterm solution > but we can start with that. Thank you! > > > > Sebastian > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > |
From: Sebastian P. <web...@ha...> - 2007-02-27 23:41:21
|
Kevin McBride wrote: > Please make sure that my project, libteklti > [http://sourceforge.net/projects/libteklti] is added to the list. ----------------------------------------------------------- Sure. Please let me know what text you want for the description. I think it should answer these questions: * sharp summary of function and problem domain * license * supported platforms * programming language(s) used (Yes, I could try to write this summary myself but this is in my eyes something the program authors should do themselves.) Sebastian |
From: Kevin M. <ke...@pl...> - 2007-02-28 18:03:21
|
Sebastian Pipping wrote: > Kevin McBride wrote: > >>Please make sure that my project, libteklti >>[http://sourceforge.net/projects/libteklti] is added to the list. > > > ----------------------------------------------------------- > Sure. Please let me know what text you want > for the description. I think it should answer > these questions: > * sharp summary of function and problem domain > * license > * supported platforms > * programming language(s) used > Summary: The Technical Library Template Interface is a library capable of providing standardized interfaces in Creative Commons EAL-4 standards to the open source community. License: GNU Library General Public License (LGPL) Supported Platforms: *nix (Linux and most Unix-based) Programming Languages: C, C++, GNU Assembler > > > > Sebastian > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > |
From: Sebastian P. <web...@ha...> - 2007-03-08 19:28:48
|
Kevin McBride wrote: > Summary: The Technical Library Template Interface is a library capable > of providing standardized interfaces in Creative Commons EAL-4 standards > to the open source community. > > License: GNU Library General Public License (LGPL) > > Supported Platforms: *nix (Linux and most Unix-based) > > Programming Languages: C, C++, GNU Assembler ------------------------------------------------------------- I changed the description to your summary suggestion. Click here: http://www.stack.nl/~dimitri/doxygen/projects.html#libteklti Sebastian |
From: Sebastian P. <web...@ha...> - 2007-02-28 17:23:23
|
Kevin McBride wrote: > Please make sure that my project, libteklti > [http://sourceforge.net/projects/libteklti] is added to the list. --------------------------------------------------------- Added. Should be online soon. Sebastian |