[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cross-project-issues-dev] Feature descriptions
- From: Aleksandar Kurtakov <akurtako@xxxxxxxxxx>
- Date: Tue, 12 Nov 2013 13:13:38 -0500 (EST)
- Delivered-to: email@example.com
- Thread-index: a5VeIydV8AqefkamwFuCzx1qMjSgrQ==
- Thread-topic: Feature descriptions
----- Original Message -----
> From: "Wayne Beaton" <wayne@xxxxxxxxxxx>
> To: "Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>
> Sent: Tuesday, November 12, 2013 8:05:20 PM
> Subject: [cross-project-issues-dev] Feature descriptions
> So I got a little bogged down this morning helping a community member install
> some Eclipse software.
> At one point, I was connected to a handful of p2 repositories that contained
> less-than-helpful descriptions. I assume that we actually want people to
> install our software, and so feel that providing a help description that
> compels them to do so is a reasonable thing to hope for.
> Rather than pick on any individual project, I'd like to invite projects to
> review your feature descriptions to see if you can be more helpful for
> potential users and consumers.
> e.g. describing the feature named "XXX UI" as "XXX UI Feature" is not
> particularly helpful. Maybe include a little something to describe why
> somebody might want to install this rather than, say, the "XXX SDK" (which
> is described as the "XXX SDK Feature").
> Or I can start opening bugs.
I would definetly welcome such bugs as keeping track of all the features is too hard and having bugs when someone spots something makes it easier to not forget it.
Red Hat Eclipse team
> Wayne Beaton
> Director of Open Source Projects, The Eclipse Foundation
> Learn about Eclipse Projects
> cross-project-issues-dev mailing list