Hi
> > We will think about this. At the moment, I prefer to have the (technical)
> > control over my infrastructure.
>
> what's the problem with the mozdev infrastructure?
At the moment, they are in a transition phase and have a huge backlog to
work through (that's what I heard)
Furthermore, my whole setup is adjusted to use my servers. I know, it's
not a big task to move that, but my time is really rare at the moment. I
just don't need more work to do just right now. It will hopefully be
better in a few weeks.
> But it's well possible, that we will move
> > over to mozdev as soon as I have more time for such things
>
> I can help you on this if you want (populate the CVS, setup the mailing
> lists, write some html pages, etc.
I'll take your word ;)
> > And furthermore, I will contribute as much as possible back to mozile.
> > I'll get CVS access to it in the next few days. Therefore some kind of
> > joint developement on mozdev is already happening.
>
> great
>
>
> Sorry for being such a pain in the ass, but I think you are repeating
> the same mistakes community wise again. I would like to suggest the
> following:
>
> 1) Choose another name (independent of your company), e.g. the japanese
> word for "editor"
>
> 2) Host your project at mozdev (CVS and all community tools ...)
We'll discuss that soon
> 3) Let other people in as soon as possible
>
> 4) Don't write your code behind closed doors
I think, you don't get any other people in if there's not much to show.
My plan is to have a working alpha version in 2 weeks. And then I will
widely announce that. If anyone is interested in working on it right now,
do not hesitate to contact me right now. I'll also try to post more on
this list about my current progress.
At the moment, I'm testing a lot of stuff, try this, try that and
hopefully will come up with a solution very soon. If anyone wants to share
his thoughts with me, I'd be very glad about that.
Besides that, the mozile mailinglist is quite active and we get some
mindsharing over there.
To sum up, after I have a working alpha version (alpha means alpha and not
a finished product), we are certainly willing to discuss a move to mozdev
and choosing a new name for it.
> 5) ensure simple integration into all kind of other CMSs
That right on the top of my list. With using Mozile as a backend, even CMS
only using XHTML as there content-format should have in intereset in using
BXE/Mozile.
chregu
--
bx-editor-dev mailing list
bx-editor-dev@xxxxxxxxxxxxxxxx
http://lists.bitflux.ch/cgi-bin/listinfo/bx-editor-dev
|
