OK, so I changed my mind again about sending you a personal email. I figured a topic like "how to contribute" would be better for everyone if it were done here in public.
As you know, there are lots of different ways to structure an "open source" project. Many of the most successful project structures that I've seen, at least in terms of developer satisfaction, looks similar to the one used by the jQuery project. Those projects have most of the following characteristics.
- roadmap with target dates
- changelog
- feature request tool
- bug tracker
- support forum
- developer forum (and maybe IRC)
- how to install tutorials
- how to use tutorials
- how to develop tutorials
- how to contribute tutorials
- how to report a bug tutorials
- OS license details and guidelines
- public code repository
- coding standards
- unit tests
- reg dev meeting w notes
- clearly assigned dev roles
- a public budget report
- more ???
And this doesn't even include any development!
I know that this is a lot of work and nearly impossible for a one- or two-man team, but I think simply articulating the targets is a good place to start. And I also know that you have already done a great job at implementing several of these tasks, but I personally think the project could use some better organization to get it the momentum it deserves.
Are you planning on implementing any more of things listed above? If so, what's the plan and how can others help?
I, for one, would be willing to help in executing some of these tasks. And though I prefer to get my hands on some code, I'd also be willing to take on some of the other important organizational tasks if that's what's most needed.
So there it is! Does this direction sound appealing to anybody else? Would anybody else be willing to lend a hand?
I'm looking forward to the discussion.
- Erick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for the late reply. Murray and I are both quite busy atm :).
To get to the topic: I think you can't be more right. A more open development process is needed, however, I personally think Sourceforge is a bit limiting in that point (for example: these forums aren't very good in ux, and a "hosted app" forum, like the phpbb we have can't be integrated). That, however, is another discussion.
I don't know precisely about Murray, but I will be able to invest a percentage of my time in ecoder and I hope to come up with at least the beginning of a new rewrite before the end of summer. I also had some ideas about making development more open, but as I haven't fully discussed them with Murray yet, I will not spread them publically (nice example of a closed development process :p).
To be fully open about my opinion (as I think an open process is very important) I think a bugtracker and a roadmap are the most important thing on your list. Doing that stuff in public should help the project to move quicker. On the other hand, as I said before, I hope to get a rewrite out before the end of summer (this is my personal goal, even our internal discussion is a bit unclear, to be honest) and I'd like to wait with the tutorials, for example, until that is done.
So to round up: I personally (and I must stress that that is a personal opinion, not something we have discussed or decided) would like to get off sourceforge and move to our own place, as this could bring more flexibility. In this way we could implement the ideas you summed up without sourceforge's limitations. Also, I'd like to get a rewrite out before the end of summer, but the roadmap is a bit foggy.
However, I'd like to ask you to still drop us an e-mail. You can reach me at wim at wimtibackx dot be and I'm quite sure Murray's address is somewhere here. In that way we can communicate easier and perhaps get things going.
Personally I'm quite busy until the 24th of this month, but afterwards I'll have much more time on my hands for Ecoder.
Also: others wishing to help out: drop us an e-mail, we can use all the help we can get, as far as I'm concerned.
And I promise, we will improve the openness of our development process :)
Kind Regards,
Wim Tibackx
Ecoder development team
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
All sounds good.. Wim - how did you learn a word like "foggy" - does sum it up well!
sourceforge provides something - but it is clearly not an essential part of the project ( which existed before it became available for download from here ).
I would be interested to join in a chat about direction and plans - technically Wim is the man, but I would love to have a more active input on UI / look and feel for the interface…
Cheers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK. Email has been sent to Wim. I couldn't find Murray's email addy anywhere on the forums or his website. Murray, ping me at hoppe xdotx erick aatt gmail and I'll cc you. I look forward to hearing from you guys.
- Erick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Welcome to Developers
Are you guys still looking for contributors? I'd be interested in helping out. I can do fron and back end. Let's kick this thing into gear!
- Erick
Whoops! Never mind. I see you've already answered this on another thread. I'll drop you an email soon.
- Erick
OK, so I changed my mind again about sending you a personal email. I figured a topic like "how to contribute" would be better for everyone if it were done here in public.
As you know, there are lots of different ways to structure an "open source" project. Many of the most successful project structures that I've seen, at least in terms of developer satisfaction, looks similar to the one used by the jQuery project. Those projects have most of the following characteristics.
- roadmap with target dates
- changelog
- feature request tool
- bug tracker
- support forum
- developer forum (and maybe IRC)
- how to install tutorials
- how to use tutorials
- how to develop tutorials
- how to contribute tutorials
- how to report a bug tutorials
- OS license details and guidelines
- public code repository
- coding standards
- unit tests
- reg dev meeting w notes
- clearly assigned dev roles
- a public budget report
- more ???
And this doesn't even include any development!
I know that this is a lot of work and nearly impossible for a one- or two-man team, but I think simply articulating the targets is a good place to start. And I also know that you have already done a great job at implementing several of these tasks, but I personally think the project could use some better organization to get it the momentum it deserves.
Are you planning on implementing any more of things listed above? If so, what's the plan and how can others help?
I, for one, would be willing to help in executing some of these tasks. And though I prefer to get my hands on some code, I'd also be willing to take on some of the other important organizational tasks if that's what's most needed.
So there it is! Does this direction sound appealing to anybody else? Would anybody else be willing to lend a hand?
I'm looking forward to the discussion.
- Erick
Hi Erick,
Sorry for the late reply. Murray and I are both quite busy atm :).
To get to the topic: I think you can't be more right. A more open development process is needed, however, I personally think Sourceforge is a bit limiting in that point (for example: these forums aren't very good in ux, and a "hosted app" forum, like the phpbb we have can't be integrated). That, however, is another discussion.
I don't know precisely about Murray, but I will be able to invest a percentage of my time in ecoder and I hope to come up with at least the beginning of a new rewrite before the end of summer. I also had some ideas about making development more open, but as I haven't fully discussed them with Murray yet, I will not spread them publically (nice example of a closed development process :p).
To be fully open about my opinion (as I think an open process is very important) I think a bugtracker and a roadmap are the most important thing on your list. Doing that stuff in public should help the project to move quicker. On the other hand, as I said before, I hope to get a rewrite out before the end of summer (this is my personal goal, even our internal discussion is a bit unclear, to be honest) and I'd like to wait with the tutorials, for example, until that is done.
So to round up: I personally (and I must stress that that is a personal opinion, not something we have discussed or decided) would like to get off sourceforge and move to our own place, as this could bring more flexibility. In this way we could implement the ideas you summed up without sourceforge's limitations. Also, I'd like to get a rewrite out before the end of summer, but the roadmap is a bit foggy.
However, I'd like to ask you to still drop us an e-mail. You can reach me at wim at wimtibackx dot be and I'm quite sure Murray's address is somewhere here. In that way we can communicate easier and perhaps get things going.
Personally I'm quite busy until the 24th of this month, but afterwards I'll have much more time on my hands for Ecoder.
Also: others wishing to help out: drop us an e-mail, we can use all the help we can get, as far as I'm concerned.
And I promise, we will improve the openness of our development process :)
Kind Regards,
Wim Tibackx
Ecoder development team
All sounds good.. Wim - how did you learn a word like "foggy" - does sum it up well!
sourceforge provides something - but it is clearly not an essential part of the project ( which existed before it became available for download from here ).
I would be interested to join in a chat about direction and plans - technically Wim is the man, but I would love to have a more active input on UI / look and feel for the interface…
Cheers
Excellent! I'll send an email today in hopes that we can start to clear the fog.
Best,
Erick
OK. Email has been sent to Wim. I couldn't find Murray's email addy anywhere on the forums or his website. Murray, ping me at hoppe xdotx erick aatt gmail and I'll cc you. I look forward to hearing from you guys.
- Erick
Did you get my email? I know you said you were busy until the 24th, but I'd love to know if you even received it.
- Erick
OK, thanks!
- Erick