<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<div class="moz-cite-prefix">Am 06.05.19 um 16:03 schrieb Bruno
Oliveira:<br>
</div>
<blockquote type="cite"
cite="mid:CA+RQFfc=40gvSf8f5=Noc5zMhn15w9LbV06Gtu69KjjHY3TWUA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hi Ronny,</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun, May 5, 2019 at 11:09
AM Ronny Pfannschmidt <<a
href="mailto:opensource@ronnypfannschmidt.de"
moz-do-not-send="true">opensource@ronnypfannschmidt.de</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>i think its a good idea to have this as a opt-in.<br>
</p>
<p>Currently a Fair Share Mechanism on a opt in basis
seems fair,<br>
if we ever hit a situation where someone could have a
reasonably set up part/full-time position primarily on
pytest we should take a look at how division is fair in
that case.</p>
</div>
</blockquote>
<div><br>
</div>
<div>Agreed, thanks Ronny.</div>
<div><br>
</div>
<div>If nobody objects, I plan to move this forward later this
week.</div>
<div><br>
</div>
<div>One question is how do we track which maintainers are
opting to receive funding.</div>
</div>
</div>
</blockquote>
<br>
<blockquote type="cite"
cite="mid:CA+RQFfc=40gvSf8f5=Noc5zMhn15w9LbV06Gtu69KjjHY3TWUA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div>I'm thinking of opening an issue which lists the
contributors receiving the funding; maintainers are then
free to post a comment indicating if they want to start/stop
receiving funding, at which point we update the original
post. Another option would be to use the Wiki, but we don't
receive change notifications so there's a chance of we
getting out of sync with the configuration on Tidelift.
Suggestions?</div>
<div><br>
</div>
</div>
</div>
</blockquote>
<p>we should make a git repo where we track meta level
documentation,<br>
that way we chould have a ci with credentials run the checks</p>
<p>i wonder if tidelift hasn an api published for that</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CA+RQFfc=40gvSf8f5=Noc5zMhn15w9LbV06Gtu69KjjHY3TWUA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div>Another question is regarding admins of the Tidelift
dashboard. I volunteer to do it, but would like more people
to also be admins to reduce the bus factor, so other
volunteers are appreciated as well.</div>
</div>
</div>
</blockquote>
<p>in about 2-3 Months i can Commit to such role as well.</p>
<p><br>
</p>
<p>Cheers Ronny<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:CA+RQFfc=40gvSf8f5=Noc5zMhn15w9LbV06Gtu69KjjHY3TWUA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div><br>
</div>
<div>Cheers,</div>
<div>Bruno.</div>
<div><br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p> </p>
<p>-- Ronny<br>
</p>
<p><br>
</p>
<div class="gmail-m_-3623151745771913705moz-cite-prefix">Am
03.05.19 um 14:11 schrieb Bruno Oliveira:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Hi Floris,</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, May 2,
2019 at 2:25 PM Floris Bruynooghe <<a
href="mailto:flub@devork.be" target="_blank"
moz-do-not-send="true">flub@devork.be</a>>
wrote:</div>
<blockquote class="gmail_quote" style="margin:0px
0px 0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex"> Why the rules
about active? Seems complicated and more open to<br>
arguing. I liked the Pillow guidelines you
linked:<br>
<a
href="https://github.com/orgs/pytest-dev/teams/contributors"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://github.com/orgs/pytest-dev/teams/contributors</a>
can express<br>
interest and <a
href="https://github.com/orgs/pytest-dev/teams/core"
rel="noreferrer" target="_blank"
moz-do-not-send="true">https://github.com/orgs/pytest-dev/teams/core</a>
decides on<br>
split (which I guess can be anything from 0% to
100%). With the same<br>
assumption that the core members are reasonable
that should end up as<br>
roughly the same.<br>
<br>
Mind you in practice I have no issue with the
above proposal of people<br>
right now, but would also not mind if e.g. hpk or
ronny wanted to be<br>
part right now (I'll pass myself). Likewise there
are probably cases<br>
where I wouldn't mind people not in core being
paid for some time.<br>
</blockquote>
<div><br>
</div>
<div>I wrote those "rules" just to come up with a
solid proposal in the e-mail, but I do like yours
better. Letting developers opt-in to a share is
fair and reasonable, certainly.</div>
<div><br>
</div>
<div>I think we should even always split the funding
evenly between those opting to receive it, to
further avoid any arguing on that.</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px
0px 0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">But in general
I'm +1, let's make it happen if there's anyone
interested<br>
in getting paid.<br>
</blockquote>
<div><br>
</div>
<div>Great, let's see what others think.</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Bruno.</div>
</div>
</div>
<br>
<fieldset
class="gmail-m_-3623151745771913705mimeAttachmentHeader"></fieldset>
<pre class="gmail-m_-3623151745771913705moz-quote-pre">_______________________________________________
pytest-dev mailing list
<a class="gmail-m_-3623151745771913705moz-txt-link-abbreviated" href="mailto:pytest-dev@python.org" target="_blank" moz-do-not-send="true">pytest-dev@python.org</a>
<a class="gmail-m_-3623151745771913705moz-txt-link-freetext" href="https://mail.python.org/mailman/listinfo/pytest-dev" target="_blank" moz-do-not-send="true">https://mail.python.org/mailman/listinfo/pytest-dev</a>
</pre>
</blockquote>
</div>
</blockquote>
</div>
</div>
</blockquote>
</body>
</html>