Date: Thu, 28 Mar 2024 17:38:41 -0400 (EDT) Message-ID: <948290611.28992.1711661921940@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_28991_1845834380.1711661921939" ------=_Part_28991_1845834380.1711661921939 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The DSpace Committers Group =E2=80=93 named because they are authorized = to "commit" change to the code repository =E2=80=93 have ultimate responsib= ility for the shape of the DSpace software, as well as its architecture and= design going forward. They can apply code changes contributed by the large= r DSpace development community to the open source platform.
A list of the current members of the committers group can be seen at DSpaceContributors
Being a committer means participating in the evolution of the DSpace pla= tform, typically by making changes to the source code, improving documentat= ion, or managing the integration of contributions made by the community at = large. But, it also means having a voice and an official vote on technical,= administrative and release management issues, providing your expertise and= guidance on the lists, organizing testing, etc.
We are mindful of the fact that no one is being paid to do this, and no = specific time commitment is required or expected; in fact we do expect that one's involvement will fluctuate over time with job dutie= s. Nor is there any specified term of office - one's job responsibilities m= ay change over time, and also one's ability to devote time to DSpace.
Becoming a committer means that you have a voice and an official vote on= decisions around the evolution of the DSpace platform. It also gives you a= n opportunity to develop leadership skills in a friendly, open source commu= nity.
Although there are no explicit requirements to become a committer, gener= ally we look for someone who has shown initiative and/or has been an active= participant in the DSpace Community. Participation may be in the form of a= ctively helping people on mailing lists, submitting code patches/features, = presenting on DSpace at conferences, leading workshops, or generally volunt= eering time to help with any DSpace initiative.
It's worth noting that committers need not be highly technical in nature= . We only ask that you make a commitment to bettering DSpace in some way. A= nyone who shows the initiative and interest in making DSpace better is elig= ible.
New committers may be nominated by anyone in the DSpace Communit= y at anytime. You can even nominate yourself.
In your nomination, please explain why you feel this individual (or indi= viduals) should be added to the Committers group. Generally, we are just lo= oking for references to his/her active participation in the DSpace Communit= y.
Send new committer nominations to any of the existing DSpace Committers. If you have any questio= ns about nominations, you can also talk to a current member who can offer a= dvice.
Again, there is no specific timeline for nominations. Nominations may be= made at any time.
Once a committer is nominated, the nomination is voted on by all current= Committers. The decision to accept or reject the nomination is based on a = majority vote. If a nomination is accepted, that person will immediately re= ceive an invite to become a DSpace Committer! If a nomination is rejected, = we will provide feedback on how that person may become more active in the c= ommunity, so that he/she could be potentially re-nominated and accepted in = the future. (Please note that a rejection of a nomination does not mean tha= t the person is "unqualified". It just means that the existing Committers m= ay not be familiar enough with that person's activities in the DSpace Commu= nity. A person can always be re-nominated at a later time.)
For more information see the Committers' policies on adding a new Committer.