|
|
|
<mediawiki xmlns="http://www.mediawiki.org/xml/export-0.10/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mediawiki.org/xml/export-0.10/ http://www.mediawiki.org/xml/export-0.10.xsd" version="0.10" xml:lang="en">
|
|
|
|
|
|
|
|
` `<siteinfo>
|
|
|
|
` `<sitename>`Eclipsepedia`</sitename>
|
|
|
|
` `<dbname>`my_wiki`</dbname>
|
|
|
|
` `<base>[`https://wiki.eclipse.org/Main_Page`](https://wiki.eclipse.org/Main_Page)</base>
|
|
|
|
` `<generator>`MediaWiki 1.26.4`</generator>
|
|
|
|
` `
|
|
|
|
|
|
|
|
<case>
|
|
|
|
|
|
|
|
first-letter
|
|
|
|
|
|
|
|
</case>
|
|
|
|
|
|
|
|
` `<namespaces>
|
|
|
|
` `<namespace key="-2" case="first-letter">`Media`</namespace>
|
|
|
|
` `<namespace key="-1" case="first-letter">`Special`</namespace>
|
|
|
|
` `<namespace key="0" case="first-letter" />
|
|
|
|
` `<namespace key="1" case="first-letter">`Talk`</namespace>
|
|
|
|
` `<namespace key="2" case="first-letter">`User`</namespace>
|
|
|
|
` `<namespace key="3" case="first-letter">`User talk`</namespace>
|
|
|
|
` `<namespace key="4" case="first-letter">`Eclipsepedia`</namespace>
|
|
|
|
` `<namespace key="5" case="first-letter">`Eclipsepedia talk`</namespace>
|
|
|
|
` `<namespace key="6" case="first-letter">`File`</namespace>
|
|
|
|
` `<namespace key="7" case="first-letter">`File talk`</namespace>
|
|
|
|
` `<namespace key="8" case="first-letter">`MediaWiki`</namespace>
|
|
|
|
` `<namespace key="9" case="first-letter">`MediaWiki talk`</namespace>
|
|
|
|
` `<namespace key="10" case="first-letter">`Template`</namespace>
|
|
|
|
` `<namespace key="11" case="first-letter">`Template talk`</namespace>
|
|
|
|
` `<namespace key="12" case="first-letter">`Help`</namespace>
|
|
|
|
` `<namespace key="13" case="first-letter">`Help talk`</namespace>
|
|
|
|
` `<namespace key="14" case="first-letter">`Category`</namespace>
|
|
|
|
` `<namespace key="15" case="first-letter">`Category talk`</namespace>
|
|
|
|
` `</namespaces>
|
|
|
|
` `</siteinfo>
|
|
|
|
` `<page>
|
|
|
|
` `
|
|
|
|
|
|
|
|
<title>
|
|
|
|
|
|
|
|
Webmaster FAQ
|
|
|
|
|
|
|
|
</title>
|
|
|
|
|
|
|
|
` `<ns>`0`</ns>
|
|
|
|
` `<id>`1294`</id>
|
|
|
|
` `<revision>
|
|
|
|
` `<id>`422642`</id>
|
|
|
|
` `<parentid>`383284`</parentid>
|
|
|
|
` `<timestamp>`2018-02-12T18:24:04Z`</timestamp>
|
|
|
|
` `<contributor>
|
|
|
|
` `<username>`Webmaster.eclipse.org`</username>
|
|
|
|
` `<id>`159`</id>
|
|
|
|
` `</contributor>
|
|
|
|
` `<model>`wikitext`</model>
|
|
|
|
` `<format>`text/x-wiki`</format>
|
|
|
|
` `<text xml:space="preserve" bytes="14387">`Something bothering you about the eclipse.org infrastructure? Something not running right? Please read these FAQ's before contacting webmaster@eclipse.org.`
|
|
|
|
|
|
|
|
## Getting the news, reading the mail
|
|
|
|
|
|
|
|
### How do I access the Eclipse newsgroups?
|
|
|
|
|
|
|
|
Our original NNTP style newsgroups have been replaced by web based
|
|
|
|
[forums](https://www.eclipse.org/forums)
|
|
|
|
|
|
|
|
You will need an Eclipse account to post messages, and you will be
|
|
|
|
automatically re-directed to the login page when you use the post
|
|
|
|
option.
|
|
|
|
|
|
|
|
### How do I unsubscribe from a mailing list or change my mailing list options?
|
|
|
|
|
|
|
|
You can manage you mailing list subscriptions by logging in to your
|
|
|
|
Eclipse.org [account](https://accounts.eclipse.org) and looking under
|
|
|
|
the 'mailing lists' tab.
|
|
|
|
|
|
|
|
### Do I have to unsubscribe to the mailing list if my email address changes?
|
|
|
|
|
|
|
|
A. No, if you update your Eclipse.org
|
|
|
|
[account](https://accounts.eclipse.org) email address it will attempt to
|
|
|
|
update all of your subscribed mailing lists once you have confirmed the
|
|
|
|
change.
|
|
|
|
|
|
|
|
### I sent an e-mail to the list, but it got rejected. What gives?
|
|
|
|
|
|
|
|
A. You must subscribe to the list before sending e-mail to it. You must
|
|
|
|
also use the same e-mail address in your mail client, otherwise our list
|
|
|
|
software won't recognize you. Please note that lists ending in -dev,
|
|
|
|
such as eclipse-dev, are intended for Eclipse developers working on a
|
|
|
|
specific project, and should not be used for general information.
|
|
|
|
|
|
|
|
### I sent an e-mail to the list, but it's not appearing in the archives. Why?
|
|
|
|
|
|
|
|
A. The list and group archives are generated hourly, so just wait a bit.
|
|
|
|
If the server load is too high when the archiving process starts, it
|
|
|
|
will abort and wait another hour.
|
|
|
|
|
|
|
|
## Reporting bugs
|
|
|
|
|
|
|
|
### Is the username and password that I use to access Bugzilla the same one used to access the mailing lists?
|
|
|
|
|
|
|
|
No. You can request an Eclipse account on [this
|
|
|
|
page](https://dev.eclipse.org/site_login/).
|
|
|
|
|
|
|
|
### Help! I've forgotten my password.
|
|
|
|
|
|
|
|
A. [The Eclipse.org account page](https://accounts.eclipse.org) has
|
|
|
|
everything you need.
|
|
|
|
|
|
|
|
### How do I change the email address that I use to login to Bugzilla?
|
|
|
|
|
|
|
|
A. Go to [My Account](https://accounts.eclipse.org)
|
|
|
|
|
|
|
|
## Help Using Eclipse
|
|
|
|
|
|
|
|
### I need help using Eclipse - where should I send my question?
|
|
|
|
|
|
|
|
A. The [forums](http://www.eclipse.org/forums/) are the best place to
|
|
|
|
post a question about using Eclipse. Please don't send questions
|
|
|
|
regarding using Eclipse to the mailing lists. They are typically used
|
|
|
|
for development discussions.
|
|
|
|
|
|
|
|
### Can you send me a list of books about Eclipse?
|
|
|
|
|
|
|
|
A. A list of Eclipse books is available on the community page under the
|
|
|
|
[Sources of Eclipse information](http://www.eclipse.org/community/)
|
|
|
|
heading.
|
|
|
|
|
|
|
|
### Is there an Eclipse FAQ?
|
|
|
|
|
|
|
|
A. See the [Official Eclipse FAQs](Official_Eclipse_FAQs "wikilink") on
|
|
|
|
this Wiki, or look at other FAQs on the [Main
|
|
|
|
Page](Main_Page "wikilink")
|
|
|
|
|
|
|
|
### I get Access Forbidden for a project's update site/p2 repository
|
|
|
|
|
|
|
|
A. Update sites are typically not browseable. The Eclipse Update Manager
|
|
|
|
knows to look for a file within that directory.
|
|
|
|
|
|
|
|
## Getting Eclipse - Downloads and Mirrors
|
|
|
|
|
|
|
|
### How do I become an Eclipse mirror?
|
|
|
|
|
|
|
|
A. Please follow [these
|
|
|
|
instructions](http://www.eclipse.org/downloads/mir_request.php).
|
|
|
|
|
|
|
|
### Help! I can't seem to download - my download stops at 99% and never completes.
|
|
|
|
|
|
|
|
A. Disable real time virus scanning while you download.
|
|
|
|
|
|
|
|
### I don't have broadband. Where can I get Eclipse on a CD?
|
|
|
|
|
|
|
|
A. Many sites offer Eclipse Distributions -
|
|
|
|
[Yoxos](http://www.yoxos.com) is one of them.
|
|
|
|
|
|
|
|
### I've downloaded Eclipse several times and it seems to be corrupt. Is the archive valid?
|
|
|
|
|
|
|
|
A. Yes, the archive is valid. Please remove all temporary files that
|
|
|
|
were created during the download and try again.
|
|
|
|
|
|
|
|
### I can't seem to download Eclipse from a mirror X. Is there a problem with this mirror?
|
|
|
|
|
|
|
|
A. We only administer eclipse.org servers. If you have a specific
|
|
|
|
problem with another mirror, please contact the webmaster of that
|
|
|
|
mirror.
|
|
|
|
|
|
|
|
## Creating new projects
|
|
|
|
|
|
|
|
### I want to create a new project. What do I do?
|
|
|
|
|
|
|
|
A. Please view this page: [Dev
|
|
|
|
Process](http://www.eclipse.org/projects/dev_process/)
|
|
|
|
|
|
|
|
## Eclipse Source Code
|
|
|
|
|
|
|
|
### Where can I download the Eclipse source code?
|
|
|
|
|
|
|
|
A. Use a Git client such as [eGit](http://eclipse.org/egit) and connect
|
|
|
|
to our [Git repositories](http://git.eclipse.org/c/).
|
|
|
|
|
|
|
|
## Committers
|
|
|
|
|
|
|
|
### I need commit access to Plugin XYZ. Can I have it?
|
|
|
|
|
|
|
|
A. Before granting access, I need PMC and/or Project Lead approval, as
|
|
|
|
well as a list of projects you need access to. I don't know that XYZ
|
|
|
|
plugin requires access to org.eclipse.zzc and org.eclipse.yyz, so be as
|
|
|
|
explicit as you can.
|
|
|
|
|
|
|
|
### I can't connect to Git anymore
|
|
|
|
|
|
|
|
A. If you're using ssh and you're getting connection timeout errors,
|
|
|
|
your IP address may be blocked or blacklisted on our firewall due to a
|
|
|
|
perceived attack (too many bad logins, trying to login using an invalid
|
|
|
|
user ID, etc). Contact the webmaster@eclipse.org, and don't forget to
|
|
|
|
specify your Internet-facing IP address ([can be obtained
|
|
|
|
here](http://whatismyip.org/))
|
|
|
|
|
|
|
|
### I need to change a web page. Can I?
|
|
|
|
|
|
|
|
A. If the page is a project page to which you are a committer, I can
|
|
|
|
grant you access to the website if the PMC/Project Lead agrees.
|
|
|
|
|
|
|
|
### How do I update help.eclipse.org?
|
|
|
|
|
|
|
|
A. Send a note to Webmaster telling us the name of your help plugin and
|
|
|
|
where we can find it on download.eclipse.org. We'll copy it over to the
|
|
|
|
help server and re-start things.
|
|
|
|
|
|
|
|
B. As part of the release train someone usually opens a bug called
|
|
|
|
something like 'Will soon need a \$release_name Info center'. You can
|
|
|
|
update that bug with your plugins and we'll add them to the help server.
|
|
|
|
|
|
|
|
### I need to add/remove.change a version/milestone/component in Bugzilla. How do I do this?
|
|
|
|
|
|
|
|
A. Committers can access the Bugzilla manager in [My
|
|
|
|
Account](https://dev.eclipse.org/site_login/myaccount.php) to edit
|
|
|
|
Bugzilla. But there are some things you should know first:
|
|
|
|
|
|
|
|
- Only the Project Leads or PMCs for projects can grant committers the
|
|
|
|
ability to edit bugzilla data.
|
|
|
|
- Edit access only aplies to one specific project. In other words: if
|
|
|
|
the platform PMC gave you access, it does not mean you can edit the
|
|
|
|
birt bugzilla data, you can only edit the platform bugzilla data. If
|
|
|
|
you convince the Birt PLs to give you access then you can edit both.
|
|
|
|
- You can't delete anything. This allows us to prevent the database from
|
|
|
|
corrupting.
|
|
|
|
- You can add as many versions and milestones as you like, but you can't
|
|
|
|
edit them once they have been created.
|
|
|
|
- Once you have submitted a new component, you can't change the name.
|
|
|
|
You can change everything else about it though.
|
|
|
|
- All email address must be valid bugzilla accounts.
|
|
|
|
|
|
|
|
If you are a Project Lead or PMC member the first item you will see is a
|
|
|
|
drop down box that contains all of the projects you are in charge of. By
|
|
|
|
selecting one of the projects and clicking the 'Edit' button you will be
|
|
|
|
presented with the known list of comitters and you can then procede to
|
|
|
|
grant and revoke access to your bugzilla components.
|
|
|
|
|
|
|
|
To change the access status of a committer simlpy click on their name
|
|
|
|
and watch for the checkmark to change in the 'Edit Bugs' column. To save
|
|
|
|
your changes just click the 'Save Changes' button.
|
|
|
|
|
|
|
|
If you are a committer that has been granted bugzilla edit privileges,
|
|
|
|
or a PL or PMC there will be a drop box containing all of the projects
|
|
|
|
you have access to. By selecting a project from this list and clickeing
|
|
|
|
the 'Edit' button you will be taken to the main bugzilla page for that
|
|
|
|
project.
|
|
|
|
|
|
|
|
The main page conatains the basic information about the project. Namely:
|
|
|
|
|
|
|
|
- A description of the project.
|
|
|
|
- The maximum number of votes per user.
|
|
|
|
- The maximum number of votes a single bug can have.
|
|
|
|
- The number of votes required to confirm a bug automatically
|
|
|
|
- The default milestone for the project.
|
|
|
|
|
|
|
|
You can edit all of these details on the main page, and you can save
|
|
|
|
them by clicking the 'Make Changes; button.
|
|
|
|
|
|
|
|
The other things located on the main pages are links to pages that will
|
|
|
|
allow you to:
|
|
|
|
|
|
|
|
- Edit/add components
|
|
|
|
- Add new versions
|
|
|
|
- Add new milestones.
|
|
|
|
|
|
|
|
Dealing with components:
|
|
|
|
|
|
|
|
The main components page show you a list of all of your current
|
|
|
|
components, their description, default owner(who gets the email whan a
|
|
|
|
bug is filed) and the default QA contact.
|
|
|
|
|
|
|
|
If you want to edit a component just click on it's name and you will be
|
|
|
|
able to change any details, excluding the name. Just click the 'Save
|
|
|
|
Changes' button when your done.
|
|
|
|
|
|
|
|
Adding a component is the same as editing except yo ucan pick the name
|
|
|
|
you want.
|
|
|
|
|
|
|
|
- NOTE: All given email addresses must be for valid bugzilla accounts,
|
|
|
|
or else you will get an error.
|
|
|
|
|
|
|
|
Dealing with milestones:
|
|
|
|
|
|
|
|
The only thing to remember is that milestones, unlike versions require a
|
|
|
|
'sort' key. This numeric value is used to order the list of milestones
|
|
|
|
you see in bugzilla.
|
|
|
|
|
|
|
|
#### Project Inboxes
|
|
|
|
|
|
|
|
It is a common practice for Eclipse projects to set a *project inbox* as
|
|
|
|
the default assignee for new bugs. Inboxes generally take the form of
|
|
|
|
\<project\>.\<component\>-inbox@eclipse.org (e.g.
|
|
|
|
equinox.framework-inbox@eclipse.org, or equinox-inbox@eclipse.org). Any
|
|
|
|
messages sent to this email address are discarded.
|
|
|
|
|
|
|
|
In the Bugzilla preferences, any user can opt to be copied whenever
|
|
|
|
email is sent to a particular email address. This makes it easy for any
|
|
|
|
user (i.e. community member) to monitor bug activity against a
|
|
|
|
particular dummy inbox. Further, this sort of arrangement is resilient
|
|
|
|
to change as there is never any need to change the inbox (individual
|
|
|
|
default assignees can change frequently).
|
|
|
|
|
|
|
|
Some projects opt to have a different dummy inbox for each Bugzilla
|
|
|
|
component. Some have a single inbox for all components. How you use
|
|
|
|
inboxes is a project decision. If you have any questions, check with
|
|
|
|
your PMC for advice.
|
|
|
|
|
|
|
|
You can request that an inbox be created by sending a note to
|
|
|
|
webmaster@eclipse.org
|
|
|
|
|
|
|
|
### I asked the webmaster to do something. When will it get done?
|
|
|
|
|
|
|
|
A. Here's how webmasters handle their workload, in order of priority.
|
|
|
|
|
|
|
|
1. Infrastructure issues causing outage or performance loss of any
|
|
|
|
kind, or that can potentially cause outage or performance loss
|
|
|
|
(kernel updates, security advisories, monitoring, enforcing proper
|
|
|
|
usage of resources, etc).
|
|
|
|
2. Issues blocking committers from working: password resets,
|
|
|
|
permissions, locked accounts, firewall issues, slow performance,
|
|
|
|
etc.
|
|
|
|
3. Other committer/project issues: new Git or bugzilla components, new
|
|
|
|
project provisioning, new lists or groups for projects, new account
|
|
|
|
provisioning, helping committers get up and going, project
|
|
|
|
reorganizations, etc.
|
|
|
|
4. General community requests that don't involve infrastructure change,
|
|
|
|
forwarding e-mail, fixing broken links, etc.
|
|
|
|
5. Enhancement requests and infrastructure changes not covered by the
|
|
|
|
above, and for which enough community support warrants its
|
|
|
|
execution: anything in bugzilla, ordered by priority, enhancements
|
|
|
|
last. Anything in this pile can be brought up higher (or lower) by
|
|
|
|
Committer/community support, or PMCs.
|
|
|
|
|
|
|
|
***Some notes:***
|
|
|
|
|
|
|
|
:\* We encourage folks to use Bugzilla for infra requests.
|
|
|
|
|
|
|
|
:\* Folks who are not happy with where their priority 4. (or higher
|
|
|
|
numerically) requests are in the queue can gather PMC support and/or
|
|
|
|
committer support to increase the priority.
|
|
|
|
|
|
|
|
:\* Folks should understand that if a priority 5 is bumped up to
|
|
|
|
priority 3, it will have an impact on everything else in 3., 4. and 5.
|
|
|
|
Likewise, if everyone wants everything at priority 3., it all looks the
|
|
|
|
same to us.
|
|
|
|
|
|
|
|
## Eclipse.org infrastructure
|
|
|
|
|
|
|
|
### What software does eclipse.org use on its servers?
|
|
|
|
|
|
|
|
A. Linux, and an assortment of Open Source Goodies.
|
|
|
|
|
|
|
|
### You're running Something-1.0.2. Why don't you use SomeOtherThing-3.4.5 instead?
|
|
|
|
|
|
|
|
### You're not using plugin-0.99/extension-4.98 for Something-1.0.2, why not?
|
|
|
|
|
|
|
|
A. There are many reasons we use the software we do. Here's a short
|
|
|
|
list:
|
|
|
|
|
|
|
|
- Because we've been using it for years, and switching to something new
|
|
|
|
may require more effort than the actual benefit.
|
|
|
|
- It's proven its stability in mission-critical environments, under
|
|
|
|
heavy load.
|
|
|
|
- It's well-understood and easy to maintain.
|
|
|
|
- It is known to perform well under load.
|
|
|
|
- It's part of our core OS. It's much easier to upgrade and maintain
|
|
|
|
software that's bundled with the OS.
|
|
|
|
- Works well in a clustered environment, making it stable, scalable and
|
|
|
|
redundant.
|
|
|
|
- Because. Just because.
|
|
|
|
|
|
|
|
There are many reasons we don't run some software. Here's a short list:
|
|
|
|
|
|
|
|
- It's not part of the above list of reasons.
|
|
|
|
- Because the projects hosted at eclipse.org haven't asked, or don't
|
|
|
|
feel the need for it.
|
|
|
|
- Because it's not enterprise-level. We install the least amount of
|
|
|
|
hacked and compiled software.
|
|
|
|
- Because it's too hard to maintain. Sure, installing it is easy, but
|
|
|
|
can it stay up 24/7/365 under heavy load?
|
|
|
|
- Because it doesn't run in a load-balanced environment. We don't set up
|
|
|
|
services on one server, that doesn't scale.
|
|
|
|
- Because it's a security risk, and Webmasters don't like getting up at
|
|
|
|
3:00am to fix problems.
|
|
|
|
- Because we haven't had time to look into it yet.
|
|
|
|
- Because. Just because.
|
|
|
|
|
|
|
|
### You should install Xyz 1.0.2. It's way cool and it only took me 15 minutes to install on my basement server.
|
|
|
|
|
|
|
|
A. When your basement server averages hundreds of concurrent connections
|
|
|
|
365 days/year, get back to me.
|
|
|
|
|
|
|
|
### Why don't you use wiki namespaces?
|
|
|
|
|
|
|
|
A. There are a couple of answers
|
|
|
|
|
|
|
|
- If Wikipedia doesn't need namespaces to serve up 2 million plus pages
|
|
|
|
then we probably don't either
|
|
|
|
- The ongoing overhead of maintaining the namespaces is not currently
|
|
|
|
offset by the limited application and benefit.
|
|
|
|
|
|
|
|
## Contacting the WebMaster
|
|
|
|
|
|
|
|
### How can I get the quickest response from the WebMaster?
|
|
|
|
|
|
|
|
A. When contacting the WebMaster, please include a detailed message,
|
|
|
|
with as much technical information as possible:
|
|
|
|
|
|
|
|
- for broken links include the URL of the page that contains a bad link.
|
|
|
|
- for problems downloading files: indicate which file and the name of
|
|
|
|
the mirror
|
|
|
|
- for information on Eclipse builds, troubleshooting, How-Tos, and
|
|
|
|
plugins, check our Forums and subscribe to the mailing lists (see
|
|
|
|
above)
|
|
|
|
|
|
|
|
### How do I contact the WebMaster?
|
|
|
|
|
|
|
|
A. Just e-mail webmaster@eclipse.org. We'll try our best to respond as
|
|
|
|
quickly as we can.
|
|
|
|
|
|
|
|
</text>
|
|
|
|
|
|
|
|
` `<sha1>`t4qa2bqtfrdodjczm6serul6e3ts5r6`</sha1>
|
|
|
|
` `</revision>
|
|
|
|
` `</page>
|
|
|
|
|
|
|
|
</mediawiki>
|
|
|
|
|
|
|
|
[Category:FAQ](Category:FAQ "wikilink") |