Jump to: navigation, search

Difference between revisions of "Modeling Project Releng/Website Maintenance"

m (Build UI)
m (Homepage Copy)
Line 1: Line 1:
 
==Homepage Copy==
 
==Homepage Copy==
  
Component owners can edit their own website copy if they are members of the group '''<code>modeling-home</code>'''. If they're not they can open a [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=community&component=CVS bug], cc: their PMC for approval, and request access from the webmaster.
+
Component owners can edit their own website copy if they are members of the group '''<code>modeling-home</code>'''. If they're not they can open a [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=community&component=CVS bug], cc: their PMC for approval, and request access from the webmaster. You r bug could, for example, be called:
 +
 
 +
Please add user jcote to group modeling-home for website maintenance
  
 
To edit website copy, check out the web content module from <code>/cvsroot/org.eclipse</code>:
 
To edit website copy, check out the web content module from <code>/cvsroot/org.eclipse</code>:
Line 18: Line 20:
  
 
Note that there's at least a 30-second lag before content appears after committing new files or changes.
 
Note that there's at least a 30-second lag before content appears after committing new files or changes.
 
  
 
==Build UI==
 
==Build UI==

Revision as of 10:51, 4 January 2008

Homepage Copy

Component owners can edit their own website copy if they are members of the group modeling-home. If they're not they can open a bug, cc: their PMC for approval, and request access from the webmaster. You r bug could, for example, be called:

Please add user jcote to group modeling-home for website maintenance

To edit website copy, check out the web content module from /cvsroot/org.eclipse:

www/modeling/emft/componentName

Then look at these files:

project-info/project-page-paragraph.html (short blurb)
project-info/overview.html (detailed page)

As to what content can be put on the site, look at other Modeling project components for examples:

Note that there's at least a 30-second lag before content appears after committing new files or changes.

Build UI

As above, content lives in /cvsroot/org.eclipse/www/modeling/emft/projectName. Copy these three files over from some other component's build/ folder, then edit _common.php to suit your needs.

build/_common.php (contains shared properties)
build/index.php (to run a build)
build/promo.php (to promote a build)

Adding new dependencies

  • If your build depends on a newer version of a component that is listed, just add the URL in the empty box below the list of already-defined URLs, and your build will use that new one. You can add several at once. You can also add dependencies without actually running a build by first clicking the 'preview build' button on the top-right corner of your build page, then running a "Preview Build". This will not run a build, it will only show you the command that will be run. If you're not sure what all the build options do, this is one way to explore them.

Site Navigation

So that your component is properly listed and will appear on the homepage, downloads, release notes, be sure to edit your parent project's _projectCommon.php file, eg. /cvsroot/org.eclipse/www/modeling/emft/_projectCommon.php.

Be sure you add yourself to these arrays, as appropriate:

$projects = array( ... );
$cvscoms = array( ... );
$nodownloads = array(); //components with no downloads available yet
$nonewsgroup = array(); //components without newsgroup
$nomailinglist = array(); //components without mailinglist
$incubating = array( ... ); // incubating components (everyone starts here)


Previewing / Testing


Updating Build Server

Once your changes are in CVS, contact your build server admin and point him here.