From: Alistair Bush <ali_bush@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: [gentoo-java] [Fwd: [linux-distros-dev] A bit of a reboot] - eclipse
Date: Mon, 01 Sep 2008 20:25:07 +1200 [thread overview]
Message-ID: <48BBA6E3.3050206@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2743 bytes --]
In case anyone hasn't gotten this....
-------- Original Message --------
Subject: [linux-distros-dev] A bit of a reboot
Date: Fri, 29 Aug 2008 14:06:02 -0400
From: Andrew Overholt <overholt@redhat.com>
To: linux-distros-dev <linux-distros-dev@eclipse.org>
Hi,
As you all know, our project hasn't really been a shining example of
output or participation. I'd like to change that. What follows are my
thoughts. I'd appreciate comments/criticisms/ideas/whatever.
Reasons for existence / Goals
=============================
We started the project after a few different distribution maintainers
found that they were complaining about the same things (builds being
difficult, lack of autotools support in CDT, package maintenance
difficulties, etc.). The goals at the time were two-fold: 1) be a
place for distributions to collaborate and 2) provide tools specific to
Linux developers and packagers.
Current status
==============
We have some Linux-specific tools that are doing well: the ChangeLog
plugin and the RPM specfile editor. Jeff Johnston has also told me that
he plans on contributing his autotools plugins. There's also some
renewed interest in the OProfile plugin which I'm hoping we'll see some
patches for soon. So we're not doing *too* badly on providing tools.
Unfortunately, little cross-distro collaboration has actually taken
place. I'd like to think this is because we all have lots to deal with
in real life and in our respective distros. What can do to improve
here? Since we all fight the same battles with builds and stuff, it
would be good to work together and not duplicate effort.
I think we need to do a few things:
1. Make an update site for the tools we have.
2. Have an actual release! Then we won't be the bad Eclipse project who
never really followed the processes :)
3. Re-focus on our goals.
To be honest, I think the tools half of our project is doing alright.
We just need to follow some processes a bit more. It's the distro
collaboration stuff that needs to be improved. I think the project that
Ben Konrath started -- eclipse-build -- is a good place for this.
Ideally we can get to the point where that project produces a buildable
source tarball that all distros can use. We can probably aim for the
Ganymede winter maintenance release. It will take care of the stuff we
all do on top of the releng srcIncluded drops. Also, we can share our
common methods of building non-SDK plugins. Scripts to run test suites
are also a good place to work together.
We need to have a plan in place soon so I'll be working on something
more formal than this email. I really welcome all feedback so please
let me know whatever you're thinking -- even if it's "you're stupid" ;) .
Andrew
[-- Attachment #2: Attached Message Part --]
[-- Type: text/html, Size: 1055 bytes --]
[-- Attachment #3: Attached Message Part --]
[-- Type: text/plain, Size: 169 bytes --]
_______________________________________________
linux-distros-dev mailing list
linux-distros-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linux-distros-dev
reply other threads:[~2008-09-01 8:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48BBA6E3.3050206@gentoo.org \
--to=ali_bush@gentoo.org \
--cc=gentoo-java@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox