[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [epp-dev] Extending the EPP Package Configuration File.
|
Hi Nathan,
thanks for helping us and setting up such a Drupal based site. I've written
some comments to your questions below:
On Tuesday 26 February 2008, Nathan Gervais wrote:
> Afternoon all,
>
> You may have been hearing some chatter on this list about a Drupal
> Packaging Site. I've been working on prototyping an Eclipse Community
> Packages site that will appear on Eclipse.org as part of the download
> section. The idea with this site is to gather all of the information for
> the EPP packages created by both the project and other package maintainers.
> Ideally this site won't require any of the maintainers to login and change
> details of the project every time the package is updated. Therefore the
> hope of this discussion is to come to an agreement on using the EPP Package
> Configuration file to allow the package maintainer to include certain
> fields that would be consumed by this new Packaging site. This way we
> keep the maintenance of the package meta-data all in one spot easing the
> burden on the package maintainers.
After our discussions by mail last week, I think it is pretty easy to include
the missing pieces in the configuration file.
> Here's a listing of the fields that I've included in my prototype. These
> fields are subject to change and if I'm missing anything please feel free
> to offer your suggestions. Also note that some of the fields listed might
> already be apart of the configuration file.
>
>
> -Package Name
Maybe we need two name categories, e.g.
* 'eclipse-jee-ganymede-M5' or 'jee' -> already in the config file
* 'Eclipse IDE for Java EE Developers' -> needs to be added
> -Package Download URLs (Should ideally be autogenerated)
This could lead to a new discussion. The current file names, file paths and
their download URLs are tailored to my build scripts, but that's maybe not
ideal for a Drupal site.
> -Package Download Counts (Per Platform)
Other statistics are possible: Download counts in the last 7 days, number of
open bugs, ...
> -Abstract (Basically a plain text description of the package)
Another thing which could be added to the config file and maintained by the
package maintainers.
> -Feature List (A full listing of the features included in the package)
Hmm, a techie will be satisfied by a feature list, but I am not sure if we can
find a better representation / abstraction that makes it easier for users to
select a particular package.
> -Package Maintainer
This is a good point. We could integrate that in the config file and use it in
a similar way as Ganymatic to inform a package maintainer about a failed
build by mail.
> -List of Package Testers
Same as above.
> -Testing Plan URL
That reminds me on starting something in that area... ;-)
> -Bugzilla URL for the package
What Bugzilla URL do you mean? Do you mean the 'initial' package creation bug
like https://bugs.eclipse.org/bugs/show_bug.cgi?id=217784 or do you think of
a button on the Drupal site like 'Report a Bug'.
Regards
Markus