<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Thanks for the links, I'll take a look on the bugslist. I'll also checkout the code and see what can I do there. Thanks, Mohamed Nicu Buculei wrote: <blockquote cite="mid:4746FE3A.6040800@nicubunu.ro" type="cite"> <pre wrap="">Mohamed Ibrahim wrote: </pre> <blockquote type="cite"> <pre wrap="">So I think I need first to communicate with the dev side, so being on the mailing list is a good step. I believe that openclipart needs on the dev side: - A bug/feature list. Either bugzilla, mantis or may be we can use one on sf.net </pre> </blockquote> <pre wrap=""> We use the freedesktop.org bugzilla: <a class="moz-txt-link-freetext" href="https://bugs.freedesktop.org/buglist.cgi?product=openclipart.org">https://bugs.freedesktop.org/buglist.cgi?product=openclipart.org</a> </pre> <blockquote type="cite"> <pre wrap="">- Planned goals for every release. </pre> </blockquote> <pre wrap=""> We didn't release for a couple of years already, the goal for the next release is (I believe) "import all the old files from the old site to ccHost". We also need to figure a way to package the files from ccHost. </pre> <blockquote type="cite"> <pre wrap="">- The goals/features needs to be distributed on people </pre> </blockquote> <pre wrap=""> It works the other way: people step up and take ownership for some goals. </pre> <blockquote type="cite"> <pre wrap="">- Use openproj or some thing similar to track progress. </pre> </blockquote> <pre wrap=""> We have a few goals and a few people, I think a wiki in manageable for tracking the progress. </pre> </blockquote> </body> </html>