I’m not sure what you’re asking here, but let me answer both interpretations:
If you’re asking who’s got the right permissions to execute such a change, I’d say the Jive people (I for one am not able to make the appropiate changes to SBS, JIRA, and I’m pretty sure I can’t make these low-level changes to the subversion repository setup either.
If, on the other hand, you’re asking who should have final say in wether or not we should go forward with this proposal, my answer would be: “the current leaders of the development team”. Although those people are not by definition the same people as “the Jive people”, I feel that currently only Matt and Gato would qualify. (See my upcoming comment in the “SVN Commit Access Guidelines” thread for a bit of elaboration on my viewpoint related to ‘current leaders’)
I had a quick chat with Matt last night, and he likes the idea as well. I’ll be splitting off the code in a few days.
In the meantime, we could come up with a project name, perhaps something slightly more attractive than “org.xmpp” (which is more of a package name, imho).
We could follow the -ack names that already exist, or fall back to the idea of naming projects after winds (remember ‘Pampero’? I liked that).
Xmppack Speaking about the winds. I kinda like the name Maestro. It’s a wind and also like a master of art (xmpp stanza mastering art ). Pampero is ok also. Though, maybe the name should sound similar to Whack?
There’s a number of projects with the name Maestro in sourceforge — I do like the name but I think it would be best to try to avoid a conflicting name if possible.
Xack is completely untaken. heheh Pronounced probably “Zack”. Has a nice ring to it.
I like Slush’s suggestion of “Tinder.” The link with the firy-theme of this community is obvious, and I like the ‘fire-starter’ implications that the name has.
I did a quick google for “xmpp tinder”. One hit that pops up is a Ruby API for Campfire. Although it’s somewhat related to chat, I think there’s enough distinction between that project and ours - I don’t feel the duplicate names would be confusing in that respect.
Tinder is cool with me … I can’t say I “like” OpenTinder, but if that’s what works so be it. =)
XTinder kinda has a cute ring to it “ex-tinder” kinda like extender but not. =D
I agree with trying not to copy the name of another library. Especially since it’s also XMPP related. Think about a potential list of available XMPP related libraries – you’d end up having to have something like:
Tinder - Ruby XMPP framework
Tinder - Java XMPP framework
=/
hahahahah what about Thwack? I’m mostly kidding about that one.
I like this idea too. Maybe we can move the org.jivesoftware.openfire.forms and org.jivesoftware.openfire.forms.spi packages also to the new lightweight xmpp libary? I plan to use them with whack and don’t want import all openfire stuff. Maybe there are more packages which are usefull for this libary?
As far as I can tell, the existing project named Tinder provides an API (to a product called BaseCamp, providing webbased chat), but isn’t an XMPP implementation. It can be combined with an XMPP implementation though, which is where the Google hits are based on.
I don’t think naming our project Tinder would cause mentionable confusion. As most of us seem to agree that this name has the best ring to it, I’d like to go with Tinder.
Chris, could you have a SVN repository created by that name please? Anonymous wizards in the order of JIRA (whoever you are), can a JIRA project be created as well please?
Guenther, I’m glad that someone claims usefulness, even before we announced the project. Your use-case is what I had in mind, when proposing the project. I’ve ran into something similar before - I bet others have similar problems.
If someone finds more useful packages that should move from Openfire (or Whack - not everything there might necessarily be external component related) let me know.
I’m writing a short roadmap and project definition, which I’ll share them later this weekend.
Can we go with TINDER, instead of a two-letter abbrevation? The full name is quite short in itself, and wouldn’t mess up any URLs that it’d be included in.