Because is basically a Sun Microsystem project and even if the
applications were FLOSS I doubt users could interact with the code.
Basically Sun Microsystem uses Collabnet infrastructure the same way
novell uses G-forge for their Novell-forge infrastructure.
If OOo was not a Sun Project I believe it would be more viable. Other
Sun-Collabnet projects include Java community project and I think the
OpenSolaris project (not sure).
http://community.java.net/
I do want to know if we can fix the DNS so we dont have the 'services'
that make the URL just way too long to use:
http://wiki.services.openoffice.org
http://qatrack.services.openoffice.org/
etc.
Also these apps could be costumize to look like the portal by doing some
work with the CSS. I think this could be a good thing for the overal
project.
Having mediawiki look like the OOo site would be cool to a degree I think.
On Fri, 14 Sep 2007 20:43:09 -0500, Shaun McDonald
<[EMAIL PROTECTED]> wrote:
Hi Louis,
I do wonder why an open source project uses a closed source
infrastructure! Surely it would be possible to get the community to have
total control of the system, using open source software. Then if there
are any problems, the community has full flexibility and creativity to
make changes.
Of course, you do need a gate keeper, and staging/testing server, to
make sure you don't get any random person making unwanted changes.
This of course is a rather radical view. However in the OpenStreetMap
project, who use this model with ruby on rails as the server, have many
contributors on the web site/apis etc.
Add to the list: anoncvs that will actually stay up to date all the time.
Shaun
On 14 Sep 2007, at 21:08, Louis Suarez-Potts wrote:
Hi all,
In parallel with enhancing the download process for endusers, [0] I'd
like to revisit the overall infrastructure requirements. You probably
recall this favourite page:
* http://wiki.services.openoffice.org/wiki/Infrastructure_Requirements
Basically, it's a wishlist of how we want things to be on OOo,
primarily from the contributors' perspective. I would like for us to
revisit it and update it, and see if we can finalize it. How will this
effort differ from the enduser pages redesign? Well, the one for
endusers focuses on making it easy (or at any rate easier) for endusers
to get OOo binaries in their language plus any other things they may
want, such as extensions, support, etc. This infrastructure effort is
focused on making it easier for developers (but also any other
contributor or user of OOo site) to do things.
I realize it's absurd to put a deadline on something like this but
consider this: with key new members to the community such as Redflag
and IBM, now is the time to clarify what we want. So, the sooner the
better, and if we can come up with a finalized list by 1 October, if
not sooner, that would be terrific (indeed, I fantasize this could be
done at OOoCon.)
What happens after the infrastructure requirements page is finalized?
Well, I envision that the ESC, which includes representatives of the
developers and stakeholders, can vote on it. That will then become the
document we can use. And if they could do this by early to mid
October, if not sooner....
Best,
Louis
[0] http://wiki.services.openoffice.org/wiki/User_Pages_Requirements
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
___________________________________________________________All new
Yahoo! Mail "The new Interface is stunning in its simplicity and ease of
use." - PC Magazinehttp://uk.docs.yahoo.com/nowyoucan.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Alexandro Colorado
CoLeader of OpenOffice.org ES
http://es.openoffice.org
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
