You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "P. Ottlinger" <po...@apache.org> on 2020/02/03 21:27:23 UTC
Re: Podling Tamaya Report Reminder - February 2020
Hi guys,
following our discussions I submitted our February report
https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#tamaya
Cheers,
Phil
Am 16.01.20 um 01:27 schrieb jmclean@apache.org:
> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 19 February 2020, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, February 05).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Candidate names should not be made public before people are actually
> elected, so please do not include the names of potential committers or
> PPMC members in your report.
Re: Tamaya's Future (was Re: Podling Tamaya Report Reminder -
February 2020)
Posted by Werner Keil <we...@gmail.com>.
Hi Anatole,
Thanks for the update, also about your future career step. Congratulations
on moving to IBM soon.
As we discussed, an incubating project does not get archived, but simply
deleted by Apache, correct me if I got that wrong?
So 1) would delete and destroy all of it. There may not be too many real
life use cases in production right now, but it demonstrated a few aspects
that e.g. Microprofile Config and other (not so cloud aware) config
solutions are still missing
2) there seems nothing wrong with that, and the GH organization you
(Anatole) already created could be used for that.
There is a very outdated fork of Tamaya
https://github.com/java-config/incubator-tamaya (which would not go away
even if the repo at Apache did;-)
and the "seed" for Tamaya: https://github.com/java-config/tamaya-export
Based on my experience I would at least declare the latter as archived and
make it read-only in GitHub (could you do that please or offer admin rights
to others in the organization?)
So maybe prior to ASF pulling the plug a "dump" may be created, but ideally
it should not be a fork but also migrated elsewhere. Reza (not the Jakarta
EE Ambassador) who also helped weather.com use OpenDDR/Devicemap (it's now
owned by IBM, but not sure, if it still uses W3C DDR or other device
recognition) forked the DeviceMap Java client to
https://github.com/TextGlass/java of course, it never saw any contributions
after 2015, so it's dead while OpenDDR data was downloaded around 150.000
times last year after more than twice that in 2018.
Unless we got a domain like javaconfig.org, we could always use
io.github.javaconfig.
Option 3) I am not sure, if e.g. the Apache Commons Config team was
interested, that is the only place I could see where parts of Tamaya may be
of interest.
Werner
On Mon, Feb 10, 2020 at 11:28 PM Anatole Tresch <at...@gmail.com> wrote:
> Hi all
>
> as you all know I also started the discussion about Tamaya's future.
> Background is that I will move to IBM end of April 2020 and start as a
> Cloud Consultant. So I will not have too much time left for doing
> Java/programming.
> That does not mean that I would like to abandon this project completely,
> but for me it makes no sense keeping it up running in the current mode,
> unless some people really start to get into the code as well (it is not
> that complicated mostly).Moving it to GitHub does not solve the community
> issue, that is correct, but objective of the incubator is to build up a
> community, which I think was not possible. So I basically see the following
> options:
>
> 1) Retire everything (RIP)
> 2) Move everything to GitHub and see how things evolve.
> 3) See if the core part/API can be moved as a subproject somewhere in
> Apache and move the extensions to GitHub.
>
> J Anatole
>
>
> Am Mo., 10. Feb. 2020 um 22:46 Uhr schrieb P. Ottlinger <
> pottlinger@apache.org>:
>
> > Hi,
> >
> > Am 10.02.20 um 22:29 schrieb Oliver B. Fischer:
> > > But looking at the number of commits, Tamaya is dying.
> >
> > LOL - Anatole is and was the main contributor and committer -
> > this did not change over the period Tamaya is in incubating mode, IMHO.
> >
> > > What do you thing, does Tamaya currently provides anything usefull for
> > > users what is not provided by other frameworks?
> >
> > Most useful is a broad variety of extensions that allow Tamaya to be
> > used in various circumstances/environments - to my mind that's the
> > biggest pro.
> >
> > But we didn't gain any momentum to let the world know of this cool
> feature.
> >
> > Moving it to Github would only stop the ASF reporting schedule but does
> > not address the issue of a viable future.
> >
> > Just my 2ct,
> >
> > Phil
> >
> >
>
> --
> *Anatole Tresch*
> PPMC Member Apache Tamaya
> JCP Star Spec Lead
> *Switzerland, Europe Zurich, GMT+1*
> *maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> *
> *Twitter: @atsticks, @tamayaconf*
>
Re: Tamaya's Future (was Re: Podling Tamaya Report Reminder -
February 2020)
Posted by Anatole Tresch <at...@gmail.com>.
Hi all
as you all know I also started the discussion about Tamaya's future.
Background is that I will move to IBM end of April 2020 and start as a
Cloud Consultant. So I will not have too much time left for doing
Java/programming.
That does not mean that I would like to abandon this project completely,
but for me it makes no sense keeping it up running in the current mode,
unless some people really start to get into the code as well (it is not
that complicated mostly).Moving it to GitHub does not solve the community
issue, that is correct, but objective of the incubator is to build up a
community, which I think was not possible. So I basically see the following
options:
1) Retire everything (RIP)
2) Move everything to GitHub and see how things evolve.
3) See if the core part/API can be moved as a subproject somewhere in
Apache and move the extensions to GitHub.
J Anatole
Am Mo., 10. Feb. 2020 um 22:46 Uhr schrieb P. Ottlinger <
pottlinger@apache.org>:
> Hi,
>
> Am 10.02.20 um 22:29 schrieb Oliver B. Fischer:
> > But looking at the number of commits, Tamaya is dying.
>
> LOL - Anatole is and was the main contributor and committer -
> this did not change over the period Tamaya is in incubating mode, IMHO.
>
> > What do you thing, does Tamaya currently provides anything usefull for
> > users what is not provided by other frameworks?
>
> Most useful is a broad variety of extensions that allow Tamaya to be
> used in various circumstances/environments - to my mind that's the
> biggest pro.
>
> But we didn't gain any momentum to let the world know of this cool feature.
>
> Moving it to Github would only stop the ASF reporting schedule but does
> not address the issue of a viable future.
>
> Just my 2ct,
>
> Phil
>
>
--
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> *
*Twitter: @atsticks, @tamayaconf*
Re: Tamaya's Future (was Re: Podling Tamaya Report Reminder -
February 2020)
Posted by Werner Keil <we...@gmail.com>.
I guess John knows best, what happens when you're no longer able to
contribute to a project:
https://github.com/eclipse/microprofile-rest-client/graphs/contributors If
it wasn't for IBM then MP Rest Client would be dead after he stopped
working on it around 2 years ago.
Same for Config btw
https://github.com/eclipse/microprofile-config/graphs/contributors but at
least Emily/IBM also helped out here a bit recently.
Whether MP Config really has a chance of becoming an integral part of
Jakarta EE (which would be a key to further participation and success)
remains to be seen, but it is a possible place to continue contributing if
Tamaya was to stop.
I mentioed others, Helidon
https://github.com/oracle/helidon/graphs/contributors is clearly a huge
success and an active community also with an interesting and promising
configuration module...
Werner
On Mon, Feb 10, 2020 at 10:46 PM P. Ottlinger <po...@apache.org> wrote:
> Hi,
>
> Am 10.02.20 um 22:29 schrieb Oliver B. Fischer:
> > But looking at the number of commits, Tamaya is dying.
>
> LOL - Anatole is and was the main contributor and committer -
> this did not change over the period Tamaya is in incubating mode, IMHO.
>
> > What do you thing, does Tamaya currently provides anything usefull for
> > users what is not provided by other frameworks?
>
> Most useful is a broad variety of extensions that allow Tamaya to be
> used in various circumstances/environments - to my mind that's the
> biggest pro.
>
> But we didn't gain any momentum to let the world know of this cool feature.
>
> Moving it to Github would only stop the ASF reporting schedule but does
> not address the issue of a viable future.
>
> Just my 2ct,
>
> Phil
>
>
Re: Tamaya's Future (was Re: Podling Tamaya Report Reminder -
February 2020)
Posted by "P. Ottlinger" <po...@apache.org>.
Hi,
Am 10.02.20 um 22:29 schrieb Oliver B. Fischer:
> But looking at the number of commits, Tamaya is dying.
LOL - Anatole is and was the main contributor and committer -
this did not change over the period Tamaya is in incubating mode, IMHO.
> What do you thing, does Tamaya currently provides anything usefull for
> users what is not provided by other frameworks?
Most useful is a broad variety of extensions that allow Tamaya to be
used in various circumstances/environments - to my mind that's the
biggest pro.
But we didn't gain any momentum to let the world know of this cool feature.
Moving it to Github would only stop the ASF reporting schedule but does
not address the issue of a viable future.
Just my 2ct,
Phil
Re: Tamaya's Future (was Re: Podling Tamaya Report Reminder -
February 2020)
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Interessting - my commits vanished ;-|
But looking at the number of commits, Tamaya is dying.
What do you thing, does Tamaya currently provides anything usefull for
users what is not provided by other frameworks?
Oliver
Am 10.02.20 um 22:12 schrieb Werner Keil:
> I think this shows that best:
https://github.com/apache/incubator-tamaya/graphs/contributors
>
> Werner
>
>
- --
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEU7j685HGR9cAsMGwB88X6wLziPwFAl5ByygACgkQB88X6wLz
iPyYYBAAlr/tByphKFjknAIT/ks/xHxTVMGFL/OeBX1sltVFwBHjP0+A/Hyo2TAx
5dfXZm2In69500DqOmQdW9tilzx0f3wxKQDa4xmjBAwkUKiRCqiJksFYlfPOPur/
pwR0YBjNRtfWE2ZlNDe6lZ0hIml32iZLyXS1EJmvDsTkhocwjCyJUMiGHFZiASZt
G5PTM5fO3aQRzN1eefRNqybiEKHa8sK1XQyPZj+L8iO+iGvWb+Od3bpvylPAIQVI
d3cUY/lAFFGz6CKOuz581XTAfj6dZ9w0HrPdD4vPwXkY6hY8vJ9Jj05Rez4hfK/i
A7LxpcRLf/idkaHQMX7nrUYlfc6h9ephiLSI7ndZZ89U/5PF3LvgEv797CdkcGyJ
iJe7quvA81ZQYLmVLtJs1niQi8Pa6tCrXnDksBLMvIaOB+GwRaf/2vs0VnOC1SmT
cWAsKbqlapjDxMn+38JMZB/m3YWZxnzic324J6t3WA5oinREdkhrp3UJhD526fV2
iXvSUTJBue6F+FUHXbo/tNBYToetrKSa7UD0o2PPKKe2K/12aU+Yeq08+wFZ8HEN
PYcZEp4bPOJ7h/37ygTbzkZM9joE5NuiRC+9fNTVL5B6ZXGmBXi+DqJkvqhLODk8
9FIoRrFG3ThOUCYCyi+tWrl7cpWsPTh9u+0XVjB6J31TtH5QUbg=
=vf/d
-----END PGP SIGNATURE-----
Re: Tamaya's Future (was Re: Podling Tamaya Report Reminder -
February 2020)
Posted by Werner Keil <we...@gmail.com>.
I think this shows that best:
https://github.com/apache/incubator-tamaya/graphs/contributors
Werner
On Mon, Feb 10, 2020 at 10:06 PM Oliver B. Fischer <o....@swe-blog.net>
wrote:
> And who is currently the most active contributer?
>
> Am 10.02.20 um 21:00 schrieb P. Ottlinger:
> > Hi *,
> >
> > Am 10.02.20 um 16:11 schrieb Oliver B. Fischer:
> >> who would describe themselves as an active committer?
> > Although I do not contribute that much code I'd consider myself an
> > active committer.
> >
> > @John: the release is officially out, we just did not announce it
> > properly due to the fact that we seem to lack a big community.
> >
> >
> > Cheers,
> > Phil
>
> --
> N Oliver B. Fischer
> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
> P +49 30 44793251
> M +49 178 7903538
> E o.b.fischer@swe-blog.net
> S oliver.b.fischer
> J oliver.b.fischer@jabber.org
> X http://xing.to/obf
>
>
>
Re: Tamaya's Future (was Re: Podling Tamaya Report Reminder -
February 2020)
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
And who is currently the most active contributer?
Am 10.02.20 um 21:00 schrieb P. Ottlinger:
> Hi *,
>
> Am 10.02.20 um 16:11 schrieb Oliver B. Fischer:
>> who would describe themselves as an active committer?
> Although I do not contribute that much code I'd consider myself an
> active committer.
>
> @John: the release is officially out, we just did not announce it
> properly due to the fact that we seem to lack a big community.
>
>
> Cheers,
> Phil
--
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
Re: Tamaya's Future (was Re: Podling Tamaya Report Reminder -
February 2020)
Posted by "P. Ottlinger" <po...@apache.org>.
Hi *,
Am 10.02.20 um 16:11 schrieb Oliver B. Fischer:
> who would describe themselves as an active committer?
Although I do not contribute that much code I'd consider myself an
active committer.
@John: the release is officially out, we just did not announce it
properly due to the fact that we seem to lack a big community.
Cheers,
Phil
Re: Tamaya's Future (was Re: Podling Tamaya Report Reminder -
February 2020)
Posted by "Oliver B. Fischer" <o....@swe-blog.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi all,
who would describe themselves as an active committer?
Bye,
Oliver
Am 10.02.20 um 15:56 schrieb John D. Ament:
> Hey guys
>
> I signed off on the report. I'd really like to ensure that you figure
out what your path forward is going to be. Activity is low, there was a
release started end of last year that it's not clear was ever finished up.
>
> If interest is low enough, moving to github is a fine approach.
Typically keeping the name isn't a problem so your existing name could
be reused.
>
> Typically a project would take this approach if they thought getting
releases out more frequently could help them rebuild a community around
a project.
>
> John
>
>
>>
- --
N Oliver B. Fischer
A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany
P +49 30 44793251
M +49 178 7903538
E o.b.fischer@swe-blog.net
S oliver.b.fischer
J oliver.b.fischer@jabber.org
X http://xing.to/obf
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEU7j685HGR9cAsMGwB88X6wLziPwFAl5Bcq8ACgkQB88X6wLz
iPwEtQ//aCsC0tIUCrm29rEil9TnuuwxHTYdkEuZN/UojmIOxsrd88uzIQ81SdEt
kQRELmIVXdKpL4KAA6CZOwzmB8N7WJW2K6l95y31lEOpEYhWqtu1DozIX6ynykoe
rspSR8xVFX8CieFodvldQB3pDXQAJKpHG/jNTPmbC6sliG99KrKIMIMR3NNqtCgW
2TgG1ttGEuJDKnc64LDdSydd5VWEP0omz4FU3GRYlTKW6W2d1kBQCbXnw3ti56Zz
rI7nxv2++RDFZpDXPZhCJ7P3s3lGBdVxs1eVXOg+PBAlGFVCuWD97iyn/K/BOR4H
lqYBUivrb3h8CM8jAnj+EER/hZUmHcFbreZTFFv3r2xmBF6LUrasueZAOZECuhXH
2+Q+eUzoI6r6AQkW4OHrJNGIAMDtwXBUwfm1zr53S6mie/MkSsWnWdzJKrOlX/y2
oYNXrHWoKvTKmrF8eObPSBalGVepL6mk8shvNmkZUflqcx8DWYw2HEZcpce4hVRE
0YoG/s75biiKWQlF9pk8/LdnVJof9uV0Fayu4O1cma/OCPIAg5LzFZ5mkjc76C5d
13rWhewRk5RwkSW5M5ifD/bw6j2etv+BblePHmiCILrw7KlcV+00MeF244Y9T9F9
u+5DUk6WfDReRbDAHSpjfLV/63FMbzbpX2DXKqs69sqv/4YbT20=
=mBLo
-----END PGP SIGNATURE-----
Tamaya's Future (was Re: Podling Tamaya Report Reminder - February 2020)
Posted by "John D. Ament" <jo...@apache.org>.
Hey guys
I signed off on the report. I'd really like to ensure that you figure out what your path forward is going to be. Activity is low, there was a release started end of last year that it's not clear was ever finished up.
If interest is low enough, moving to github is a fine approach. Typically keeping the name isn't a problem so your existing name could be reused.
Typically a project would take this approach if they thought getting releases out more frequently could help them rebuild a community around a project.
John
On 2020/02/03 21:27:23, "P. Ottlinger" <po...@apache.org> wrote:
> Hi guys,
>
> following our discussions I submitted our February report
>
> https://cwiki.apache.org/confluence/display/INCUBATOR/February2020#tamaya
>
> Cheers,
> Phil
>
> Am 16.01.20 um 01:27 schrieb jmclean@apache.org:
> > Dear podling,
> >
> > This email was sent by an automated system on behalf of the Apache
> > Incubator PMC. It is an initial reminder to give you plenty of time to
> > prepare your quarterly board report.
> >
> > The board meeting is scheduled for Wed, 19 February 2020, 10:30 am PDT.
> > The report for your podling will form a part of the Incubator PMC
> > report. The Incubator PMC requires your report to be submitted 2 weeks
> > before the board meeting, to allow sufficient time for review and
> > submission (Wed, February 05).
> >
> > Please submit your report with sufficient time to allow the Incubator
> > PMC, and subsequently board members to review and digest. Again, the
> > very latest you should submit your report is 2 weeks prior to the board
> > meeting.
> >
> > Candidate names should not be made public before people are actually
> > elected, so please do not include the names of potential committers or
> > PPMC members in your report.
>