Greetings!

If you go to dsource.org, and click on projects, there is a multitude of projects there.  Beautiful!  However, if one wants to know anything about the project, the only one that seems to have any extraordinary information about the project is mango.  It would be nice for each project to have some kind of description of the project other then the short two'liner that each has.

Just a thought...

josé

On Wed, 27 Jul 2005 19:55:42 +0000 (UTC), jicman wrote:

> Greetings!
> 
> If you go to dsource.org, and click on projects, there is a multitude of projects there.  Beautiful!  However, if one wants to know anything about the project, the only one that seems to have any extraordinary information about the project is mango.  It would be nice for each project to have some kind of description of the project other then the short two'liner that each has.
> 
> Just a thought...

I'm happy to comply. This is Build's current description:

"Build   -   Tool for building D executables and libraries.
Build is designed to simplify the process of compiling a D application. It
removes the need for tools like make and Scons, in that it analyzes the
source code to work out source file dependancies, and then determines which
of the dependant files need recompiling and linking. It can build either
executables or libraries."

Can anyone suggest more that I could add to improve it?

-- 
Derek Parnell
Melbourne, Australia
28/07/2005 7:44:31 AM

Looks good too me -- although dependancies is misspelled . ( dependencies )

Charlie

"Derek Parnell" <derek@psych.ward> wrote in message news:vobmel0htx4p.1bng979z5hsd5.dlg@40tude.net...
> On Wed, 27 Jul 2005 19:55:42 +0000 (UTC), jicman wrote:
>
> > Greetings!
> >
> > If you go to dsource.org, and click on projects, there is a multitude of projects there.  Beautiful!  However, if one wants to know anything
about the
> > project, the only one that seems to have any extraordinary information
about the
> > project is mango.  It would be nice for each project to have some kind
of
> > description of the project other then the short two'liner that each has.
> >
> > Just a thought...
>
> I'm happy to comply. This is Build's current description:
>
> "Build   -   Tool for building D executables and libraries.
> Build is designed to simplify the process of compiling a D application. It
> removes the need for tools like make and Scons, in that it analyzes the
> source code to work out source file dependancies, and then determines
which
> of the dependant files need recompiling and linking. It can build either executables or libraries."
>
> Can anyone suggest more that I could add to improve it?
>
> --
> Derek Parnell
> Melbourne, Australia
> 28/07/2005 7:44:31 AM

most of the projects are at an extremely early stage, the best place to find info is the forum, most projects have a post with what you are looking for.


jicman wrote:
> Greetings!
> 
> If you go to dsource.org, and click on projects, there is a multitude of
> projects there.  Beautiful!  However, if one wants to know anything about the
> project, the only one that seems to have any extraordinary information about the
> project is mango.  It would be nice for each project to have some kind of
> description of the project other then the short two'liner that each has.
> 
> Just a thought...
> 
> josé
> 
> 

Derek Parnell says...
>
>On Wed, 27 Jul 2005 19:55:42 +0000 (UTC), jicman wrote:
>
>> Greetings!
>> 
>> If you go to dsource.org, and click on projects, there is a multitude of projects there.  Beautiful!  However, if one wants to know anything about the project, the only one that seems to have any extraordinary information about the project is mango.  It would be nice for each project to have some kind of description of the project other then the short two'liner that each has.
>> 
>> Just a thought...
>
>I'm happy to comply. This is Build's current description:
>
>"Build   -   Tool for building D executables and libraries.
>Build is designed to simplify the process of compiling a D application. It
>removes the need for tools like make and Scons, in that it analyzes the
>source code to work out source file dependancies, and then determines which
>of the dependant files need recompiling and linking. It can build either
>executables or libraries."
>
>Can anyone suggest more that I could add to improve it?

Heh heh heh... Derek, your build tool was the last project I was thinking of. :-)  Your description is very helpful, though, if you look at mango's, there is a home page where everything else is included.  However, all I am looking for is something like yours description on each project.  Yes, I know some are in limbo, productivily speaking, however, there are a few that are actively being developed and their description are not descriptive (pardon the repetition) at all.

For example:
http://www.dsource.org/projects/dsp/
http://www.dsource.org/projects/d_server_platform/
http://www.dsource.org/projects/eclipseD/
..
..
etc...

These description say very little about what the project is.  You have done a fine job, Derek.  As always. :-)

thanks,

josé

I understand that, but, the description of the product defines what the product will be (or likely be), so it's needed for people to get interested on them. For example, if it is an editor, then it should have the capabilities that it has now, the capabilities that it will have in the future.  This will help the users/browsers of dsource.org understand more about the project, which will cause more downloads of the products.  Sometimes I want to download a product, but there is not enough information there.  So, I am not going to download a zip file to read the "readme.txt" file and see what this application does.  It should be on the description.

Again, just a thought to help us out...

J Thomas says...
>
>most of the projects are at an extremely early stage, the best place to find info is the forum, most projects have a post with what you are looking for.
>
>
>jicman wrote:
>> Greetings!
>> 
>> If you go to dsource.org, and click on projects, there is a multitude of projects there.  Beautiful!  However, if one wants to know anything about the project, the only one that seems to have any extraordinary information about the project is mango.  It would be nice for each project to have some kind of description of the project other then the short two'liner that each has.
>> 
>> Just a thought...
>> 
>> josé
>> 
>> 

In article <dc9ljb$1745$1@digitaldaemon.com>, jicman says...
>
>Heh heh heh... Derek, your build tool was the last project I was thinking of. :-)  Your description is very helpful, though, if you look at mango's, there is a home page where everything else is included.  However, all I am looking for is something like yours description on each project.  Yes, I know some are in limbo, productivily speaking, however, there are a few that are actively being developed and their description are not descriptive (pardon the repetition) at all.
>
>For example:
>http://www.dsource.org/projects/dsp/

::embarassed::

Thank you for bringing this to my attention.

Until I get that updated, please see the existing documentation.  I have a webpage setup in the SVN repos that should provide a more detailed description of DSP:

http://svn.dsource.org/projects/dsp/trunk/doc/index.html

It is by no means complete.  Any critiques are welcome.

- EricAnderton at yahoo

jicman wrote:
> Greetings!
> 
> If you go to dsource.org, and click on projects, there is a multitude of
> projects there.  Beautiful!  However, if one wants to know anything about the
> project, the only one that seems to have any extraordinary information about the
> project is mango.  It would be nice for each project to have some kind of
> description of the project other then the short two'liner that each has.
> 
> Just a thought...
> 
> josé
> 
> 

dsource doesn't allow the owner of the project to set/change the overview.
there are many features on dsource not yet implemented.
we have to thank Brad for the availability of dsource anyway.

Antonio

im sorry, do you want your money back?




jicman wrote:
> I understand that, but, the description of the product defines what the product
> will be (or likely be), so it's needed for people to get interested on them.
> For example, if it is an editor, then it should have the capabilities that it
> has now, the capabilities that it will have in the future.  This will help the
> users/browsers of dsource.org understand more about the project, which will
> cause more downloads of the products.  Sometimes I want to download a product,
> but there is not enough information there.  So, I am not going to download a zip
> file to read the "readme.txt" file and see what this application does.  It
> should be on the description.
> 
> Again, just a thought to help us out...
> 
> J Thomas says...
> 
>>most of the projects are at an extremely early stage, the best place to find info is the forum, most projects have a post with what you are looking for.
>>
>>
>>jicman wrote:
>>
>>>Greetings!
>>>
>>>If you go to dsource.org, and click on projects, there is a multitude of
>>>projects there.  Beautiful!  However, if one wants to know anything about the
>>>project, the only one that seems to have any extraordinary information about the
>>>project is mango.  It would be nice for each project to have some kind of
>>>description of the project other then the short two'liner that each has.
>>>
>>>Just a thought...
>>>
>>>josé
>>>
>>>
> 
> 
> 

People who write free software generally want people to use it.  I would imagine that they would appreciate it when people tell them why they aren't using it.  Such a trivial thing as not having a decent description is a huge barrier to entry.

J Thomas wrote:
> im sorry, do you want your money back?
> 
> 
> 
> 
> jicman wrote:
> 
>> I understand that, but, the description of the product defines what the product
>> will be (or likely be), so it's needed for people to get interested on them.
>> For example, if it is an editor, then it should have the capabilities that it
>> has now, the capabilities that it will have in the future.  This will help the
>> users/browsers of dsource.org understand more about the project, which will
>> cause more downloads of the products.  Sometimes I want to download a product,
>> but there is not enough information there.  So, I am not going to download a zip
>> file to read the "readme.txt" file and see what this application does.  It
>> should be on the description.
>>
>> Again, just a thought to help us out...
>>
>> J Thomas says...
>>
>>> most of the projects are at an extremely early stage, the best place to find info is the forum, most projects have a post with what you are looking for.
>>>
>>>
>>> jicman wrote:
>>>
>>>> Greetings!
>>>>
>>>> If you go to dsource.org, and click on projects, there is a multitude of
>>>> projects there.  Beautiful!  However, if one wants to know anything about the
>>>> project, the only one that seems to have any extraordinary information about the
>>>> project is mango.  It would be nice for each project to have some kind of
>>>> description of the project other then the short two'liner that each has.
>>>>
>>>> Just a thought...
>>>>
>>>> josé
>>>>
>>>>
>>
>>
>>