--- Begin Message ---
I'm non binding -1 on this as a starting point. I prefer a unit
test-first/code-oriented approach to the specification design. I've
been unimpressed by past efforts to start this on the wiki. Not that
there shouldn't be discussion but it should be discussion about commi
Cool, appreciated. If we did this, I'd expect we'd keep this in the
same project in ASF, though a rename from James to Email might make
sense. That's unchartered territories though, and I'd rather not deal
with it too much if we can avoid it.
Sure. Committership/voting should be different t
Okay. I don't think its very important but could be to others. Since
JAMES is the server and it will be perceptually JAMES's mailets and not
just Apache Mailets it might kind of inhibit adoption. I don't really
care enough to be personally inhibited, just pointing out that it is an
inhibitio
I wouldn't mind starting to formulate a plan. Here are some
suggestions. I'm somewhat inspired by the JCP, but probably everyone
here (including myself) has problems with it. I think the overall idea
of how to create a compatible API with compatibility standards can be
done in an open/open-s
I don't really see us as that competitive. I rather thing we'll carve
out two different nitches in the market.
I've actually started moving most of the plan into JIRA. We're actually
going to try and cut a 1.0 release sooner rather than later and cut our
planned feature set (really just move
Don't want to confiscate the list but just correct a falacy that I've
propegated through negligence.
Yeah thats a lie, I update the schedule as things progress so its always
"best information RIGHT NOW" but I haven't had a moment to update it. I
will shortly.. . its looking like May for an initia
