Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 369279

Summary:	Incorrect cross-references in bylaws
Product:	Community	Reporter:	John Arthorne <john.arthorne>
Component:	Process	Assignee:	Eclipse Management Organization <emo>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	mike.milinkovich, wayne.beaton
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description John Arthorne

2012-01-20 14:29:44 EST

By-law version: 2011-08-15

http://eclipse.org/org/documents/Eclipse%20BYLAWS%202011_08_15%20Final.pdf

Section 3.2 (d) states:

  (d) Committer Members. Committer Members (as defined in Section 6.2(d) below)

However section 6.2 (d) is for Solutions Members. The correct section reference would be 6.2 (e).

I think several of the other cross-references in 3.2 are off by one as well.

Comment 1 Eclipse Genie

2014-09-18 19:01:50 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 2 Eclipse Genie

2016-09-09 07:08:43 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 3 Eclipse Genie

2018-08-31 10:46:16 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 4 Eclipse Genie

2020-08-21 06:53:02 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 5 Wayne Beaton

2022-01-05 17:12:50 EST

The bylaws have undergone multiple changes since this was reported and the issue no longer exists AFAICT.