Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » General (non-technical) » Eclipse Foundation » [PROJECT] - Collaboration and Government Infrastructure (CAGI)
[PROJECT] - Collaboration and Government Infrastructure (CAGI) [message #2676] Sun, 10 October 2004 05:45 Go to next message
Eclipse UserFriend
Originally posted by: ilias.lazaridis.com

The Eclipse Foundation most important project is... not existent!

The "Collaboration and Government Infrastructure" project.

This project would implement a systems similar to SourceCast, with additional modules dealing with the governance issues of a fast growing, large scale open source system like the eclipse foundation.

Examples modules:
- forums (mailinglist, newsgroups, html-groups)
- CVS
- CMS for project content
- Meeting
- ...

*JAVA*
The project would use available java solutions (prefered) or write java-wrappers to existing non-java solutions (should be avoided).

Focusing on java technology enables easy integration of functionality into the eclipse IDE, increasing efficiency of the developement process.

*self-hosting*
- Eclipse would have a project where many other eclipse.projects would be used for developement.
- By using j2EE/EJB: the webtools project, Pollinate
- BIRT project for reporting
- TPTP
- ...

*self-hosting RCP*
- The project would result additionally in an RCP-application, which would have a much more convenient GUI than a web-based collaboration system.

Possible contributors for this project would be:
- JAVA Open-Source projects
- The hosted eclipse projects
- Vendors like SourceCast
- Webhosting providers
- ensuring solution can be easily hosted @providers
- increasing use of java technology
- ...

-

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!

-

Some more information:

Re: [ECLIPSE.ORG] Issues - [was: Re: BIRT Charter Approved]
http://www.eclipse.org/newsportal/article.php?id=30245&g roup=eclipse.platform

..

--
http://lazaridis.com
Re: [PROJECT] - Collaboration and Government Infrastructure (CAGI) [message #3072 is a reply to message #2676] Sun, 10 October 2004 19:56 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: pkorros.bigfoot.com

This is a great idea!

Currently eclipse lacks common structure/infrastructure for all projects.

Many projects use different mechanisms to address the same problems
(e.g. downloads, planning).
The eclipse website has many navigational problems. The downloads link
allows to download only the Eclipse SDK/Platform, it should also allow
downloading of other eclipse project downloads like EMF,XSD etc.

Many projects (especially new ones) are not OPEN enough. eg. they don't
have meeting notes in their web sites, they don't have published plans.

I think that a project like this could help the eclipse foundation to
gain consistent look and functionality across all projects.

ilias wrote:
> The Eclipse Foundation most important project is... not existent!
>
> The "Collaboration and Government Infrastructure" project.
>
> This project would implement a systems similar to SourceCast, with
> additional modules dealing with the governance issues of a fast growing,
> large scale open source system like the eclipse foundation.
>
> Examples modules:
> - forums (mailinglist, newsgroups, html-groups)
> - CVS
> - CMS for project content
> - Meeting
> - ...
>
> *JAVA*
> The project would use available java solutions (prefered) or write
> java-wrappers to existing non-java solutions (should be avoided).
>
> Focusing on java technology enables easy integration of functionality
> into the eclipse IDE, increasing efficiency of the developement process.
>
> *self-hosting*
> - Eclipse would have a project where many other eclipse.projects would
> be used for developement.
> - By using j2EE/EJB: the webtools project, Pollinate
> - BIRT project for reporting
> - TPTP
> - ...
>
> *self-hosting RCP*
> - The project would result additionally in an RCP-application, which
> would have a much more convenient GUI than a web-based collaboration
> system.
>
> Possible contributors for this project would be:
> - JAVA Open-Source projects
> - The hosted eclipse projects
> - Vendors like SourceCast
> - Webhosting providers
> - ensuring solution can be easily hosted @providers
> - increasing use of java technology
> - ...
>
> -
>
> 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!
>
> -
>
> Some more information:
>
> Re: [ECLIPSE.ORG] Issues - [was: Re: BIRT Charter Approved]
> http://www.eclipse.org/newsportal/article.php?id=30245&g roup=eclipse.platform
>
>
> .
>
Re: [PROJECT] - Collaboration and Government Infrastructure (CAGI) [message #4257 is a reply to message #3072] Fri, 15 October 2004 21:42 Go to previous messageGo to next message
Mike Milinkovich is currently offline Mike MilinkovichFriend
Messages: 260
Registered: July 2009
Senior Member
We do hope to create a project similar to this in the future. Currently we
are moving the Eclipse IT infrastructure and hopefully acquiring some new
hardware. 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.

It will likely be a few months before we start thinking about how to
significantly enhance the website content and processes. 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. We feel that we cannot
afford the risk of a major interruption to our developers or community.

/mike
--------------------
Mike Milinkovich
Executive Director,
Eclipse Foundation

"Panagiotis Korros" <pkorros@bigfoot.com> wrote in message
news:ckc3qu$iml$1@eclipse.org...
> This is a great idea!
>
> Currently eclipse lacks common structure/infrastructure for all projects.
>
> Many projects use different mechanisms to address the same problems
> (e.g. downloads, planning).
> The eclipse website has many navigational problems. The downloads link
> allows to download only the Eclipse SDK/Platform, it should also allow
> downloading of other eclipse project downloads like EMF,XSD etc.
>
> Many projects (especially new ones) are not OPEN enough. eg. they don't
> have meeting notes in their web sites, they don't have published plans.
>
> I think that a project like this could help the eclipse foundation to
> gain consistent look and functionality across all projects.
>
> ilias wrote:
> > The Eclipse Foundation most important project is... not existent!
> >
> > The "Collaboration and Government Infrastructure" project.
> >
> > This project would implement a systems similar to SourceCast, with
> > additional modules dealing with the governance issues of a fast growing,
> > large scale open source system like the eclipse foundation.
> >
> > Examples modules:
> > - forums (mailinglist, newsgroups, html-groups)
> > - CVS
> > - CMS for project content
> > - Meeting
> > - ...
> >
> > *JAVA*
> > The project would use available java solutions (prefered) or write
> > java-wrappers to existing non-java solutions (should be avoided).
> >
> > Focusing on java technology enables easy integration of functionality
> > into the eclipse IDE, increasing efficiency of the developement process.
> >
> > *self-hosting*
> > - Eclipse would have a project where many other eclipse.projects would
> > be used for developement.
> > - By using j2EE/EJB: the webtools project, Pollinate
> > - BIRT project for reporting
> > - TPTP
> > - ...
> >
> > *self-hosting RCP*
> > - The project would result additionally in an RCP-application, which
> > would have a much more convenient GUI than a web-based collaboration
> > system.
> >
> > Possible contributors for this project would be:
> > - JAVA Open-Source projects
> > - The hosted eclipse projects
> > - Vendors like SourceCast
> > - Webhosting providers
> > - ensuring solution can be easily hosted @providers
> > - increasing use of java technology
> > - ...
> >
> > -
> >
> > 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!
> >
> > -
> >
> > Some more information:
> >
> > Re: [ECLIPSE.ORG] Issues - [was: Re: BIRT Charter Approved]
> >
http://www.eclipse.org/newsportal/article.php?id=30245&g roup=eclipse.platform
> >
> >
> > .
> >
Re: [PROJECT] - Collaboration and Government Infrastructure (CAGI) [message #5404 is a reply to message #4257] Mon, 18 October 2004 14:38 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: ilias.lazaridis.com

On Fri, 15 Oct 2004 17:42:34 -0400, Mike Milinkovich
<mike.milinkovich@eclipse.org> 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
Re: [PROJECT] - Collaboration and Government Infrastructure (CAGI) [message #5738 is a reply to message #5404] Wed, 27 October 2004 19:30 Go to previous messageGo to next message
Mike Milinkovich is currently offline Mike MilinkovichFriend
Messages: 260
Registered: July 2009
Senior Member
It is "hopefully" because we are asking for hardware and software donations
from several corporations. Until we have confirmation of what (if anything)
we are getting and when it will be arriving, we cannot complete our plans.

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

Why "hopefully"?
Re: [PROJECT] - Collaboration and Government Infrastructure (CAGI) [message #5773 is a reply to message #5738] Thu, 28 October 2004 10:12 Go to previous message
Eclipse UserFriend
Originally posted by: ilias.lazaridis.com

On Wed, 27 Oct 2004 15:30:02 -0400, Mike Milinkovich
<mike.milinkovich@eclipse.org> wrote:

>>> Currently we are moving the Eclipse IT infrastructure
>>> and hopefully acquiring some new hardware.
>>
>> Why "hopefully"?
>
> It is "hopefully" because we are asking for hardware and software
> donations from several corporations.

The eclipse foundation is _not_ a small group of Open Source People.

It is a consortium of strong industry leaders.

It should not depend on donations for keeping things running.

And it does not:

Due to my latest information, the 2004 budget should have a surplus of
$400.000.

"
Budget overview
The Board reviewed and approved the 2004 budget as provided by the EMO.
The 2004 budget is based on expectations of $1.6M in membership revenue,
and approximately $1.2M in expenses.
The surplus will be carried forward to assist in funding
operations in 2005.
"
http://eclipse.org/org/board/minutes/2004_06_25%20Abridged%2 0Minutes.pdf

> Until we have confirmation of what (if anything)
> we are getting and when it will be arriving, we cannot complete our
> plans.

What is the hardware/software you are asking for?

Which are those plans?

You should inform the community about this.

-

[ As a sidenote: please acknowledge the receipt of this letter:
http://www.eclipse.org/newsportal/article.php?id=100&gro up=eclipse.foundation
]

..

--
http://lazaridis.com
Previous Topic:Running Eclipse 3.0.1 under Windows XP
Next Topic:EclipseCon Exhibitor and Sponsorship Information
Goto Forum:
  


Current Time: Fri Apr 19 01:20:16 GMT 2024

Powered by FUDForum. Page generated in 0.02487 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top