Thanks to everyone who joined the discussion. It looks to me as if the project has a healthy level of ongoing development, and the community works together effectively on the mailing lists.
There are only two things missing: (1) a release, (2) for the community to say 'yes! we're ready to graduate!'. Sure, continuous integration (CI) is nice. But it's not essential. A well-running Apache community will create CI if they need it. So if you don't have CI, I guess you don't need it. Under Apache, a release is a legal act, not a piece of software engineering. You need to collect the source code into a tar ball (tar.gz file, or similar), write release notes, write instructions for someone who has downloaded the release to build it (or otherwise get it running), check that the appropriate headers, license and notices are present, and then vote that the tar ball looks like a valid release. The software engineering steps in a release are rather simple. You don't need Maven to create the tar ball; the following two shell commands are probably good enough: git ls-files > /tmp/manifest.txt tar cvfz sdap-x.y.tar.gz -T /tmp/manifest.txt You will need to sign the release tar ball, and you will need to publish the KEYS file that contains the PGP key that was used to sign the release. After the release you will need to add a Downloads page to the web site, and the release manager should publish the steps that they used to perform the release, so that you can repeat the process. That's it, really. If someone volunteers to be release manager (RM), they can roll a first release candidate, the mentors can critique it, and we can iterate until we have a good release. So, are ready to get started? :) Julian On 2022/10/14 19:30:10 Nga Chung wrote: > Hi all, > > I am an active member as well and am currently invovled with several NASA > funded projects that leverage and contribute to SDAP. > > As both Trevor and Frank had already mentioned, getting an official release > out has been the biggest hurdle. > > We had an attempt last year to set up GitHub Actions to automate the build > process but ran into a hurdle with pushing images to Docker Hub, so that > was left unfinished. > > Besides a formal release, I've heard from Stepheny that we also need to > identify a PMC chair, though I'm not clear what the process for that is. > > We could really use a clear checklist of items we must complete in order to > graduate. > > Thanks, > Nga > > On Fri, Oct 14, 2022 at 10:57 AM Frank Greguska <fg...@apache.org> wrote: > > > Hi Julian, > > > > I am an active member but mostly just admin stuff at this point; not able > > to provide much development support. I agree with Trevor's assessment that > > the hardest part has been trying to get a release together for review by > > Apache. There's a lot of history there I won't get into but I know there is > > a current effort underway to try again. > > > > - Frank > > > > On Fri, Oct 14, 2022 at 9:52 AM Trevor Grant <trevor.d.gr...@gmail.com> > > wrote: > > > > > Based on what I've seen from the project for the last couple of years, > > > here's my short synopsis of the status wrt graduating. > > > > > > To graduate, a project must cut an official release. This is the main > > point > > > holding SDAP back from graduation. Apache as an organization was designed > > > for creating and releasing Java projects, SDAP is a Python project. > > (There > > > are Python projects elsewhere in the ASF, but I will stand by my original > > > statement, that Java is first class, everything else should adapt to > > Java). > > > SDAP as a community has focused the majority of its cycles to supporting > > > existing deployments of their software as opposed to refactoring to > > conform > > > with ASF things. I don't think there exists undue stress from the ASF to > > > conform- just a lack of documentation for non-Java paths. > > > > > > My recommendation in terms of cutting a release (and thus removing the > > > largest hurdle to graduation) would be to > > > 1. call a code freeze > > > 2. tag / create a zip file of the current code base. > > > 3. have various PPMC member test the code (what ever that means in > > relation > > > to SDAP) > > > 4. vote > > > 5.manually push the zip file to whatever repository that is needed. > > > > > > I know there are lots of maven plugins that automate #5, that will be > > > effectively unusable since this isn't a Java project. Just get ahold of > > > someone at Infra and ask them what you need to do to manually release a > > > source tar ball. Then document it, maybe put it on the website- and make > > a > > > plan to do it again once a year to keep the board off your back. I know > > > your real life users don't care about official releases anyway, so it's > > > just a formality that has to happen every so often. > > > > > > My .02 > > > > > > tg > > > > > > > > > On Thu, Oct 13, 2022 at 1:17 PM Justin Mclean <jmcl...@apache.org> > > wrote: > > > > > > > Hi Julian, > > > > > > > > Thanks for reaching out to the SDAP project, I also think it time this > > > > project needs to consider graduating or the other option is retirement > > > from > > > > the ASF. > > > > > > > > Kind Regards, > > > > Justin > > > > > > > > > >
