>> Hasn't that been done already on the discussion thread about this? Eg >> releases would follow the usual ASF release requirements and need to >> be labeled as a Labs release similar to how Incubation releases are >> labeled as incubating and then review/vote as any normal release so >> with at least 3 Labs PMC member +1s required. > > How is that not "routing around the Incubator?"
You are no official Apache project You cannot use Apache in your release name You do not have an TLD You do not guarantee to continue development with the tag "Labs" and so on > What is the point of the release? To raise interest in the lab? Isn't that > community building? Isn't that what the incubator is for? You could do a tag of a "pretty stable" bunch of your code. Or you could simply create a jar/zip file of it. If the download really gets attention, then you can move to the incubator. Maybe you simply want to have a jar file ready without checking out the sourcecode all the time. Or you want to use that on a project and send to a collegue. > What if it raises interest? You want to give commit access to non-ASF > committers, right? If interest raises and you want non-committers to collaborate with you, you can either go to the incubator or to apache-extras. Lab is closed then > How is this situation different from the incubator? See above and probably my suggestion to create components for projects you have no karma for > Why do we need to route around the incubator like this? This is no rerouting. Projects are too small for the incubator when they arrive at labs. They are more an idea without the goal to succeed. In incubator is no guarantee still, but the goal is to succeed. > Why did the original proposal include rules that specifically prevents this > routing around the incubator? Because it should not bypass the incubator. While incubating, you are mentoring new apache committers (probably) and clear IP questions. In labs people are already apache committers and start there - therefore the ip is clear. > How do we manage user expectations of projects that come out of labs? What do you mean with that? A lab exits to the incubator (do community building) or terminates (apache extras) or goes directly to a TLD, if the project is interested to take this component. A lab has a clear IP and has done by asf committers only. > Its OK for the incubator to say "here's an incubator release, this project > may not be sustainable but we are working towards it". I'm not sure that > saying "here's a labs release we have no intention of making this sustainable > via a community" makes any sense at all. If the release isn't saying this > then what leaked it different from an incubator project? When a TLD is stable software, I consider incubator "beta" and labs "alpha". It just to try out. > I'm not saying these questions can't be answered satisfactorily I'm just > saying that, at least for me, they are not yet answered. > If someone can come up with sensible answers the. I promise I'll back down ;-) We all try best ;-) Maybe we need to reflect the starting point of a lab. This is different to the usual starting points of the incubator. Rarely I have seen starting a project from scratch in the incubator. A project/component from scratch should start at the labs. Cheers Christian > > Ross > >> If the labeling requirements need to be spelled out in more detail >> then ok lets do that but presently i'm not sure there is much point >> until the Labs PMC is more on board. Maybe thats just going to take >> more time so more and more people who've worked on Labs get added to >> the PMC as its those who seem more in favour of doing this. >> >> ...ant >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- http://www.grobmeier.de --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
