Hi All, We have been working on a* connector tool <https://github.com/ankit-gubrani/AEM-WookieConnector>* which connects AEM ( *A*dobe *E*xperience *M*anager - Java based CMS) with Apache Wookie. And our idea is to use out of the box Wookie widgets directly in AEM.
In the future releases of this tool we are aiming to connect with other CMS like Drupal, Magento etc. We are focusing to introduce a Modular approach that we follow in AEM to develop components. Looking at the current market there are lots of big names using one or the other CMS like AEM, SharePoint, Wordpress, Drupal etc. We are willing to contribute to the current Wookie development. I think with a market shift towards different CMS (with AEM taking significant market share) introducing any such feature would give a push to Wookie's popularity as well. Let us know, we can discuss more and get started. Thanks Ankit Gubrani On Tue, Oct 6, 2015 at 3:04 PM, Scott Wilson <[email protected] > wrote: > > > On 6 Oct 2015, at 10:19, Sharples, Paul <[email protected]> wrote: > > > > On 05/10/2015 19:11, Scott Wilson wrote: > >>> On 5 Oct 2015, at 18:11, Ross Gardler <[email protected]> > wrote: > >>> > >>> Thanks Scott, > >>> > >>> I recommend the board report for this month indicate that there is a > discussion thread underway (this one) and that we will vote and act before > the next reporting session. > >> Good call. > >> > >>> That gives us a whole quarter to ensure this is the right thing for > the project. > >>> > >>> For what it is worth I’m +0 on the proposal. There are more than three > active PMC members (from an oversight perspective), but it seems no > development is underway as you say. If there are users out there who want > to keep the project alive now is the time to step up. > >> I’ve been contacting developers who’ve been mentioning the project in > recent events - not many, but there are a few, and it would be good to give > them an opportunity to get involved. I’m happy to mentor anyone who wants > to take an active role in steering the project. > > > > I'm guessing that Scotts Idea to try to get new engagement into the > project is a good one, hopefully we can find some developers before we to > decide to move wookie into the attic or not. > > Ankit and Rima should have just joined us on the list - maybe they can > introduce themselves and say how they would see Wookie developing..? > > >> > >>> Ross > >>> > >>> From: Scott Wilson [mailto:[email protected]] > >>> Sent: Monday, October 5, 2015 10:00 AM > >>> To: [email protected] > >>> Subject: Move Wookie to the Attic? > >>> > >>> In our recent reports to the ASF Board we’ve raised the possibility of > Wookie moving to the Attic[1], given we haven’t been able to grow our > community over the past two years. > >>> > >>> I think now is as good a time as any to make that decision, and so I’m > proposing we recommend that the Board moves Wookie to the Attic in our > report this month. > >>> > >>> When a project moves to the Attic it means it is no longer being > actively developed at ASF; however the code remains available for anyone > using it, and if anyone wishes to take the code and make use of it outside > of ASF (e.g. creating a fork) they are very welcome to do so. > >>> > >>> However, there will be no further official ASF releases unless the > project is “rebooted” by putting it back into the Incubator to build a new > community around it. > >>> > >>> There is no urgency in this as we still have enough PMC members to > vote on releases, and none of us are actively withdrawing, so if anyone > does object to the idea of moving Wookie to the Attic please speak up. If > anyone in the community wants to take the project forwards that would be > very welcome! > >>> > >>> S > >>> > >>> [1] http://attic.apache.org/ > > > >
