Forums

Just to clarify: The “post-commit” hook is in Subversion, and it is used by the scripts provided by Bugzilla and Trac. (Not the other way around.) It’s hardly an “integration”, thus I interpreted him to mean the repo browsing features.

Good, since none of them require compilation. (Disclaimer: Python will compile to bytecode when running a script.)

EDIT: Unless you meant the interpreters themselves, in which case: never mind!

I see where you're getting at.    I don't know.  Maybe you should write an email to FSF.   I'd be interested to know too.

The section "How to Apply These Terms to Your New Programs" in GPLv2 states that "each file should have at least the "copyright" line and a pointer to where the full notice is found." But this only refers to "new programs", and that section is not part of the actual license terms.  The terms for modified software are described in section 2 of the GPLv2.  As you will notice, the terms of section 1 (including the first snippet I posted) also apply to modified software.  FluxBB 1.3 is "modified software".

That was exactly what the "hold Enter" part was for.

Calling people trolls and mocking their age is completely unnecessary and uncalled for.

Am I really the only one who managed to close the tab?

Happy new year. It's already 2009 here.

And because of that I forgot what's most important: happy birthday!   (And a merry new year.)

If you're talking about this:

Then I suppose from this post.

I don't think you've been reading carefully what I've said.    The way I see it now, there are at least three ideas about this floating around:

1. Have separate devs for the 1.2 (1.4) branch (as suggested at least by Smartys, Elbekko, me…)

2. Develop both branches with the same developers (yann, …?)

3. Stop developing 1.2 (only maintaining security fixes) and focus all efforts on the 1.3 (2.0) branch instead (Rich, ridgerunner)

You seem to be under the impression that I support C, and still want to use 1.2.

No one said that.  But fact is, many people don't need those features, at least not yet.  Things like UTF-8 support are (in my opinion) much more widely needed.  And like Smartys said, "The idea is to support 1.2 for the many people who can not or will not upgrade to 1.3 while also developing a more modern version of 1.2".  In the long term, using an obsolete forum software would be a bad idea, but like I said, I would support further development of the 1.2 branch, while the current dev team would have less pressure with developing the 2.0 branch.

You're making it look like I was diminishing it.  I'm not.  Some people just don't need it and/or the current methods (hacking the code manually) work well enough.

For people who want an extensible forum as opposed to minimalistic, the extension system will be a good addition.  For people who don't need extensions, it's useless.  That is my point.

Sharing is caring!

Didn't he just say it?

Haha

gender