I'm back.
I spent some of my day today looking through the modeling website.
For starters, I migrated the whole thing to Git and it seems to work
on my local workstation. I don't foresee any difficult problems with
this migration. My preference is to effect this migration before the
deadline and move from there. If we do run into big challenges with
a website Git migration, we can talk about leniency.
To be clear, however, we're very serious about the December 21/2012
deadline.
I did noticed that there is a lot of content in the project-specific
directories that may be better suited elsewhere. There are, for
example, some articles that we might consider moving to /articles.
But that is something that we can address over time.
As a move-forward strategy, I'd like consider moving/adapting some
of the Modeling project-specific behaviour to the more general
project summary pages [1] and the upcoming replacement [2]. I think
that this will help us with some of the traditional access
management problems that we've had with modeling projects as the
configuration of these pages will be almost entirely a
content-management problem and not a coding problem.
I'm not targeting a solution for representing downloads/builds in
the short term, but do intend to focus on that in the new year. The
existing site can limp along until then.
Modeling projects that (requ|des)ire a custom website can still have
one, but I recommend moving that website to the web root (e.g.
/Xtext).
Does this make any sense?
Wayne
[1] http://eclipse.org/projects/project.php?id=modeling
[2] http://projects.eclipse.org/projects/modeling
On 11/27/2012 01:55 PM, Wayne Beaton wrote:
I have more to say... I hit "send" by accident.
I'll follow up on this insightful response shortly.
Wayne
On 11/27/2012 01:52 PM, Wayne Beaton wrote:
Hi Ed.
On 11/24/2012 12:12 AM, Ed Merks wrote:
Ed,
With the restructuring process (eliminating container projects
and terminating inactive projects, i.e., https://bugs.eclipse.org/bugs/show_bug.cgi?id=393682)
now underway, I've asked for some leniency in the migration
time frame for the website.
Personally, I'd prefer not to migrate all the out-of-date
baggage, but rather to start with something fresh in git.
I'll work with Wayne on how best to proceed.
Of course individual projects can choose to move at their own
pace and should migrate their source repos immediately if they
haven't already done so. Projects that don't do so
demonstrate that they are inactive and will be considered for
termination.
Regards,
Ed
On 23/11/2012 10:56 PM, Ed Willink wrote:
Hi
Many modeling projects currently share the common modeling
infrastructure hosted by www/modeling in CVS.
How is this being migrated to GIT?
Looking at /gitroot/www.eclipse.org, I can see that some
projects have independent repos: Xtext, emf/compare,
modeling/amalgam but most projects have no presence at all.
Assuming that no new infrastructure is going to be ready in
four weeks, shouldn't we just pick a date and move
www/modeling in it's entirety? When new infrastructure is
available projects can acquire their own repos.
Regards
Ed Willink
_______________________________________________
modeling-pmc mailing list
modeling-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/modeling-pmc
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse Projects
--
Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
Explore Eclipse
Projects
|