[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[phoenix-dev] Phoenix Developer FAQ
|
For those who don't yet see the difference between the
eclipse.org-common directory and the other CVS directories, this
humourous FAQ should help.
Q: I made changes in eclipse.org-common. Can I put them on the website NOW?
A: No.
Q: I made a small change to the stylesheet. Can we put that live NOW?
A: No.
Q: I have a small bug in something in eclipse.org-common. If I fix it,
can you put it live NOW?
A: No.
Q: I just added a bunch of nifty changes in eclipse.org-common. Really
cool stuff. I want to use it now. Can you put it live NOW?
A: No.
Q: Why do you keep saying "No"?
A: Because changes in eclipse.org-common affect the entire website, and
should be tested thoroughly before going live. Messing up your web page
is okay. Messing up the entire site is not.
Q: I should be able to commit to the live eclipse.org-common HEAD as we
please. If I break something, I'll fix it fast, promise.
A: The WebMaster doesn't run Apache from HEAD, Bugzilla from HEAD, Linux
Kernel from HEAD, or even Eclipse from HEAD. He won't run Phoenix from
HEAD either.
Q: I want to write a piece of code that everyone can use, even the
projects. Do I have to put it in eclipse.org-common?
A: You should. That's what it's there for.
Q: Can WebMaster release eclipse.org-common more often to the live website?
A: Yes. We'll write documents called "Plans" where we document features
and bugs we'll fix. We'll call a group of tested features and bug fixes
a "Release". We'll do these regularly, as required.
Q: I want an easy way to write content that can easily be edited by
anyone in the Community. Phoenix doesn't allow that. What do I do?
A: Use the wiki. That's what it's there for.
Denis
--
Denis Roy
Manager, IT Infrastructure
Eclipse Foundation, Inc.
Office: 613.224.9461 x224
Cell: 819.210.6481
denis.roy@xxxxxxxxxxx
