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 <atsti...@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 < > pottlin...@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* >
