December 2024 - Datalad-devel - lists.fz-juelich.de

[VOTE] Fix and clarification of governance docs
by Michael Hanke 16 Jan '25

16 Jan '25

Hi, I am calling a vote re the adoption of two changes to our governance docs that address minor issues that have been identified during the initial vote on these texts. The two proposed changes can be found in individual commits at https://hub.datalad.org/www/project.d.o/pulls/7/commits Last commit: 36b7e75e5f92d42f25484ab324ab2b9c299bf358 Given the time of the year and the minor severity of the changes, I propose Jan 15 2025 as the end of this "unanimous consensus" vote (see https://project.datalad.org/governance/decisions#types-of-approval) Thank you! Michael -- Michael Hanke GPG: 4096R/C073D2287FFB9E9B http://psychoinformatics.de

3 3

[VOTE] DataLad project governance
by Michael Hanke 21 Dec '24

21 Dec '24

Hi all, over the past weeks, some people in the DataLad community have worked together to compose a draft describing the (future) governance of the DataLad project. This draft can be found as a pull-request at https://hub.datalad.org/www/project.d.o/pulls/4 with commit https://hub.datalad.org/www/project.d.o/commit/e2676e7b8f09b3ab9b0d2e8f803f… Although this document represents a consensus within the group of authors, it makes sense to subject it to the same community-approval process that it describes, specifically in `decisions.md`, section `Voting`: https://hub.datalad.org/www/project.d.o/src/commit/e2676e7b8f09b3ab9b0d2e8f… Therefore, I am calling a vote regarding the adoption of this text as the governance specification of the DataLad project. As described in https://hub.datalad.org/www/project.d.o/src/commit/e2676e7b8f09b3ab9b0d2e8f… *everyone* has a vote. Voting is done by replying to this message, on this mailing list, with `+1`, `+0`, `-0`, or `-1` in this subject line. Comments and suggestions can be included in the message body. Such comments must be included for votes that oppose the adoption process to go forward with the proposed text. Given the central role of project governance, I believe that an "unanimous consensus" is desirable. The proposed voting period for this type of approval is 120h (5 days). Thank you for voting! Michael -- Michael Hanke GPG: 4096R/C073D2287FFB9E9B http://psychoinformatics.de

8 10

Re: [datalad-devel] [VOTE] DataLad project governance +1
by Benjamin Poldrack 20 Dec '24

20 Dec '24

3 2

Re: [datalad-devel] [VOTE] DataLad project governance
by Heunis, Stephan 17 Dec '24

17 Dec '24

+1

1 0

[VOTE] DataLad project governance
by Adina Wagner 16 Dec '24

16 Dec '24

1 0

Re: [datalad-devel] Datalad-devel Digest, Vol 1, Issue 1
by Heunis, Stephan 13 Dec '24

13 Dec '24

Thanks for the update. I think this is a great step forward, and happy to be here. > On 13. Dec 2024, at 12:00, datalad-devel-request(a)fz-juelich.de wrote: > > Send Datalad-devel mailing list submissions to > datalad-devel(a)fz-juelich.de > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.fz-juelich.de/mailman/listinfo/datalad-devel > or, via email, send a message with subject or body 'help' to > datalad-devel-request(a)fz-juelich.de > > You can reach the person managing the list at > datalad-devel-owner(a)fz-juelich.de > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Datalad-devel digest..." > > > Today's Topics: > > 1. New mailing list (Michael Hanke) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 12 Dec 2024 14:08:41 +0100 > From: Michael Hanke <mih(a)ngln.eu> > To: datalad-devel(a)fz-juelich.de > Subject: [datalad-devel] New mailing list > Message-ID: <Z1rgWUrhdhhG-kLa@meiner> > Content-Type: text/plain; charset=utf-8 > > Dear future audience! > > This is a first post to this new mailing list `datalad-devel`. It has > been created as part of a process to introduce more transparent and more > accessible governance and planning processes for the DataLad project. > > Although we will continue to maintain a number of additional communication > channels for a variety of purposes and audiences, all communication on > management, strategic planning, decisions, and publication of voting results > will now take place on this mailing list. > > This is not a fundamental change for the project. Since the beginning > of DataLad more than 10 years ago, virtually all communication on > planning, design, maintenance and other development-related topic > happened on public channels. What is changing now, is that we are > declaring this mailing list to be the one channel that will have all > essential communication on this topic, and that it will be publicly > archived by a service that is not dependent on a collection of 3rd-party > platforms. > > All contributors are encouraged to subscribe to this mailing list. > > Thanks, and looking forward to reading you here! > > > ------------------------------ > > Subject: Digest Footer > > Datalad-devel mailing list > Datalad-devel(a)fz-juelich.de > https://lists.fz-juelich.de/mailman/listinfo/datalad-devel > > > ------------------------------ > > End of Datalad-devel Digest, Vol 1, Issue 1 > *******************************************

1 0

New mailing list
by Michael Hanke 12 Dec '24

12 Dec '24

Dear future audience! This is a first post to this new mailing list `datalad-devel`. It has been created as part of a process to introduce more transparent and more accessible governance and planning processes for the DataLad project. Although we will continue to maintain a number of additional communication channels for a variety of purposes and audiences, all communication on management, strategic planning, decisions, and publication of voting results will now take place on this mailing list. This is not a fundamental change for the project. Since the beginning of DataLad more than 10 years ago, virtually all communication on planning, design, maintenance and other development-related topic happened on public channels. What is changing now, is that we are declaring this mailing list to be the one channel that will have all essential communication on this topic, and that it will be publicly archived by a service that is not dependent on a collection of 3rd-party platforms. All contributors are encouraged to subscribe to this mailing list. Thanks, and looking forward to reading you here!

1 0