I will not commit to any specific day to release an update to Operator.

In other words:

I am placing these things as priorities above releasing on schedule.

Everyone who has any kind of software engineering or computer science training knows they should be testing, but seeing the actual order of priorities is interesting.

These projects are typically small projects that may be of interest to others, but which are unlikely to gain enough attention from the original author to become viable projects. In other words their TiLi projects. The idea is get the code out there and see if anyone else wants to pick it up. There is a single mailing list for all labs projects and very loose project guidelines that only really care about legal issues. No requirement for a website, complete documentation, community development etc.

The Apache Labs does not allow just any old project into its infrastructure, there are some controls, i.e. there has to be some complete funtionality. But there is very little requirement for ongoing maintenance of the code.

The benefit of labs is that it enables ASF committers to utilise the ASF infrastructure for their own TiLit work. Other people can get at the code and learn from it or work with it if they want. Should a project find a community is developing around it that project is moved to the Apache Incubator where there are requirements for creating a proper open source infrastructure.

Perhaps you should consider encouraging your employer to set up a “labs” project for you and your colleagues to share TiLi projects. After all, it won’t help anyone sitting on your hard drive.