Yeah, before it becomes a TLP, there should be something to be done and happen. One thing is, have a separate web site. I discussed about this with an Apache officer and was told it was doable. There can be found quite a few examples, sub project can have standalone web site.
To evolve, we shouldn't keep all things together, to make the parent web site crowded and crowded. Glad to have a new component from PSU! Regards, Kai -----Original Message----- From: Shawn McKinney [mailto:smckin...@apache.org] Sent: Saturday, May 14, 2016 7:16 AM To: Apache Directory Developers List <dev@directory.apache.org> Subject: Re: Scim library contribution > On May 13, 2016, at 3:40 PM, Emmanuel Lécharny <elecha...@gmail.com> wrote: > > The rational here is to make sure that we have some common interest in > having those projects and the associated people working hand in hand, > to create a strong community. It has been immensely valuable to have the guidance of this project committee. It brings extra eyes to our code and processes. > > On May 13, 2016, at 3:40 PM, Emmanuel Lécharny <elecha...@gmail.com> wrote: > > Fortress was also benefiting from ApacheDS, as all the unit tests are > based on it. Now that a 1.0 is out, we can also think about making it > a TLP. That would be up to Shawn and Chris to see when it would make > sense, but the community around it is small atm. Agreed. The community must grow before TLP status makes sense. Otherwise I guess you’re stuck with us cause we’re not giving up anytime soon. ;-) Shawn
