Just one wee inline comment...
On Wed, 2011-05-11 at 19:49 +0100, Peter Dietz wrote:
This discussion is not about the ASync release anymore.
dspace + modules(xmlui, solr) = My DSpace
Well it sort of is. One of the consequences of Async releases is that we
would be moving much of source code
On Wed, May 11, 2011 at 02:50:36PM -0500, Tim Donohue wrote:
On 5/11/2011 1:49 PM, Peter Dietz wrote:
But, for developing DSpace, and people that build from source (since
they've got their own modifications to make), mvn + ant are excellent
tools to do that. For everyone who doesn't quite
A brief comment below
On 5/12/2011 8:55 AM, Mark H. Wood wrote:
I think I hear a disagreement about who the installation docs are for.
Are they for new users, and people who need more control are on their
own? Or are they for people looking to fit DSpace more neatly into
their operation,
Hi Graham,
On 5/11/2011 5:51 PM, Graham Triggs wrote:
On 11 May 2011 20:50, Tim Donohue tdono...@duraspace.org
mailto:tdono...@duraspace.org wrote:
I can definitely see you point about also improving documentation.
But as DSpace is now nearly 9 years old and we still haven't found
To: Graham Triggs
Cc: Mark Diggory; DSpace Developers
Subject: Re: [Dspace-devel] Async releases discussion
Hi Graham,
On 5/11/2011 5:51 PM, Graham Triggs wrote:
On 11 May 2011 20:50, Tim Donohue tdono...@duraspace.org
mailto:tdono...@duraspace.org wrote:
I can definitely see you point about
Hi,
On 12 May 2011 15:30, Tim Donohue tdono...@duraspace.org wrote:
IMHO Documentation should likely have (at least) two audiences:
* Novice User (never tried DSpace before, but wants to try it out and get
it running relatively quickly)
* Advanced User or System Admin (describes/explains all
Hi Graham,
It sounds like we actually agree completely in this. I'm NOT wanting to
create an entirely new (non-Maven) path for customizations/addons that
we cannot support. I'm literally just playing around with Easy Installer
options to see if there's something that will work for both
Hi Alex,
Thanks for the feedback, actually. It's good to get an outside opinion
on all this!
On 5/12/2011 10:51 AM, Lemann, Alexander Bernard wrote:
The person running the simple installer is signing up to be the
administrator for a web application. They're not installing up
Acrobat Reader
Alex,
This is a great list of questions! Its just the kind of real enduser feedback
we need. I invite you to keep this dialog moving with us.
On May 12, 2011, at 8:51 AM, Lemann, Alexander Bernard wrote:
At the risk of being to anecdotal and ranting, but with the goal of bringing
a dspace
Many good points.
The answers to some of those questions is, we don't have a good
answer yet -- only what has worked for some individual. Some of them
(how to do X which isn't built into DSpace) depend on your local
environment. And there's been a sense that things which are common
belong in
On May 12, 2011, at 3:11 PM, Graham Triggs wrote:
On 12 May 2011 16:51, Lemann, Alexander Bernard ablem...@bsu.edu wrote:
I have had trouble with the *customization* documentation. How do I rebuild
reinstall just my changes so things won't take ~3 minutes?
I just ran some compilation
On 11 May 2011 01:48, Mark Diggory mdigg...@atmire.com wrote:
Yes, but you need to realize that confluence has certain standards it
maintains.
1.) Its just one webapplication and only one webapplication
A good thing.
5.) An OSGi implementation mounts a secondary directory to run plugins
On May 10, 2011, at 10:11 AM, Mark H. Wood wrote:
On Tue, May 10, 2011 at 08:56:04AM -0700, Mark Diggory wrote:
On May 10, 2011, at 7:23 AM, Mark H. Wood wrote:
On Tue, May 10, 2011 at 01:38:52PM +0100, Robin Taylor wrote:
[snip]
Whilst editing a pom is an option for developers who are
Hi all,
All I was thinking of was some means of helping a developer or admin
select and add modules to their local DSpace. At the very least we could
provide patches but it would be nice to do something more sophisticated,
you could call it the DSpace AppStore and provide some downloader that
On 11 May 2011 08:12, Mark Diggory mdigg...@atmire.com wrote:
Until you create addons that have dependencies on other addons, then you
need to add more than one jar and make sure your versions are correct, part
of the reason they use OSGi.
This isn't really the right thread for a
Hi Graham,
On 5/11/2011 6:06 AM, Graham Triggs wrote:
At one level, I still find it curious that asking people to run:
mvn packge
or
ant fresh_install
can be considered to be more confusing/harder than running 'install-dspace'.
Admittedly, I don't like that we are asking people to do
Hi,
On 11 May 2011 15:57, Tim Donohue tdono...@duraspace.org wrote:
The missing piece here that you may not have understood is that the DSpace
Easy Installer actually is automating more of the install processes.
That's why I said it would be good to know more about it. I realized it
would be
This discussion is not about the ASync release anymore.
dspace + modules(xmlui, solr) = My DSpace
But about improving the installation problems of the straw man.
I do find using a program like Splunk very awesome. Just download an
archive, unzip, execute [splunk]/bin/start.sh and all of a sudden
On May 11, 2011, at 11:49 AM, Peter Dietz wrote:
This discussion is not about the ASync release anymore.
Quite true..
But, for developing DSpace, and people that build from source (since they've
got their own modifications to make), mvn + ant are excellent tools to do
that. For everyone
Hi Peter,
On 5/11/2011 1:49 PM, Peter Dietz wrote:
But, for developing DSpace, and people that build from source (since
they've got their own modifications to make), mvn + ant are excellent
tools to do that. For everyone who doesn't quite get maven, then we
should have easy to follow docs
On 11 May 2011 20:50, Tim Donohue tdono...@duraspace.org wrote:
I can definitely see you point about also improving documentation. But as
DSpace is now nearly 9 years old and we still haven't found easy enough
documentation, I'm not sure I'm in full agreement that we'll ever be able to
All,
Since it was mentioned, I'll put in a plug for the DSpace Easy
Installer work I've begun (but have since set aside till I can get back
to it). More below..
On 5/10/2011 9:23 AM, Mark H. Wood wrote:
On Tue, May 10, 2011 at 01:38:52PM +0100, Robin Taylor wrote:
[snip]
Whilst editing a
On May 10, 2011, at 5:38 AM, Robin Taylor wrote:
Apologies for starting this up again but...
Whilst I tend towards being in favour of Mark's proposal, I think there
is still a lot og grey areas so its important to keep the discussion
going.
Picking up on a couple of Peter's points...
On May 10, 2011, at 7:23 AM, Mark H. Wood wrote:
On Tue, May 10, 2011 at 01:38:52PM +0100, Robin Taylor wrote:
[snip]
Whilst editing a pom is an option for developers who are familiar with
the DSpace Maven infrastructure I think we need to come up something
much more user friendly. In the
Well, there are a couple of things to think about here:
We need to distinguish building and installing. Anyone is welcome to
build DSpace if he wish, but many sites don't really want to and
shouldn't need to. If you're not developing the stock DSpace code
then there should be no reason for you
On 10 May 2011 13:38, Robin Taylor robin.tay...@ed.ac.uk wrote:
In the UK at least most sites do not have a
dedicated repo developer. I also suspect most sites take the code from
the downloadable zip and never go near SVN. There is already a Jira
issue from the DCAT group asking for an
Hi Graham,
On 5/10/2011 11:17 AM, Graham Triggs wrote:
On 10 May 2011 13:38, Robin Taylor robin.tay...@ed.ac.uk
mailto:robin.tay...@ed.ac.uk wrote:
In the UK at least most sites do not have a
dedicated repo developer. I also suspect most sites take the code from
the downloadable
On Tue, May 10, 2011 at 08:56:04AM -0700, Mark Diggory wrote:
On May 10, 2011, at 7:23 AM, Mark H. Wood wrote:
On Tue, May 10, 2011 at 01:38:52PM +0100, Robin Taylor wrote:
[snip]
Whilst editing a pom is an option for developers who are familiar with
the DSpace Maven infrastructure I
On May 10, 2011, at 9:19 AM, Tim Donohue wrote:
Mark,
A few responses inline.
On 5/10/2011 10:51 AM, Mark Diggory wrote:
Hmm, so you would favor a custom installer that we would have to put
more resources into maintaining rather than a tried and true build
tool thats got tons of
Hi All,
Modules
The modularizing the DSpace codebase proposal is going to require project
restructuring. The benefits to us all is that unused modules (in my case
LNI, SWORD, JSPUI) can be disabled/dropped from my view of the project
all-together. And then on the positives, new developments in
On 5 May 2011 22:48, Tim Donohue tdono...@duraspace.org wrote:
I will state that I *completely* agree that we should have an open
development workspace for anyone (committers or non-committers) to
create their own Maven projects DSpace plugins. But, I think that is
*NOT* the same as what the
On Thu, May 05, 2011 at 04:48:52PM -0500, Tim Donohue wrote:
[snip]
On 5/5/2011 3:43 PM, Mark Diggory wrote:
[Quoting Tim Donohue, IIRC]
To be honest, I worry that jumping directly into technology
implementation ideas (git/github, etc.) only muddles things a bit.
I don't mean any offense
Hi All,
I'll take an initial stab at this. This is just my initial
thoughts/brainstorms, but I could be convinced otherwise :)
On 5/5/2011 10:15 AM, Robin Taylor wrote:
Hi all,
I just wanted to bring up one area that we didn't really touch on in the
developer meeting viz. the management of
Rather timely that you sent an email about this, as I was thinking a bit
more about this over lunch.
And in particular, about the issue of 'additional' modules and the spaghetti
dependencies between them and the projects of the official release [trunk].
Bottom line, is that I still believe that
On May 5, 2011 8:06 AM, Mark Diggory mdigg...@atmire.com wrote:
It would make for a better developer discussion.
On May 5, 2011, at 7:11 AM, Robin Taylor wrote:
Hi all,
I just wanted to bring up one area that we didn't really touch on in the
developer meeting viz. the management of
Mark All,
Although I welcome more discussion around Git/Github and whether or not
we'd like to move that direction, I feel we should try to avoid jumping
down to 'technological solutions' with these questions that Robin posed.
Robin can correct me if I'm wrong, but I feel Robin's questions
On 5 May 2011 17:27, Tim Donohue tdono...@duraspace.org wrote:
Robin can correct me if I'm wrong, but I feel Robin's questions were
more related to *policy decisions* from the Committers group. For
example, his first question could have been reworded as: What should be
our *policy* around
On May 5, 2011, at 9:27 AM, Tim Donohue wrote:
Mark All,
Although I welcome more discussion around Git/Github and whether or not we'd
like to move that direction, I feel we should try to avoid jumping down to
'technological solutions' with these questions that Robin posed.
Its hard,
On May 5, 2011, at 8:28 AM, Graham Triggs wrote:
Yes, it would start with the 'minimal' community supported, truly supported
release - which is trunk and doesn't have any reference to things that are
modules. But there could be subsequent separate release(s), that do bundle in
the
On May 5, 2011, at 1:14 PM, Graham Triggs wrote:
On 5 May 2011 17:27, Tim Donohue tdono...@duraspace.org wrote:
Robin can correct me if I'm wrong, but I feel Robin's questions were
more related to *policy decisions* from the Committers group. For
example, his first question could have been
Mark,
I feel like you and I may actually be coming at this from two different
directions. But I'm not sure, primarily because I'm not sure I fully
understand some of your ideas (see below for more)
On 5/5/2011 3:43 PM, Mark Diggory wrote:
Robin can correct me if I'm wrong, but I feel Robin's
41 matches
Mail list logo
