Hi, On Friday, August 23, 2013 11:51:10 Thom Castermans wrote: > Quite some time ago, we sent a mail [1] on this list to ask for your > opinion about Joxy [2]. Joxy is a Java look-and-feel that aims to have > nice-looking integration with the Oxygen theme, the default under KDE. > Stimulated by the positive responses, we kept working on Joxy whenever > we had time (which is not as much as we would like, unfortunately). > Now, recently we migrated to a Maven structure (currently, this is > still in a separate branch, but we plan on merging it into main soon) > and we feel like Joxy is finally becoming a decent project. It was > suggested [3] on our forum that Joxy can become a KDE project and we > think that would be a good step. We hope that other people want to > contribute to Joxy too - there are still a lot of things to improve - > and being on KDE Playground would help in that matter we think. > > So basically, we would like to ask if it is possible to move Joxy > under the KDE umbrella (Playground?) and if so, if there is some kind > of procedure that we should follow or if there are some requirements > that we should meet. For example, the KDE website [4] notes that "The > KDE Playground group is defined as those applications built on the KDE > Development Platform that are hosted by the KDE infrastructure but > have not yet had a stable release and may never be released." However, > Joxy is built in Java (and a bit of C++) and hence not on the KDE > Development Platform: would that be a problem? We look forward to hear > from you!
No, the build dependencies or technology doesn't matter. To get Joxy under teh KDE umbrella, you need to agree and follow the manifesto at http://manifesto.kde.org/ If you do, I don't think there's anything in the way of getting Joxy "into KDE". This page should help you get going with that: http://techbase.kde.org/Contribute/Get_a_Contributor_Account Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
