Patch, mailing list etc...
9 posts,
6 voices
|
Feb 6, 2008 05:45
13 posts
|
Hi all, i'm a new frog user, i started some days ago to play with Framework ad Frog, i really love the clean code and the approach of both; well done :) Anyway, i wrote small patch to add some functionalities to Frog, and reading the code i see some duplicated portions of code or minor bug... i suppose you already know about it, but could be interesting to discuss. So why not open a mailing list or a group on google for the developers; i think could be the best way to discuss about the devel and keep up to date. What do you think? where may i submit my patch to let you to review? |
|
Apr 23, 2008 13:55
6 posts
|
I think getting a Google Group setup is a great idea. |
|
Apr 23, 2008 14:57
83 posts
|
i think that would be awesome ;) phillippe, go on! :p |
|
Apr 24, 2008 03:23
6 posts
|
Btw I think patches can be submitted here: http://code.google.com/p/madebyfrogs/issues/list/ I submitted a small patch for FileManager yesterday. |
|
Apr 24, 2008 10:18
820 posts
|
@Chrononaut: Glad you found the Frog Google code page. It seems Philippe isn't linking it from the main Frog site at the moment. I suppose developers could always use this part of the forum: it's listed under "Development", anyway! :) It seems quite a few in this small community are not really backend developers/coders.... David. |
|
May 27, 2008 09:03
6 posts
|
Just to let you know, I have created a fork of Frog CMS for use at work. Future goals are listed here: http://github.com/Chrononaut/monolith/tree/master . Changes already made are listed under the "Commits"-tab. If anyone is interested in contributing, I'll give you commit access after you get one patch accepted. Hopefully some of these changes gets merged back into Frog CMS, but that's Phillipe's call. For me, Frog CMS development is currently just too slow/closed for contributions. |
|
May 28, 2008 04:35
396 posts
|
@David: The only developers on the team that I'm aware of is Philippe himself and a certain djreimer. :-) In defense of Philippe: Frog has only existed since mid 2007 or so as far as I can tell.. I think Philippe has done a marvelous job on Frog so far. The only slightly frustrating thing right now is that I/we have no idea what Philippe is planning for Frog and on what timescale. @Philippe: if you're reading this, I'd be happy to help out occasionally with applying patches for example. Please open up Frog development a little more. |
|
May 28, 2008 04:58
13 posts
|
Personally i think that the right solution is talk to Philippe, frog it's still a small project with few people and even less coders. So we could try to improve Frog before try to forking. @Chrononaut: i agree with mvdkleijn, anyway i've read your short and long term goals and i agree. I've already ported frog to jquery and write additional code for my personally propose; sadly i not yet fully tested the code (this is the main reason because i've not sent a patch). @mvdkleijn: Philippe made a really good job with frog, but i think that we need a developer plan or so, i would use frog at work, but i don't write/manage/develop a software alone, actually i don't have the time. I need to know that the software it's active and have an active community. Anyway I understand that this is for Philippe an hobby or something that really like to do on his spare time. |
|
May 28, 2008 11:10
6 posts
|
BTW: I don't want to compete with Frog - the motivation behind this fork is to help improving Frog. Which is what will happen if some of the changes gets merged back in. At the moment I don't see any other way for contributing code. I do hope that this fork is only a temporary one, working together is of course the best option. |
|
2 days ago at 17:37
9 posts
|
I second Chrononaut and would also setup mailinglist on Google Groups. Developer type of guys generally do not like to hang on forums (me included :). |