Even if we go to ops4j.github.com, I think it will be helpful to redirect
from ops4j.org. So, I volunteer to "take" the ops4j domain. It will give us
time to "transfer" resources to github.
OK with that ?
Regards
JB
On Tue, Mar 31, 2020 at 4:15 AM Niclas Hedhman wrote:
>
> The thread's
The thread's primary question is;
Shall I a) let the ops4j domain names expire, or b) transfer them to
someone else? If b), then Who/What?
The rest is "interesting" but actually "out of scope" for something very
concrete in 10 weeks time. The full structure of community can in principle
be
Hello
What do you think I start a vote on the mailing list
>
+1 for starting the vote ;)
regards
Grzegorz Grzybek
wt., 31 mar 2020 o 04:15 Niclas Hedhman napisał(a):
>
> The thread's primary question is;
>
> Shall I a) let the ops4j domain names expire, or b) transfer them to
> someone else?
Thanks Niclas for bringing up the issue!
FWIW - I think Github is basically what OPS4J set out to be
code-contribution-wise. IMHO going back to Apache is a matter of the
community deciding if the barriers for governance/contribution are lower
now. Otherwise - I think just moving everything to
I agree.
What do you think I start a vote on the mailing list to propose to move to
ops4j.github.com ?
Regards
JB
On Mon, Mar 30, 2020 at 4:34 PM Peter Neubauer
wrote:
> Thanks Niclas for bringing up the issue!
>
> FWIW - I think Github is basically what OPS4J set out to be
>
