[db-wg] Database Working Group Chair Selection
- Previous message (by thread): [db-wg] Database Working Group Chair Selection
- Next message (by thread): [db-wg] Database Working Group Chair Selection
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Tatlisu
dbwg at tatlisu.eu
Thu Jun 8 22:37:57 CEST 2023
Hello everyone, I am David, the second co-chair candidate. 20 years old, located in Berlin, I work as a network engineer for a large hosting company. Some of you may have already met me at a local beering or a RIPE meeting. I've already talked to Denis and William about the position, what happens behind the scenes, and what is expected. I also got additional tips and information from Franziska and Mirjam and plan to take part in the upcoming co-chair training program. Some of my goals as a co-chair would be - To support the moderation of the mailing list and facilitate working group tasks - Promote active discussion, sending summary emails to make the content easier to follow - Perform community outreach to raise awareness of this working group and the policy process Please do not hesitate to ask me any question or to give feedback. Regards, David On 6/8/23 17:30, William Sylvester via db-wg wrote: > > Fellow working group members, > > We currently have two slots open, the first is Denis’s term has come > to an end. In keeping with our continuity plan to have chairs on a > three year rotation offset yearly. The other open slot has two years > remaining as a term. We have two candidates currently for these open > slots with preferences as indicated; > > Denis Walker, two year term > > David Tatlisu, three year term > > I encourage each candidate to post any statements they wish to make > directly to the working group. > > This notice serves as the candidate announcement and call for discussion. > > Thanks, > > William > > DB-WG Co-Chair > > Our current chair process is as revised in 2017, as follows; > > 1) Number of chairs is a minimum of 2 with a maximum of 3. > > 2) Chair can be removed at any time by consensus. > > 3) Chair terms are staggered yearly. > > 4) One chair per year is replaced. > > 5) Workinggroup selects chair by consensus. > > 6) The consensus judgement will be made by the serving WG co-chair(s) > and will exclude the co-chair(s) who is the subject of that consensus > judgement. > > 7) Selectionprocess is as follow; > > 7.1) Interested parties have two weeks to make their interest known > via the mailing list, or directly to the Chair/s. > > 7.2) After two weeks, the Chair/s ensure that all candidates are > announced on the mailing list and issue a call for discussion. > > 7.3) WG members express their approval or otherwise of the presented > candidates. > > 7.4) Two weeks after the call for discussion, the Chair/s declare a > decision, based on mailing list discussion, as they would do for a > policy proposal. > > 8) Any appeal over a consensus decision will be heard by the RIPE > Chair (or their deputy) whose decision shall be final. > > 9) In the case more than one chair is up for selection at the same > time, the chair with the greatest support will take a multi-year term, > the chair with the least support will take the second longest term. > Terms will be determined by the number of chairs (3 chairs = 3 year > term, 2 chairs = 2 year teams). The intent is to maintain continuity > of the workinggroupchairs. So the workinggroup is never left without a > chair. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.ripe.net/ripe/mail/archives/db-wg/attachments/20230608/0215cf15/attachment-0001.html>
- Previous message (by thread): [db-wg] Database Working Group Chair Selection
- Next message (by thread): [db-wg] Database Working Group Chair Selection
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]