General Community > Off-Topic

The Pacer EditionCMS

<< < (9/11) > >>

mickpage:
No, serious. Issuing software under a licence is not to be taken lightly.

WebBird:
Maybe I should point out that this was a test.

I wanted to know how the people behind Pacer act. A fork normally has the goal to be "better" than the original, and in most cases the people who make a fork do so 'cause they don't succeed in ensuring that their ideas are really good and important. (For different reasons.) Sometimes the developer(s) of the original are no longer interested in developing, or they don't like the ideas, or they are not able to implement them, or whatever.

WB has a nice, helpful community and a (mostly) co-operative development team. But does Pacer have, too?

Doesn't look like this.

I think requesting the removal of a module (which is in beta state, just to mention it) from the bundle was a very simple test. They failed. They could have asked 'Why?'. They could have said: 'We like your work, we would be happy to bundle it. It's in your interest.' But instead, they just said: 'No, you released under GPL, end of discussion.'

So how will they act on other requests? Maybe more expensive (time consuming) ones? When asking for a backend enhancement, for example?

It's very interesting that this leads to a "political" discussion, insisting on licenses and such things. It's interesting that you're blaming _me_, telling me I shall leave the Open Source Community.

That's what I called "style". :-P

sharmpro:
Hello everybody,

I'm someone who tried to get things moving on WB! Where was the community when the discussion about the fork took place?

Only some of you, now concerned by our move, where then there.

In several month the thinking heads of WB couldn't came out with a realistic plan for a feature that could meet the 'minimum standards' to bring WB to the next level so in only 2 month and only few people involved, the Pacer Edition came to a point.

We feel sorry for the everyone feeling about  the ideas and code we picked up along the way thinking of a better use for our project than the present one on WB.
Feel free to express your concerns about the use of your initial idea, but please don't ask the community to stop using it!

The idea of a new project is (maybe) bringing some new life under the sun. It's not a war and for sure not a personal one.

As many projects start from a previous idea and code, any new developments can profit of  the 'status quo' and then proceed with new implementations. Our idea is as simple as "get the good ideas and bring up a new (possibly) better product".

I personally took some code and add my small or huge modifications to get at the end a complete new product (sometime a better one) to make available for the public and never got jealous of something ment to be public.

Having some of my work taken in consideration and even bundled in any project, actually would make me proud!

The restrictions of use of some modules I see happening now and in the near future is the opposite on what we're doing.

Regards

Stefano

ruebenwurzel:
@scharmpro


--- Quote ---Feel free to express your concerns about the use of your initial idea, but please don't ask the community to stop using it!
--- End quote ---

With your decision to announce your fork in the WB Forum you accepted the discussion here about your fork. So one thing is clear, you are here in the WebsiteBaker Discussion Forum and it must be allowed a open discussion about your fork, even the opinion to not use your fork must be allowed. If you don't wanna have discussed your fork in this way, you should have not opened this thread in the WebsiteBaker Community.

And as i see on your posts it looks like you definetely not interested in any discussion. This was the same as you decided to built a fork. You didn't accept other opinions then yours, how WB should be developped further.

So WebsiteBaker will be a community Project and your fork is a product of you and JohnP. I really hoped you find back to our community, but the way you do things (not allowing TinyMCE on AMASP, using graphics without asking the developper if you are allowed using it, the handling of EasyMenu ...) shows again that you are not interested on a community. So i think you only wanna use this fantastic and helpfull community to marketing your fork.

By the way, tested your fork and i never saw a beta wich produces more errors then yours. Starting from the install script where you are not able to allow higher php versions then 5.2.6 ending with your advertised sidebar wich didn't work on all tested servers. So your announced "next level" is a deeper (a very deeper) level and definately not a higher level. I Invite alll WB users to test the fork and built their own opinion.

Matthias

Argos:

--- Quote from: sharmpro on June 30, 2009, 01:49:19 PM ---I'm someone who tried to get things moving on WB! Where was the community when the discussion about the fork took place?
--- End quote ---
Which discussion? You mean that simple post in 2008 in a forum that is not read by regular WB users? No one responded on that post, as obviously no one knew about it. I for sure didn't, and I am a forum regular.

Look, it's perfectly allright to create a fork, why not? But why didn't you try to communicate about it better? Why not introduce your team and project properly? Why not tell us clearly why you decided to create a fork, why you think it is better, why you have lost faith in the WB development and community, and what your goals are. You don't even give that basic info on the project site.

Instead you drop an announcement on the WB forum, ask people to visit the project site, and when people go there, many basic questions are not answered. And when people are a bit agitated in the forum, nothings is done to callm us down, to explain, to try to cooperate, etc. All this together doesn't really create a positive attitude towards your project and team. That's a shame, cause combined efforts to make WB better could be a good thing.

Navigation

[0] Message Index

[#] Next page

[*] Previous page