|
List Info
Thread: Suggestion: componentization of Phoenix
|
|
| Suggestion: componentization of Phoenix |
 
United States |
2007-03-22 15:47:11 |
|
Phoenixers,
I'd like to suggest that we divide Phoenix into components so that we
can more accurately elect Phoenix committers. For example, I "own" the
/projects/ and /proposals/ sub-trees, and I occasionally delve into
/org/councils/, but other than that I'm not *full* Phoenix committer. I
wouldn't care touch EPIC or Planet or even the main App files. If I
felt like make a change to those files, I'd send a patch to one of the
senior committeres (Denis, Nathan, ...). Thus I'm really only a
committer on the "Projects" component of Phoenix. Similarly, Anne is
also a full committer on Phoenix, but she works on even less of the
tree than I do. And Donald is a full committer, so he has commit rights
to modify the development process pages, but he shouldn't really
because he doesn't understand the complexities there.
I believe we are already effectively managing Phoenix commit rights by
component, but we're doing it in a hidden way, i.e., we all just
understand what we are allowed to do or not. If we were to switch to a
full component strategy, we would be open and public about the
situation:
- *: Denis, Nathan
- Projects: Bjorn, Anne
- EPIC: Nathan, Susan, Mark, Jochen, Howard, Maher, Todd
- Planet: Gunnar, Chris
- Members: Donald, Ian, Lynn
- Foundation: Mike, Bjorn
Plus it would be easier to add others as appropriate (after they
qualify for committer status through patches, etc), for example:
Thoughts?
- Bjorn
|
| RE: Suggestion: componentization of
Phoenix |
United States |
2007-03-23 06:31:39 |
|
+1 (except that I would point out that I currently own the legal
pages as well)
Mike Milinkovich
Office: +1.613.224.9461 x228
Mobile: +1.613.220.3223
mike.milinkovich eclipse.org">mike.milinkovicheclipse.org
From: phoenix-dev-bounceseclipse.org
[mailto:phoenix-dev-bounceseclipse.org] On Behalf Of Bjorn
Freeman-Benson
Sent: Thursday, March 22, 2007 4:47 PM
To: phoenix-dev
Subject: [phoenix-dev] Suggestion: componentization of Phoenix
Phoenixers,
I'd like to suggest that we divide Phoenix into components so that we can more
accurately elect Phoenix committers. For example, I "own" the /projects/
and /proposals/ sub-trees, and I occasionally delve into /org/councils/, but
other than that I'm not *full* Phoenix committer. I wouldn't care touch EPIC or
Planet or even the main App files. If I felt like make a change to those files,
I'd send a patch to one of the senior committeres (Denis, Nathan, ...). Thus
I'm really only a committer on the "Projects" component of Phoenix.
Similarly, Anne is also a full committer on Phoenix, but she works on even less
of the tree than I do. And Donald is a full committer, so he has commit rights
to modify the development process pages, but he shouldn't really because he
doesn't understand the complexities there.
I believe we are already effectively managing Phoenix commit rights by
component, but we're doing it in a hidden way, i.e., we all just understand
what we are allowed to do or not. If we were to switch to a full component
strategy, we would be open and public about the situation:
- *: Denis, Nathan
- Projects: Bjorn, Anne
- EPIC: Nathan, Susan, Mark, Jochen, Howard, Maher,
Todd
- Planet: Gunnar, Chris
- Members: Donald, Ian, Lynn
- Foundation: Mike, Bjorn
Plus it would be easier to add others as appropriate (after
they qualify for committer status through patches, etc), for example:
Thoughts?
- Bjorn
|
| RE: Suggestion: componentization of
Phoenix |
United States |
2007-03-23 10:03:02 |
|
| This sounds OK to me, but I think the list of committers is
incomplete. I believe that I'm a committer on the Epic portion of the
project. Let me know if I have this wrong.
MikeT
Content-Type: multipart/alternative;
;
boundary="----=_NextPart_000_004B_01C76D1D.5072D2D0"
Content-Language: en-ca
+1 (except that I would point out that I
currently own the legal pages as well)
Mike Milinkovich
Office: +1.613.224.9461 x228
Mobile: +1.613.220.3223
eclipse.org"
>mike.milinkovicheclipse.org
From:
phoenix-dev-bounceseclipse.org
[mailto:phoenix-dev-bounceseclipse.org] On Behalf Of Bjorn
Freeman-Benson
Sent: Thursday, March 22, 2007 4:47 PM
To: phoenix-dev
Subject: [phoenix-dev] Suggestion: componentization of
Phoenix
Phoenixers,
I'd like to suggest that we divide Phoenix into components so that we
can more accurately elect Phoenix committers. For example, I
"own" the /projects/ and /proposals/ sub-trees, and I
occasionally delve into /org/councils/, but other than that I'm not
*full* Phoenix committer. I wouldn't care touch EPIC or Planet or even
the main App files. If I felt like make a change to those files, I'd
send a patch to one of the senior committeres (Denis, Nathan, ...).
Thus I'm really only a committer on the "Projects" component
of Phoenix. Similarly, Anne is also a full committer on Phoenix, but
she works on even less of the tree than I do. And Donald is a full
committer, so he has commit rights to modify the development process
pages, but he shouldn't really because he doesn't understand the
complexities there.
I believe we are already effectively managing Phoenix commit rights by
component, but we're doing it in a hidden way, i.e., we all just
understand what we are allowed to do or not. If we were to switch to a
full component strategy, we would be open and public about the
situation:
- *: Denis, Nathan
- Projects: Bjorn, Anne
- EPIC: Nathan, Susan, Mark, Jochen, Howard, Maher, Todd
- Planet: Gunnar, Chris
- Members: Donald, Ian, Lynn
- Foundation: Mike, Bjorn
Plus it would be easier to add others as
appropriate (after they qualify for committer status through patches,
etc), for example:
Thoughts?
- Bjorn
_______________________________________________
phoenix-dev mailing list
phoenix-deveclipse.org
https://dev.eclipse.org/mailman/listinfo/phoenix-dev
--
--- -------------------------------------
Mike Taylor
President and CEO
Instantiations, Inc.
Build Quality Software!
Voice: (503) 598-4911
mike_taylorinstantiations.com
http://www.instantiations.com
|
| Re: Suggestion: componentization of
Phoenix |
 
Canada |
2007-03-23 10:46:54 |
|
+1
So what do suggest we do to make the division visible? I can thinnk of
a) Bugzilla. We create components in Technology/Phoenix for the
additional components you have enumerated.
b) the Phoenix website: http://www.eclipse.org/phoenix/about.php We
split the "team" section into components and list the committers for
each component
Anything else?
Bjorn Freeman-Benson wrote:
eclipse.org" type="cite">
Phoenixers,
I'd like to suggest that we divide Phoenix into components so that we
can more accurately elect Phoenix committers. For example, I "own" the
/projects/ and /proposals/ sub-trees, and I occasionally delve into
/org/councils/, but other than that I'm not *full* Phoenix committer. I
wouldn't care touch EPIC or Planet or even the main App files. If I
felt like make a change to those files, I'd send a patch to one of the
senior committeres (Denis, Nathan, ...). Thus I'm really only a
committer on the "Projects" component of Phoenix. Similarly, Anne is
also a full committer on Phoenix, but she works on even less of the
tree than I do. And Donald is a full committer, so he has commit rights
to modify the development process pages, but he shouldn't really
because he doesn't understand the complexities there.
I believe we are already effectively managing Phoenix commit rights by
component, but we're doing it in a hidden way, i.e., we all just
understand what we are allowed to do or not. If we were to switch to a
full component strategy, we would be open and public about the
situation:
- *: Denis, Nathan
- Projects: Bjorn, Anne
- EPIC: Nathan, Susan, Mark, Jochen, Howard, Maher, Todd
- Planet: Gunnar, Chris
- Members: Donald, Ian, Lynn
- Foundation: Mike, Bjorn
Plus it would be easier to add others as appropriate (after they
qualify for committer status through patches, etc), for example:
Thoughts?
- Bjorn
_______________________________________________
phoenix-dev mailing list
eclipse.org">phoenix-deveclipse.org
https://dev.eclipse.org/mailman/listinfo/phoenix-dev
--
Denis Roy
Manager, IT Infrastructure
Eclipse Foundation, Inc. -- http://www.eclipse.org/
Office: 613.224.9461 x224 (Eastern time)
Cell: 819.210.6481
eclipse.org">denis.royeclipse.org
|
| Re: Suggestion: componentization of
Phoenix |
United States |
2007-03-23 10:49:42 |
|
After (b) we will add the committer <-> component mappings to the
portal for any future committer elections.
Denis Roy wrote:
eclipse.org" type="cite">
Anything else?
|
| RE: Suggestion: componentization of
Phoenix |
Canada |
2007-03-23 14:08:26 |
|
+1
Although it would be helpful to state that
you wouldnR17;t be constrained by your assigned component for typo-esque
changes, so that typos can be fixed by anyone, no matter the page. ; -Lynn
From: phoenix-dev-bounceseclipse.org
[mailto:phoenix-dev-bounceseclipse.org] On
Behalf Of Bjorn Freeman-Benson
Sent: Thursday, March 22, 2007
4:47 PM
To: phoenix-dev
Subject: [phoenix-dev] Suggestion:
componentization of Phoenix
Phoenixers,
I'd like to suggest that we divide Phoenix into
components so that we can more accurately elect Phoenix committers. For example, I
"own" the /projects/ and /proposals/ sub-trees, and I occasionally
delve into /org/councils/, but other than that I'm not *full* Phoenix committer. I wouldn't care touch EPIC
or Planet or even the main App files. If I felt like make a change to those
files, I'd send a patch to one of the senior committeres (Denis, Nathan, ...).
Thus I'm really only a committer on the "Projects" component of Phoenix. Similarly, Anne
is also a full committer on Phoenix,
but she works on even less of the tree than I do. And Donald is a full
committer, so he has commit rights to modify the development process pages, but
he shouldn't really because he doesn't understand the complexities there.
I believe we are already effectively managing Phoenix commit rights by component, but we're
doing it in a hidden way, i.e., we all just understand what we are allowed to
do or not. If we were to switch to a full component strategy, we would be open
and public about the situation:
- *: Denis, Nathan
- Projects: Bjorn, Anne
- EPIC: Nathan, Susan, Mark, Jochen, Howard, Maher,
Todd
- Planet: Gunnar, Chris
- Members: Donald, Ian, Lynn
- Foundation: Mike, Bjorn
Plus it would be easier to add others as appropriate
(after they qualify for committer status through patches, etc), for example:
Thoughts?
- Bjorn
|
[1-6]
|
|