Tracking REBOL Projects
I've added a few updated comments to the end of this article, based on comments within the group.
I need your help! These days there's far too much going on in the world of REBOL for me to personally keep track of and attempt to manage it all.
In fact, I have so many projects right now (about 20), I can hardly keep track of those alone. I now use an internal website where I use the WIP Wiki 3 to keep track of projects and all the notes related to them.
However, for worldwide REBOL projects, including those related to R3 development, the situation is more complex. I would classify it right now as a bit chaotic.
So that's a problem; now what's the solution? The perfect solution (for me) would be a web-page that lists each project along with status, who's leading the development, and when something was last done. It could also be for "wish projects" (things we want, but don't yet have developer commitments), as well as bounties, if so sponsored.
Yes, originally, I wanted DevBase to do this. But, I just don't have the time.
So, I need your help identifying an existing open software projects website that we could rally around for REBOL projects. This approach not only gives everyone access, also adds some visibility to REBOL overall.
Of course, whatever we pick, it must be possible to see a list of all REBOL projects and the status of each project... that's my primary requirement.
In addition to the Host-Kit, a few projects that are high on my R3 list are:
And, there are many others.
I should stress that simpler is better. We do not need the classic project management system with all the administration duties and such (because that's not an effective approach for community-based project development.)
What I envision is a listing of projects that can be suggested by or implemented by anyone who's interested. The main purpose of the list is to make developers aware that a need exists for each project. For example, a better R3 console.
This is important because if the full development community can see the list, they may find that they can contribute to projects in one way or another. In addition, allowing anyone to post a project makes it possible for developers to request the implementation of something that is important to them (but perhaps not to others), even if they don't intend to implement it themselves.
And finally, some of the projects will "pop up" as being features we may want integrated into R3 itself. So, the list gives us a stream of improvements to the capabilities for all users.
The bottom line is that the result is more of a communication method than a management mechanism. That's what I'm interested in.