I also support the decision of the chairs 100% (as a long time attendee of RIPE
meetings and (mostly silent) subscriber of this list).
> On 16. Dec 2023, at 09:33, Maria Matejka via opensource-wg
> wrote:
>
> This is indeed a good way to resolve this, even though it maybe should have
> been
Hello Paul,
(replies inline)
On 2023-12-20 14:14, Paul Menzel wrote:
[…]
(I always wonder, why a Open Source group use proprietary software
like Google Docs. Does RIPE offer alternatives already? Otherwise, I’d
suggest some Git repository.)
There are projects like HackMD useful for this,
Dear Valerie,
Thank you for your message.
Am 20.12.23 um 03:27 schrieb Valerie Aurora:
Thanks for everyone's enthusiasm at the RIPE session about the open
source project credit policy! While recovering from COVID I managed to
put together a starting draft that included all of the
Hello Valerie and others,
(replies inline)
On 2023-12-20 03:27, Valerie Aurora wrote:
Thanks for everyone's enthusiasm at the RIPE session about the open
source project credit policy! While recovering from COVID I managed to
put together a starting draft that included all of the suggestions I
Hi,
On Wed, Dec 20, 2023 at 02:14:16PM +0100, Paul Menzel wrote:
> Has this issue come up more often in the RIPE related Open source projects
> (BIRD, Quagga, OpenBGPD, XORP, DHCP, RRDtool, ntop and Nagios, ???), that
> the working group wants to take this on?
As we discussed in the WG session,
