1. Wiki, it's already available. Maybe we should reconstructure the
content so they could be better categorized.
2. Bug tracker, it's already available using Mantis. Maybe we
should fix the appearance so its theme could fit the new design.
3. Source code browser, it's already available using
If you mean in FPC, count me in :)
From the content structure that I proposed on the other thread, we
need some applications to accompany the web site.
1. Wiki, it's already available. Maybe we should reconstructure the
content so they could be better categorized.
2. Bug tracker, it's
On Feb 2, 2010, at 6:05 PM, Michael Van Canneyt wrote:
4. Contributed code repo, it's already available through
Contributed Units on FPC site. I think we should build a new one
for this using fpWeb.
I was planning to do so. I will also rewrite the testsuite tool.
Great news. This is a
1. Wiki, it's already available. Maybe we should reconstructure the
content so they could be better categorized.
2. Bug tracker, it's already available using Mantis. Maybe we should
fix the appearance so its theme could fit the new design.
3. Source code browser, it's already available using
On Tue, 2 Feb 2010, Bee Jay wrote:
1. Wiki, it's already available. Maybe we should reconstructure the content
so they could be better categorized.
2. Bug tracker, it's already available using Mantis. Maybe we should fix
the appearance so its theme could fit the new design.
3. Source code
On Feb 2, 2010, at 6:38 PM, Michael Van Canneyt wrote:
One more thing:
8. Account integrator. Since we have many applications for the
website i.e. wiki, forum, mantis, svn, etc. I think we should make
one app to synchronized a single account across those apps. So, the
user would only
02.02.2010 17:56, Bee Jay wrote:
5. Code bounty manager, it's not available, only a page on Wiki. I
think we should build a new app for this for more accountable
participants. This app could become a way to boost FPC and Lazarus
development.
Maybe bounty field can be added to the bug-tracker.
Michael Van Canneyt wrote:
On Tue, 2 Feb 2010, Bee Jay wrote:
8. Account integrator. Since we have many applications for the website
i.e. wiki, forum, mantis, svn, etc. I think we should make one app to
synchronized a single account across those apps. So, the user would
only remember 1
On Feb 2, 2010, at 7:05 PM, Paul Ishenin wrote:
Maybe bounty field can be added to the bug-tracker. So if a reporter
want to pay some money for the issue he/she can fill that field?
Anyway, bounties does not differ from regular issues - just reporter
want to pay to speedup the solution.
02.02.2010 19:18, Bee Jay wrote:
Good idea. But, IMO, it should be put upfront instead of hidden
beneath the mantis system. It will ease people who want to donate to
the development, not just for technical things, but for other non
technical things as well e.g. creating a tutorial, writing an
2010/1/31 Zaher Dirkey parm...@gmail.com
On Sun, Jan 31, 2010 at 9:20 AM, Graeme Geldenhuys
graemeg.li...@gmail.com wrote:
On 31 January 2010 01:52, Marc Weustink m...@dommelstein.net wrote:
If it is to be for the FPC website too, then Firebird is a must.
When talking databases, I'd
31.01.2010 6:51, Marc Weustink wrote:
I vote against any yet another complex to be hacked php site.
So if we do something then I either prefer to something fpweb or keep
the current engine. (and I'm serious about that)
What is fpWeb? Some pascal web framework. Framework is not a cms so to
31.01.2010 6:52, Marc Weustink wrote:
When talking databeses, I'd prefer Postgresql.
Postresql maybe a good database engine but Firebird is the better choise
since it is related to Borland. Borland is related to pascal, pascal to
fpc, and fpc to lazarus :)
Best regards,
Paul Ishenin.
--
Hmm, the fact that this thread already has a lot of messages but the
content thread (which it is all about imho) has not recieved one
answer makes me a bit sceptical about this project...
;-)
--
___
Lazarus mailing list
On Sun, 31 Jan 2010, Marc Weustink wrote:
Michael Van Canneyt wrote:
On Sat, 30 Jan 2010, Paul Ishenin wrote:
30.01.2010 23:00, Bee Jay wrote:
For development reason, I still prefer fpWeb. Yes, we would reinvent the
wheel, if we say in CMS world as there are many ready-to-use CMS out
On 1/31/2010 4:58 AM, theo wrote:
Hmm, the fact that this thread already has a lot of messages but the
content thread (which it is all about imho) has not recieved one
answer makes me a bit sceptical about this project... ;-)
Yes, it seems like people are just recommending the database they
The companies around me that makes the best websites, don't use CMS's
anymore. And if they do they do not use on of the standard ones, but one
of their own.
That's because a good website begins with the design. And all
CMS-systems lay rules on how the design should look like. If you want to
On Sun, 31 Jan 2010, Joost van der Sluis wrote:
The companies around me that makes the best websites, don't use CMS's
anymore. And if they do they do not use on of the standard ones, but one
of their own.
That's because a good website begins with the design. And all
CMS-systems lay rules on
Em 31-01-2010 04:58, zeljko escreveu:
On Sunday 31 January 2010 00:52, Marc Weustink wrote:
When talking databeses, I'd prefer Postgresql.
+1
zeljko
+1.
--
Silvio Clécio
--
Contato - silvioproggmail/googlewave
Blog estilo mural - silvioclecio.blogspot.com
Twitter - twitter.com/silvioprog
On 1/31/2010 04:58, theo wrote:
Hmm, the fact that this thread already has a lot of messages but the
content thread (which it is all about imho) has not recieved one
answer makes me a bit sceptical about this project...
;-)
maybe the problem is that the discussion is not subject line oriented
theo wrote:
Hmm, the fact that this thread already has a lot of messages but the
content thread (which it is all about imho) has not recieved one
answer makes me a bit sceptical about this project...
;-)
If I try to remember where all this started, it was the lack of a simple
welcome page
On Sat, 30 Jan 2010, Bee Jay wrote:
Hi all,
One more thing, but this is optional, we should give the decision to the one
who are gonna do the real work: what tool are we going to use to serve the
backend? PHP? Wordpress? Joomla? fpWeb?
Honestly, I expect it would be build using fpWeb.
At the very least, this point has my vote :-)
I'll contribute my yunior designer work on this effort. I'll confirm
this by Monday. I'll personally supervise his work. He's able to
produce the HTML, CSS, and required JS for the design. So, it's only
the front-end part. Would you do the
30.01.2010 23:00, Bee Jay wrote:
For development reason, I still prefer fpWeb. Yes, we would reinvent
the wheel, if we say in CMS world as there are many ready-to-use CMS
out there, though mostly build using PHP (and mysql). But, in pascal
world, it maybe the first CMS that's build using
On 30 January 2010 18:00, Bee Jay bee.ogra...@gmail.com wrote:
and showcase for FPC/Lazarus. And for the database, personally, I much
prefer Firebird, for many reasons. But, again, that's me.
+1 here. Firebird is so much better than MySQL. I really don't
understand the hype around MySQL.
--
On Sat, 30 Jan 2010, Paul Ishenin wrote:
30.01.2010 23:00, Bee Jay wrote:
For development reason, I still prefer fpWeb. Yes, we would reinvent the
wheel, if we say in CMS world as there are many ready-to-use CMS out there,
though mostly build using PHP (and mysql). But, in pascal world, it
Paul Ishenin wrote:
30.01.2010 21:34, Bee Jay wrote:
One more thing, but this is optional, we should give the decision to
the one who are gonna do the real work: what tool are we going to use
to serve the backend? PHP? Wordpress? Joomla? fpWeb?
Honestly, I expect it would be build using
Michael Van Canneyt wrote:
On Sat, 30 Jan 2010, Paul Ishenin wrote:
30.01.2010 23:00, Bee Jay wrote:
For development reason, I still prefer fpWeb. Yes, we would reinvent
the wheel, if we say in CMS world as there are many ready-to-use CMS
out there, though mostly build using PHP (and
On 1/30/2010 18:51, Marc Weustink wrote:
Paul Ishenin wrote:
30.01.2010 21:34, Bee Jay wrote:
One more thing, but this is optional, we should give the decision to
the one who are gonna do the real work: what tool are we going to use
to serve the backend? PHP? Wordpress? Joomla? fpWeb?
Before use pascal (fbWeb or others), you must ask how many users will use it
in the future (use the project in there site), because those user will
improves the project by send bugs and patches.
SY, Zaher Dirkey
--
___
Lazarus mailing list
On 31 January 2010 01:52, Marc Weustink m...@dommelstein.net wrote:
If it is to be for the FPC website too, then Firebird is a must.
When talking databases, I'd prefer Postgresql.
Postgresql eluded me for many years (I don't know why). I was
pleasantly surprised when I took a look at
On Sun, Jan 31, 2010 at 9:20 AM, Graeme Geldenhuys
graemeg.li...@gmail.comwrote:
On 31 January 2010 01:52, Marc Weustink m...@dommelstein.net wrote:
If it is to be for the FPC website too, then Firebird is a must.
When talking databases, I'd prefer Postgresql.
Postgresql eluded me for
2010/1/31 Zaher Dirkey parm...@gmail.com:
Firebird has less features than Postgresql but Postgresql has bad client
(for me), I prefer FirebirdSQL.
If you're going to use Drupal, then I think the options are MySQL or Postgres.
Personally I don't like MySQL; I think it's weaker than Postgres.
On Sunday 31 January 2010 00:52, Marc Weustink wrote:
When talking databeses, I'd prefer Postgresql.
+1
zeljko
--
___
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
34 matches
Mail list logo
