Yes, you are correct. Those community pages needs to be ASFified soon enough. Qi4j started in 2007, and it has been a long journey and many drastic changes along the way, from subversion to self-hosted Git to GitHub hosted and now to ASF hosted, from SiteVision CMS to AsciiDoc + Jekyll and now some Subversion based content.
A lot of docs has been written, a lot more is needed, and it is hard tiresome to do, the appreciation is low, and one must do quite a lot for it to be noticeable. The biggest 'advancement' in documentation was when I assigned 2 hours a day over quite a long period, writing mostly about what was being worked on at the moment by Rickard. I wished I had time for such cohesive effort again.... :-/ Anyway, instead of me complaining; I am really happy for your help Sandro!! Cheers Niclas On Fri, Jun 12, 2015 at 6:52 PM, Sandro Martini <[email protected]> wrote: > Hi, > > > Perhaps you and others haven't seen our "codebase" guideline; > > http://zest.apache.org/community/codebase.html, which contains a nice > > diagram on the Git forking model we use. > > Note that in that page, references aren't to ASF Git Zest repository > ... and probably something (later) should be written on how to > conrtibute via push request (with GitHUB mirror, or directly at Apache > Git ?). > > git://git.apache.org/zest-qi4j.git > and its mirror: > https://github.com/apache/zest-qi4j > > maybe that page has to be updated (and maybe even write that read-only > users can use normal http, not https). > > Note: > I'm using this but not sure if it's good the same (generally speaking): > https://git-wip-us.apache.org/repos/asf/zest-qi4j.git > > > > Maybe even this page should be updated (soon or later): > http://zest.apache.org/community/contributors.html > PMC Members and more info related on an ASF Project structure ... > > > Bye > > 2015-06-12 12:31 GMT+02:00 Sandro Martini <[email protected]>: > > Hi Paul, > > > >> And for information we have our "old" CI server at > >> https://qi4j.ci.cloudbees.com/ > >> > >> It already points to Apache git service. > >> > > great, I haven't an account there, but I'll try to take a look > > > >> The uploadArchive weekly job push SNAPSHOTS maven artifacts to our old > >> repository hosted at Cloudbees too. There is ZEST-20 to setup maven > >> repository @apache for the Zest project. > >> > >> If the `version` is a -SNAPSHOT, the build system do not sign the > >> artifacts so PGP setup is unneeded. > >> > > even better :-) , so I'd skip the signing of artifacts > > > > > >>> For updating Gradle to latest, I'll check it later (unless someone > >>> will do it before me) ... > >> I have the needed changes locally, will push them asap. > >> > > very well > > > >>> We need also to add our PGP signing keys to KEYS file, you remember ? > >>> And then maybe add keys from other Zest PMC Members (at least Release > managers). > >> We already have a KEYS file in the source tree root. > >> Only mine and Niclas's are in for now. > >> > > ok, I'll do some check on mine and maybe add there ... > > > > > > Paul, you know that in my "someone other" I was thinking to you as > > Release Manager, right ? :-) ... > > > > Thanks for now. > > > > Bye > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
