[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Newsgroup Home]
[News.eclipse.foundation] Re: [PROJECT] - Collaboration and Government Infrastructure (CAGI)

On Fri, 15 Oct 2004 17:42:34 -0400, Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx> wrote:

We do hope to create a project similar to this in the future.

Where you can act, hope is not enouth!

Currently we are moving the Eclipse IT infrastructure
and hopefully acquiring some new hardware.

Why "hopefully"?

So our focus for the next little while is going to be on
re-implementing our current function in a new environment while maintaining stability and performance.

Based on the announcements, this should be solved within the first november week.
[moving servers to new location (www.magma.ca) on 2004-10-30 + 1 week trouble solving]


It will likely be a few months before we start thinking about how to
significantly enhance the website content and processes.

Please provide the resources, thus the community can start thinking & interacting immediately.


See my concrete suggestions below [1].

Perhaps we are being overly conservative,
but we feel that we need to keep the number of
moving parts to a minimum while we migrate our site.

This is a basic requirement.

We feel that we cannot
afford the risk of a major interruption to our developers or community.

This is a basic requirement.

-

My suggestions are not contrary to the stated basic requirements.

Even more: they would ensure keeping those requirements would be kept
(context: community/developers which use the infrastructure)

-

[1]

Suggestions, 1st priority:

"Community" Product in Bugzilla
https://bugs.eclipse.org/bugs/show_bug.cgi?id=57040

Thus the community can start filing Issues affecting the
Infrastructure.

-

Suggestions, 2nd priority:

As the creation of an eclipse project takes some time, possibly a first step should be made within the technology project (subproject, category incubation )

This would allow to start earlier on such a project (for/during the
eclipse.org transfer IBM = > eclipse Foundation (http://www.magma.ca)
).

Another possibility would be, to create a subproject "www-transfer"
within platform (which seems to manage website related stuff anyway)
- place all code/files in CVS (mailinglist configuration files, scripts, website, ...)
- discuss and decide about smooth, quick and save transistions.
- let the community (and its experience) assist with those transistions.


Most important:
- let the community have (at least some) influence on resources they
have to use!

.

--
http://lazaridis.com